> 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/readme.md). # Solcis: the open compliance layer for AI Solcis enforces your controls at runtime on every action your AI and software systems take, with independently verifiable evidence. ## Why Solcis exists Compliance and engineering teams use Solcis to enforce organisational controls on what their AI systems do, the AI-powered software, agents, and models they run, and to produce evidence for every action. The Solcis Policy Engine evaluates each action before it proceeds. Each decision is recorded as a compliance receipt in the evidence ledger in Compliance Studio. You deploy Compliance Studio and the Solcis Policy Engine in your infrastructure.
Solcis AI Compliance Infrastructure Overview
Solcis is for regulated organisations developing AI-powered software. Compliance Studio (governance) and the Solcis Policy Engine (enforcement) connect AI governance, control enforcement and engineering workflows. Engineers connect their AI-powered software to the Solcis Policy Engine (directly or through a gateway) and focus on developing new functionality. Compliance teams define and maintain controls in Compliance Studio; the Solcis Policy Engine enforces them. As requirements change, they update those controls without disrupting the engineering workflow. {% hint style="success" icon="face-thinking" %} The Solcis Policy Engine works like a firewall for AI actions, not network traffic. Engineers ensure it is connected correctly. Compliance teams use Compliance Studio to keep its rules appropriate, current and enforceable. {% endhint %} ## Four engineering problems solved How the Solcis Policy Engine was built for runtime policy enforcement in regulated, sovereign and edge AI deployments.
ProblemResultCover image

Speed

Compliance checks must run within the enforcement path of an AI system.

Result
Full check loop, including inference, under 200 ms.		cover-problem-speed.svgFour engineering problems solvedFour engineering problems solved

Scope

Controls must apply to the actions and context they govern.

Result
Routes to the right rules no matter the library size.		cover-problem-scope.svgFour engineering problems solvedFour engineering problems solved

Sovereignty

Regulated deployments need defined infrastructure and data boundaries.

Result
100% self-hosted, air-gapped with no data out.		cover-problem-sovereignty.svgFour engineering problems solvedFour engineering problems solved

Size

Enforcement must fit the systems where actions occur.

Result
Solcis Policy Engine in under 2 GB.		cover-problem-size.svgFour engineering problems solvedFour engineering problems solved
## Why Solcis exists Your board, your regulator or your procurement team has asked what your AI systems are allowed to do, what they did, and how you'd prove it. Three things about Solcis answer that. 1. **It evaluates actions before they proceed.** The Solcis Policy Engine evaluates each action your AI systems take against your controls, before it happens. 2. **Both products run in your infrastructure.** You configure components and models in Compliance Studio. Review the deployment documentation to understand the applicable boundary. 3. **Compliance Studio records the evidence.** Each action the Policy Engine evaluates creates a compliance receipt in the evidence ledger. Verifiers can use these records when assessing the deployment. ## The rest of this site
Cover image
Why SolcisWhy runtime control enforcement and verifiable evidence matter for AI-powered software.Why Solcishttps://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2FqBEWoI8EWLabOhd3pDS0%2Fcover-section-why-solcis.svg?alt=media&token=36514715-3170-491b-8318-87a2c6877aab
Understand SolcisHow Solcis works, where it fits in your architecture, and how it compares.Understand Solcishttps://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2Fr1oJRNjbgtRFsroIVGw7%2Fcover-section-how-it-works.svg?alt=media&token=bef2617c-fe06-4521-8885-c1df6d1daea1
Evaluate SolcisEverything you need to assess Solcis: functionality, security, threat model, and what leaves your deployment.Coming soonhttps://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2FyMjRTt9Sfx6oyJqgLW5Z%2Fcover-evaluate.svg?alt=media&token=45e8aec2-21af-42a1-b896-3aac11740005
Get SolcisThe two products (Compliance Studio and Solcis Policy Engine), where to get them, trial and pilot.Get Solcishttps://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2FaQZkfR48hlJRMKAsa6Ze%2Fcover-get.svg?alt=media&token=e90516f8-cdbb-4bec-9a76-17d3ed9f688e
Deploy SolcisInstall, secure and operate Compliance Studio and the Solcis Policy Engine, and connect your AI systems through the Solcis SDK, the Solcis Gateway or your own gateway, NVIDIA OpenShell or Microsoft AGT.Coming soonhttps://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2Fv1uLYvC00rVhLZ3CrISf%2Fcover-deploy.svg?alt=media&token=53c6a915-6754-4bee-bd2a-e8cb7553b1fe
ReferenceCore concepts, the AI regulatory landscape by market, glossary definitions, and frequently asked questions.Referenceshttps://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2FBWTHcjcFKjNOeqm1hT2A%2Fcover-reference.svg?alt=media&token=41051210-1e23-498a-a931-e840dad787d1
PartnersWhy Solcis is delivered through partners, who those partners are, what they do, and how to apply.Partnershttps://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2Fr1oJRNjbgtRFsroIVGw7%2Fcover-section-how-it-works.svg?alt=media&token=bef2617c-fe06-4521-8885-c1df6d1daea1
ResearchOur approach to research, partnerships, and the people behind our work.Coming soonhttps://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2FoKfYveSOniUA1h3oDZU2%2Fcover-section-research.svg?alt=media&token=c15e76ce-8f47-40d5-bb7d-69e40181aa7b
Legal CentreSolcis legal documents and policies.Legal Centrehttps://644912709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFwpyjzyaYY4oV7LJBr4N%2Fuploads%2FNvLagQuOfMEcWAt74ony%2Fcover-legal.svg?alt=media&token=f1472a40-553b-461a-a07a-f4404ba0d76a
*** {% columns %} {% column width="41.66666666666667%" %}
{% endcolumn %} {% column width="58.33333333333333%" %} #### **See Solcis enforce a control** A walk-through of a live deployment with one of our engineers. Book a demoBecome a partner {% endcolumn %} {% endcolumns %} Looking for a term? The [Glossary](/references/glossary.md) defines every one used in these pages. --- # 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/readme.md?ask=&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.