> 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/who-is-it-for.md).
# Who is it for
Regulated organisations and governments that run their own infrastructure, the people in them who answer for AI, and the partners who deliver it.
Solcis is for organisations that have to answer for what their AI systems do, and that run their own infrastructure. In practice that means regulated enterprise, government, critical infrastructure, and defence, and advisory, audit, and delivery firms that work with them.
## Organisations
**Regulated enterprise.** Banks, insurers, asset managers, health providers, telecommunications carriers and utilities. Organisations with a regulator, a control library, an internal audit function and an external assurance relationship. They already govern their systems and want their AI systems governed the same way.
**Government.** Agencies deploying AI systems whose decisions affect citizens directly. They need in-country infrastructure, data that never leaves the jurisdiction, and a record a parliamentary committee or ombudsman can examine.
**Critical infrastructure and defence.** Operators for whom hosted software is ruled out by policy, and for whom air-gapped deployment is a requirement rather than an edge case.
What these organisations share is a buying position. They will run Solcis themselves for three reasons and buy it for a fourth.
| They want | Because |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- |
| Compliance scope set by risk, not latency | A control that adds time to every call gets scoped down. One that runs next to the AI system doesn't have to be. |
| Sovereignty over data, models and hosting | Prompts, tool calls and traces are the payloads they can't let cross a boundary. |
| Security they control | They already hold their own certifications and have no interest in importing a vendor's posture. |
| Compliance software that makes them faster | They have AI systems they can't deploy and a backlog gated on a risk answer nobody can give. Controls are what unlock it. |
## People
Solcis is used by six kinds of people. Each has a section of these pages written for them.
| Who | What they need | Start with |
| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| **CISOs, chief risk officers, boards** | To know what their AI systems are allowed to do, what they did, and how to prove it | *Why Solcis*, then *Evaluate Solcis* |
| **Compliance, risk and governance teams** | To express the controls they already own as policies their AI systems are held to, and to read the results in Compliance Studio | *How it works › Controls to policy* and *Policy lifecycle* |
| **AI platform and engineering teams** | To connect agents, frameworks and tools to the Solcis Policy Engine, and to run the deployment in production | *Deploy Solcis › Quickstart*, then *Connect your agents* |
| **Infrastructure, security and operations teams** | To deploy, secure and operate Compliance Studio and the Solcis Policy Engine in their own environment, including air-gapped | *Deploy Solcis › Deployment profiles* and *Securing your deployment* |
| **Internal auditors, external assurance providers, regulators** | To verify the evidence ledger without help from the people who run the system | *How it works › Evidence and verification*, then *Verification and assurance* |
| **Partners** | To deploy and support both products, and configure and integrate Compliance Studio, for clients, often across many environments | *Partners*, visible after sign-in |
Most pages are written for two readers at once, an engineer and a compliance practitioner, because governing AI systems is one job seen from two sides. Every page defines its terms from both directions.
## Partners
Solcis is delivered through partners as much as by us. Advisory firms author controls in Compliance Studio and run assurance over its evidence ledger. Systems integrators and managed service providers deploy, integrate and operate them for clients, on the client's infrastructure or their own. Audit and assurance practices get something they've not had for AI. They get a record of every action their AI systems take that they can test independently of whoever built or runs the system.
If you advise, audit or assure the organisations above, the [*Partners*](https://docs.solcis.ai/partners/) section is for you.
{% columns %}
{% column width="41.66666666666667%" %}
{% endcolumn %}
{% column width="58.33333333333333%" %}
#### **Deploy Solcis for your clients**
Consultants, advisers and auditors run Solcis on their clients' infrastructure and verify its evidence independently.
Become a partnerQualify an opportunity
{% endcolumn %}
{% endcolumns %}
## Markets
Solcis serves regulated industries and government across the Gulf, Australia and New Zealand, Asia, India, the United Kingdom and Ireland, Canada, and South Africa. Many readers work in English as a second or third language, and these pages are written with that in mind.
Solcis isn't tied to any of these markets by its architecture. It runs where there's compute and someone to run it. The list reflects where sovereignty has become a procurement requirement rather than a preference.
## Who it isn't for
Solcis isn't for compliance or security professionals seeking a vendor-hosted software as a service (SaaS) service. There is no version that we run for you. If you want to sign in, hand over your data and controls, and let a vendor operate compliance, other options fit that model. Solcis requires you to run the software yourself and retain control of your environment; containerised deployment is a first-class citizen, built for exactly that.
---
# 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/who-is-it-for.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.
