Prove you can leave your hyperscaler.
Sovrift’s agents read your Terraform, Kubernetes manifests and billing exports, then produce a cost twin, a gap analysis and a tested exit plan toward Scaleway, OVHcloud and Outscale. Verified migration merge requests are coming next.
1xManaged PostgreSQL
aws_dynamodb_table
Four modules. One deliverable: an exit you can prove.
Each module works from your actual estate (IaC, manifests, billing), not from a questionnaire.
- Example
38x compute
6x databases
14x buckets
9x functions
Discovery
Ingests Terraform, Kubernetes and Helm manifests, AWS CUR or GCP billing exports. Agents classify resources and infer workload boundaries and criticality.
- terraform
- helm
- k8s
- aws-cur
- gcp-billing
- Example
Cost twin. Illustrative figures. Not a customer. Cost twin per month Δ AWS (current) €38,400 Scaleway €27,900 −27% OVHcloud €29,300 −24% Outscale €33,100 −14% - Compute rightsized from p95 usage−€5,120
- Managed Kubernetes control plane−€440
- Egress and NAT−€5,460
- DynamoDB → managed PostgreSQL+€520
Cost twin
Prices your real estate on Scaleway, OVHcloud, Outscale and S3NS, rightsized from observed usage. Every delta comes with its explanation.
- Example
aws_dynamodb_table
scaleway_rdb_instance
aws_lambda_function
scaleway_container
aws_s3_bucket
scaleway_object_bucket
Gap analysis
Service-by-service mapping. Flags what has no equivalent and proposes a replacement: DynamoDB → managed PostgreSQL, Lambda → containers.
- Example
Exit plan · rev. 7
- DORA
- SecNumCloud
- HDS
- Cloud Act
Compliance & exit plan
Maps workloads to DORA, SecNumCloud, HDS and Cloud Act exposure, then generates a DORA exit plan from your real IaC.
Verified migration merge requests
Target-cloud Terraform, opened as merge requests after passing the checks below.
Continuous exit-readiness
Exit plan regenerated on every infrastructure change, quarterly exit drills, drift alerts.
FinOps on European clouds
Cost tracking and rightsizing on Scaleway, OVHcloud and Outscale once you’ve moved.
Generated, then checked. Never auto-applied.
Models handle the long tail well and the common case unreliably. So the common path is deterministic, the model only handles what rules can’t, and nothing reaches you without passing the checks your platform team would run.
Parse IaC
Terraform modules and Helm values become a typed resource graph.
Deterministic mapping
Rule-based translation for the common path. Same input, same output.
LLM for the long tail
Only for resources rules can’t map, with the graph as context.
Checks
Every generated change runs through:
- terraform validate
- terraform plan
- tflint
- checkov / opa
- cost re-check
- sandbox apply
Repair loop
Failures go back to the agent with the error output. Three attempts, then a human takes over.
Merge request
Diff, check results, cost delta and a confidence score. Your team reviews and merges.
fail → repair · max 3 → human
Sovrift never runs apply against your accounts.
What Sovrift can and can’t touch.
Built for teams that answer to a regulator: read-only by default, no US model endpoints, and a full trail of what the agents did.
Read-only by design
We ask for read-only cloud credentials. Sovrift never writes to your accounts.
No US LLM endpoints
No IaC or billing data is sent to US LLM endpoints.
Self-hosted option
Sovrift can run in your own VPC when your data must stay there.
Every AI action logged
Agent actions are logged with their inputs, model and outcome, so you can audit how a conclusion was reached.
From first call to exit plan.
Exit exposure call
30 min · free
Where you run, what regulates you, and what an exit would touch.
You leave knowing whether an assessment makes sense and what read-only access it needs.
Cost twin & gap summary
5 working days
You grant read-only access. We return a first cost twin and gap summary.
Every price delta and every missing equivalent is explained, service by service.
Sovereign Exit Assessment
Fixed price
The full analysis across all four modules. Key deliverable: your DORA exit plan, generated from your real IaC.
The exit plan is traceable to your Terraform, resource by resource.
Fixed-price assessments, then an optional subscription.
Become a design partner.
We are taking three design partners. You get the Sovereign Exit Assessment at a reduced price; we get your feedback and, with your approval, a case study.
- Sovereign Exit Assessment at a reduced, fixed price
- Direct line to the founders while the product takes shape
- Case study published only with your written approval
Prefer to talk first?
Book an exit exposure callQuestions engineers and CISOs ask first.
What data do you need?
Read access to your IaC repositories (Terraform, Helm, Kubernetes manifests), a billing export (AWS CUR or GCP billing export) and read-only cloud credentials for discovery. No application data and no database contents.
Do you write to our cloud?
No. Credentials are read-only and Sovrift never applies changes. Migration code (coming next) arrives as merge requests that your team reviews and merges.
Which clouds do you support?
Sources: AWS and GCP. Azure is not supported yet. Targets: Scaleway, OVHcloud and Outscale, with S3NS also priced in the cost twin.
Which models do you use?
Mistral and open-weight models served through Scaleway. No IaC or billing data is sent to US LLM endpoints. With the self-hosted option, inference runs inside your environment.
Is this only for regulated companies?
No. DORA, SecNumCloud and HDS make exit plans mandatory for some. The cost twin and gap analysis help anyone weighing a move to a European cloud, and the Data Act removes switching charges for everyone from January 2027.
How is this different from a consulting firm?
A consulting report is accurate on the day it’s written. Sovrift derives every number from your actual IaC and billing, explains each one, and is built to regenerate the exit plan as your infrastructure changes (coming next). We work hands-on with design partners, but the output is reproducible.