Digital sovereignty
Sovereignty means: you can leave.
Software only becomes yours when you can keep running it without its maker. That is exactly how we build — contractually, technically, verifiably.
Why this topic is on every table.
US law reaches into Europe
The CLOUD Act obliges US providers to hand over data — even when the servers are in Frankfurt or Vienna. If you hold sensitive client or case data, you carry that risk with them.
Renting is the weaker position
Price hikes, dropped features, discontinued products: whoever builds on rented software negotiates without an alternative. A real exit option is the strongest negotiating position.
Your customers ask about the supply chain
With NIS2, large clients audit their software suppliers: where does the data live, who owns the code, what happens in an outage? You need answers to these questions — not excuses.
What ownership means at NEPTIQ, concretely.
- 01
Source-code handover
Contractually agreed for custom development: repository, history and docs transfer into your ownership. Not a viewing right — actual ownership.
- 02
Standard stack
TypeScript, PostgreSQL, open standards. Any experienced development team can take over your system — you are never dependent on us.
- 03
EU data residency
Hosting and databases in the EU. On request with EU-sovereign providers — the choice is yours, not the vendor's.
- 04
On-premise option
Selected products run as Docker containers on your own infrastructure. Your hardware, your control.
- 05
Data export without hurdles
Your data leaves the system in open formats — CSV, JSON, PDF. No application, no extra fee.
- 06
Escrow on request
For licensed software we deposit the source code with an escrow agent on request. If the maker fails, your system does not.
The three questions nobody asks — until it gets serious.
What if NEPTIQ is gone tomorrow?
Your code sits with you (custom development) or in escrow (licensed). Standard stack means any development team can take over. Operations continue — without us.
What if you cancel?
Data export in open formats, documented interfaces, an orderly handover. Cancellation is a process, not a fight over your own data.
What if you want to self-host?
On-premise option for selected products, documented infrastructure for custom projects. Migration is a planned step, not a restart.
Asked concretely.
Does source-code handover mean we may only look at the code?
No. For custom development, the repository including history and documentation transfers into your ownership — contractually settled in the term sheet. You may modify, extend and pass it on.
Can we migrate an existing system out of the US cloud?
In most cases, yes. In the first conversation we assess which data and processes are affected, then plan the migration as its own work package — including parallel operation until everything is verified.
Is EU hosting slower or more expensive?
Technically, modern EU infrastructure is on par — what matters is the software's architecture. Any operating-cost differences are marginal compared to the risk of a lock-in.
Talk to us about your exit plan.
30 minutes that clarify where your system stands today — and what ownership would concretely mean for you.
Free · No obligation · Reply < 24h