0.1
Find the real constraint.
Start with the system, the people operating it, and the failure that matters. A clear boundary is more useful than a broad promise.
Bordeaux / software systems
Quavern is a Bordeaux software studio building and running open-source AI, developer tools and public-data systems.
Four services are in operation. The latest release is QuavernOS Aurora 2026.0.
01 / Services
Everything below is live and can be opened today.
02 / Method
Technology choices follow the constraint, not the fashion cycle.
0.1
Start with the system, the people operating it, and the failure that matters. A clear boundary is more useful than a broad promise.
0.2
Keep the important logic inspectable where openness creates reuse, confidence, and a credible route beyond one vendor.
0.3
Use hosted software where shared operation is the useful part: deployment, maintenance, collaboration, or live public data.
0.4
Prefer legible interfaces, open formats, measured behaviour, and documentation that survives the first release.
03 / Practice
Every decision should be visible in the work, not only in the pitch.
| Practice | Quavern stance | Evidence to leave behind |
|---|---|---|
| AI | An implementation material, used when it improves the system. | Evaluations, failure cases, cost, and a non-magical fallback. |
| Open source | A way to make the durable core inspectable and reusable. | A licence, readable code, contribution paths, and releases. |
| SaaS | Shared operation where running the service creates value. | Clear boundaries, export paths, service status, and ownership. |
| Public data | Maps and transit treated as living systems, not decoration. | Sources, update dates, geometry, provenance, and accessibility. |
04 / Company
“Open by default. Useful at street level. Maintained for the long run.”