> 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/partners/partners/partner-overview.md).
# Partner overview
Why Solcis is delivered through partners, who those partners are, and what the work involves.
{% hint style="info" %}
**About this section.** The Partners section is partner enablement material, not product documentation. Commercial statements here, including anything about positioning, licensing or delivery models, are subject to your partner agreement. Where the two differ, the agreement applies.
{% endhint %}
Solcis enforces an organisation's controls on what its AI systems do: the Solcis Policy Engine evaluates each action on the action path, and Solcis Compliance Studio holds every decision in an evidence ledger a third party can verify. Both Solcis products run in the customer's infrastructure, under their certifications, with a model they host. We don't host either for them.
That one property decides the shape of this programme. Software the customer runs has to be deployed, connected to their AI systems, and kept running, and the controls it enforces have to be written by someone who understands both the client's obligations and their systems. Most of that work happens at the client, not at Solcis, which is why partners are how Solcis reaches production rather than an addition to how it does.
## Who our partners are
| Partner type | What you deliver | Typical firm |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Implementation and advisory | Deployment, integration, controls authoring, and readiness for assurance over the evidence ledger. | Consultancies, advisory and audit practices, systems integrators. |
| Managed service | Operating a client's deployment after go live, often across many client environments. | Managed service providers, sovereign cloud operators, national technology partners. |
| Technology distributor | Making Solcis available through your technology catalogue, reseller network, or procurement channel. | Cloud marketplaces, value-added distributors, technology distributors, and regional reseller networks. |
| OEM and embed | Solcis Policy Engine enforcement inside your own product, platform or service offering. | Software vendors, platform operators. |
| Technology | Adapters, Model Context Protocol (MCP) servers, and connectors that let your tools sit correctly inside the enforcement path, or connect to Solcis Compliance Studio (GRC, SIEM, ticketing). | Agent platform, security, and governance, risk and compliance (GRC) vendors. |
A firm can hold more than one of these. An advisory practice that authors controls for a client often ends up operating the deployment as well, because the client has nobody to hand it to.
## The work
Five activities make up almost every engagement. Which ones you take depends on the partner type and on what the client can do themselves.
1. **Deploy.** Install Solcis Compliance Studio and the Solcis Policy Engine (and the Solcis Gateway where used) in the client's cloud, data centre, or air-gapped network, and secure it to their standard.
2. **Connect.** Put the Solcis Policy Engine on the client's action path, at model, tool and MCP endpoints. Use the Solcis SDK to build it into the application, or a gateway to put it in the traffic path: the client's own gateway or the Solcis Gateway. Where the client runs NVIDIA OpenShell or Microsoft AGT, Solcis Compliance Studio can supply them enforcement policies and collect their decisions and evidence. A Policy Engine with no action path routed through it enforces nothing. See *Why Solcis › Where Solcis enforces* for how the options compare.
3. **Author controls.** Express the controls the client already owns as rules and a runtime policy in Solcis Compliance Studio, keeping the lineage to the framework requirement each one satisfies.
4. **Verify.** Show the client, their internal audit function, and their external assurance provider how to check the evidence ledger held in Solcis Compliance Studio without help from the people who run the system.
5. **Operate.** Run the deployment, manage policy change and escalations in Solcis Compliance Studio, and upgrade on the client's schedule.
## Where the demand is
Our clients are regulated organisations and governments that run their own infrastructure: banks, insurers, health providers, utilities and telecommunications carriers, government agencies, and critical infrastructure and defence operators. They are concentrated in the Gulf, Australia and New Zealand, Asia, India, the United Kingdom and Ireland, Canada, and South Africa, which is where sovereignty has become a procurement requirement rather than a preference.
The buying trigger is consistent. A board, a regulator, or a client has asked what the organisation's AI systems are allowed to do, what they actually did, and how that can be proven. Until there is an answer, AI systems that are built and tested cannot go to production. *Why Solcis › Who is it for* sets out the reader groups and markets in full.
## What we look for in a partner
* Delivery capability in the client's own infrastructure, including cloud, on-premise, and air-gapped environments.
* Literacy in both directions: engineers who can reason about controls, or compliance practitioners who can reason about tool calls and agent frameworks. Most engagements need one person who can hold both.
* Standing with regulated or government buyers in at least one of our markets.
* A delivery team, not only a sales relationship. Solcis is not something a client can be left to switch on alone.
## Next steps
New to Solcis? See [Become a partner](/partners/partners/become-a-partner.md) for what we look for and how to apply. Already a partner? Register each client opportunity with us.
Register an opportunityBecome a partner
---
# 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/partners/partners/partner-overview.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.