Skip to content

Sovereignty

Sovereignty & security

Sovereignty is not a hosting location. It's control over your infrastructure, data, models and access.

10 controls

Sovereignty in practice — 10 concrete controls

01
Infrastructure ownership
The platform runs on servers you own or rent. Not on ours.
02
European hosting
When you use cloud, it is a European provider of your choice.
03
Jurisdiction
You choose the provider, and with it the legal framework your data falls under.
04
Open source
Every component can be inspected, patched and run without us.
05
Portability
Kubernetes and open formats: move between on-prem and cloud without a rewrite.
06
Access control
Identity runs on your own identity provider. You decide who sees what.
07
Encryption
Data encrypted in transit and at rest, with keys and secrets managed on your side.
08
Operational access
Our engineers access your systems only as you allow, and that access can be withdrawn.
09
Vendor independence
No proprietary layer in the middle. No licence that holds your data hostage.
10
Exit strategy
Documented, as code, handed over. Leaving us is a planned step, not a project.

Architecture

An open architecture, layer by layer

  1. StoreS3-compatible object storage · Apache Iceberg · PostgreSQL
  2. ProcessApache Spark · Trino · DuckDB
  3. Transformdbt · SQLMesh
  4. OrchestrateApache Airflow · Dagster
  5. GovernApache Polaris · OpenMetadata
  6. SecureKeycloak · OpenBao
  7. AnalyseJupyterHub · RStudio · Apache Superset
  8. AIvLLM · open-weight models (Mistral, Llama, Qwen) · pgvector · Qdrant
  9. RunKubernetes · Argo CD · OpenTofu — on-prem, sovereign cloud or air-gapped

Every component can be replaced. Your architecture remains yours.

Exit

Reversibility, built in

  • →Your data remains in open formats.
  • →Your workloads run on standard infrastructure.
  • →Your models can be replaced.
  • →Your architecture does not depend on Datasider.

Everything is documented, as code, and handed over. Leaving Datasider is a planned step, not a project.

Security

Security is part of the architecture

  • →Encryption in transit and at rest, with keys on your side.
  • →Identity and access on your own identity provider.
  • →Secrets management.
  • →Network isolation.
  • →Air-gapped deployment option.
  • →Audit trail of access and actions.
  • →Operational access by our engineers only as you allow, revocable at any time.
  • →Backup and recovery defined with your team.

Regulation

Designed for regulated environments

Datasider deploys on certified providers and designs for the frameworks that apply to you: GDPR, HDS-certified hosting for health data, the CNIL health data warehouse framework, and the EU AI Act.

Exact controls depend on your deployment and are agreed with your security team.

Talk to an engineer