Glossary · Sovereignty

Data residency

Data residency on KERNSTACK means a project runs in one declared European zone on bare-metal infrastructure KERNSTACK operates itself — not in a hyperscaler region rented underneath — and every environment of the project answers the residency question the same way.

NoSQL TablesObject Buckets
Talk to us Read Technical Documentation → Software Lifecycle Cloud →

Definition: Data residency

Data residency on KERNSTACK means a project runs in one declared European zone on bare-metal infrastructure KERNSTACK operates itself — not in a hyperscaler region rented underneath — and every environment of the project answers the residency question the same way.

Residency as a property of the project

On assembled clouds, residency is per-service homework: this database in Frankfurt, that bucket accidentally in Oregon, a model API whose subprocessors list runs to a page. On KERNSTACK the zone is a property of the project target: functions, tables, buckets, indexes, and workflows run there, so the answer to a DPO’s question is one sentence with one operator in it.

What residency does not claim

Residency is not sovereignty theatre. It does not make a US parent company European, and it does not stop your own code from calling an API in another jurisdiction — the workflow that emails through a US provider is visible in your stack precisely so that choice stays conscious. What it removes is accidental geography: nothing runs somewhere because a default put it there.

FAQ

Frequently asked questions

In the project’s European zone, on bare metal KERNSTACK operates — named infrastructure, not a region of a US hyperscaler rented beneath a European flag. The zone applies to every resource the project declares.

Yes. Preview targets and agent-<id> environments are instantiations of the same project in the same zone, so rehearsal data never quietly lives under different geography from production.

It can — visibly. Outbound calls are your functions’ and workers’ ordinary HTTPS, declared in your code for your reviewers. Residency governs where the project runs, not which conscious integrations you choose.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Category PillarThe Software Lifecycle CloudHow KERNSTACK unifies infrastructure, code, intelligence, and collaboration.Platform · DataBucketsObject storage with presigned uploadPlatform · DataTablesServerless key-value and document tablesGlossary · PricingCreditA credit is KERNSTACK’s single unit of metering: compute costs 0.01 credits per GiB-second, storage 0.04 credits per GB-hour, egress 9.00 credits per GiB, and catalogue inference is priced per token or image in credits. One balance pays for everything a project does.Glossary · AccessEnvironment isolationEnvironment isolation is the separation between a project’s targets — default (production), preview targets, and agent-<id> environments — each instantiating the same stack.json with its own data, routes, and keys, so work in one cannot touch another.Glossary · ArchitectureProject graphThe project graph is the whole system a KERNSTACK project declares in stack.json — gateway routes, functions, workers, tables, buckets, search indexes, workflows, and secrets — instantiated per environment target and changed only through reviewed plans.

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →