> 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/get-solcis/get-solcis.md).

# Get Solcis

Where to get Solcis, how to trial it, what it needs to run, and, for customers and partners, where it's going.

You've decided Solcis answers the question your board or regulator asked. This section covers what comes next: what you're buying, where you get it, how to try it first, and what it needs to run. It's written for the person who acquires Solcis, who's often not the person who deploys it.

Nothing here quotes a price or a contract term. Prices are agreed with you or your partner; terms are in the Compliance Studio Software Licence in the Legal Centre; the Policy Engine is licensed under FSL. This section explains the shape of what those documents describe.

## What's in this section

<table><thead><tr><th width="285.66668701171875">Page</th><th>Question it answers</th></tr></thead><tbody><tr><td><a href="/get-solcis/editions.md">Products</a></td><td>What are the two Solcis products, and how do they work together?</td></tr><tr><td>Licensing</td><td>How is the fee set, what do the licences give me, and how do I buy?</td></tr><tr><td>Where to get it</td><td>Which routes to acquiring Solcis are open today?</td></tr><tr><td>Working with a partner</td><td>What does a partner do, what stays mine, and how do I find one?</td></tr><tr><td>Trial and pilot</td><td>How do I try it before I commit, and what does a pilot look like?</td></tr></tbody></table>

## Before you start

Solcis is two products you run: Compliance Studio and the Policy Engine. Acquiring them gives you licences and deployment packages, not a service. Someone in your organisation, or a partner, deploys it.


---

# 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/get-solcis/get-solcis.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.