Why we publish this
A dependency you cannot exit is not a supplier relationship. It is an exposure.
Switzerland has just demonstrated what that exposure is worth: a
capable platform was rejected because the residual risk of not being able to inspect it, or
to run it without its vendor, was judged unacceptable. We think that judgement was correct, and we would rather be measured against it openly than argue about it in a questionnaire cell.
1 · Your data is yours, in formats you can read
No proprietary storage formats. Data is held in open, documented structures, and the
schema is part of your documentation set, not a trade secret.
- Complete export of all data and history, on request, at any time
- Open formats, JSON, CSV, SQL dump, never an opaque container
- No export fee, no volume limit, no notice period
- Exports remain available for an agreed window after termination
2 · Documented interfaces, not private ones
Every capability the system offers internally is reachable through a documented
interface. If we can do it, you or your next supplier can do it too.
- REST APIs with published specifications
- No undocumented endpoints reserved for our own tooling
- Integration with your existing systems by contract, not by favour
3 · You control where it runs and when it changes
Containerised and deployable on your own infrastructure. There is no mechanism by
which we can push a change into your environment without your decision.
- On-premise, private cloud or Swiss hosting, your choice, not ours
- You decide the update cadence; no forced remote update
- Reproducible infrastructure definitions handed over with the system
4 · Source escrow
Source code and build instructions deposited with an independent Swiss escrow agent,
released to you on defined trigger events, insolvency, discontinuation, or sustained
failure to meet support obligations.
- Escrow agreement offered as standard, not as a negotiated concession
- Release triggers written plainly and testable
- Deposit verified to build, not merely deposited
5 · Your team can run it without us
The measure of a good handover is that it is boring. Documentation and training are
deliverables, not afterthoughts, and we will train your staff to operate the system.
- Architecture and operations documentation maintained as part of delivery
- Operator and administrator training included
- Runbooks for the failure modes that actually occur
6 · Exit assistance is a duty, not a negotiation
If you decide to leave, our obligation to help is written into the contract before you
ever need it, including help handing over to a competitor.
- Defined transition support period at agreed rates
- Cooperation with an incoming supplier, including knowledge transfer
- No hostage clauses: no data withheld, no licence cliff, no exit penalty
And the part most suppliers leave out
We are an early-stage firm. We do not yet have a long list of comparable installations,
and we will not pretend otherwise in a tender. What we offer instead of a reference list is
verifiable structure: a system you can inspect before you commit, a fixed-scope pilot rather
than a leap, escrowed source, and the exit terms above agreed in advance rather
than discovered later.
If a reference list is the deciding criterion, you should choose an established supplier, and we will say so. If what you actually need is a Swiss partner who cannot lock you in and
is small enough to be answerable, that is precisely what we are built to be.
These commitments describe how we contract and how our systems are built. The
binding form is the contract itself; this page exists so that the conversation starts from a
known position rather than a discovery process. Ask us to put any of it in writing.