> For the complete documentation index, see [llms.txt](https://docs.solcis.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solcis.ai/design-principles/sovereign-by-construction.md).

# Sovereign by construction

Compliance Studio and the Solcis Policy Engine run in your infrastructure, under your certifications, with your model. Nothing leaves your deployment, because there's nowhere for it to go.

Compliance Studio and the Solcis Policy Engine are software you run, not hosted services. Every component runs in your environment. Prompts and tool calls remain there. You choose and host the model that performs inference checks. We share benchmarks and practical insights for your industry and operating jurisdictions. Sovereignty is not a deployment option. It is built into both products.

## Nothing leaves. Ever. Guaranteed

No data produced by, passed through or held in a Solcis deployment leaves your environment or your control, and we warrant it in the Software Licence. The Solcis Guarantee states it in full: what's covered, why we hold to it, what makes it true, how you check it, what backs it and what it doesn't cover.

<figure><img src="https://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2FypPWjzJ3MgCWy4vKoQ5O%2Fyour-environment.svg?alt=media&#x26;token=299ce06e-6d60-41a1-824d-936027003977" alt=""><figcaption></figcaption></figure>

Customers with demanding compliance obligations need control, not outsourced assurances. A hosted SaaS provider with annual SOC 2 certification and a roadmap of upgrades suits a different customer.

Solcis exists for organisations that keep AI compliance infrastructure within their own environment and control. That conviction comes from working alongside CISOs, risk leaders and compliance teams across the Gulf, Australia and New Zealand, Asia, India, the United Kingdom and Ireland, Canada, and South Africa.

## Legal reach, not distance

The sovereignty problem isn't where the servers are. It's who can be compelled to hand over what runs on them. A cloud operator is subject to its home jurisdiction's powers wherever its data centres sit. A region in your country, operated by a foreign entity, doesn't change that.

<figure><img src="https://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2FWOrpSGa4W28NAhgK13gs%2Flegal-reach.svg?alt=media&#x26;token=68befe86-ffaf-4b89-825a-fa506d903a2e" alt=""><figcaption></figcaption></figure>

Software you run on infrastructure you already govern sidesteps the question. There's no vendor in the path to compel. The regulator's question about a critical provider becomes a question about your own environment, which you can already answer.

## Where compute is

Governments and national programmes are building compute in-country, treating it as strategic infrastructure. Workloads that run on that compute have to be governed on it. The Solcis Policy Engine is built to run wherever the workload runs. That includes a public cloud region, a sovereign cloud, a data centre, or an air-gapped network with no route out. *Deploy Solcis › Deployment profiles* describes each.

Air-gapped isn't a reduced mode. Every component, including the model, runs inside the boundary. Compliance Studio licensing works offline. *Deploy Solcis › Installation* covers the air-gapped path alongside the connected one.

## Partner-hosted deployments

Advisory firms, managed service providers and platforms may run Solcis for clients on their own infrastructure and under their own certifications. The customer and partner choose that delivery model. The deployment remains theirs, and nothing leaves it to us. *Partners* describes the delivery models.

## Operating responsibilities

A typical Solcis Policy Engine container deployment takes 15 minutes. You operate, upgrade, and secure your deployment. Our documentation and your partners can support that work. *Deploy Solcis › Securing your deployment* and *Upgrade, rollback, recovery* cover those responsibilities.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.solcis.ai/design-principles/sovereign-by-construction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.