> ## Documentation Index
> Fetch the complete documentation index at: https://docs.subconscious.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Methods

> Full inference system via Ryvn, or OrangeLine only as a Docker container

There are two ways to run Subconscious in your infrastructure.

## Full inference system

The API Gateway plus OrangeLine, operated as one system. This is the recommended production path.

* Ryvn deploys the **API Gateway** into your **AWS, GCP, or Azure** account. That is the only supported way to run our gateway.
* **OrangeLine** runs on GPUs anywhere you can run a Docker container. Those GPUs do not have to be in the same hyperscaler as the gateway.
* Attach that compute to the gateway as model routes, whether the GPUs are in the same cloud account, on a NeoCloud or inference platform, or on your own local cluster or bare metal.

This path includes API keys, routing, usage, and **context pruning visualization and intelligence**.

Examples of OrangeLine GPU homes: AWS, GCP, Azure, Nebius, Lambda, CoreWeave, Together AI, Baseten, Modal, other NeoClouds, a local cluster, or bare metal. If you have GPUs we have not named, we can work with that.

See [Ryvn](/on-prem/ryvn/overview) and [Configurations](/on-prem/deployments/configurations).

### Walkthrough

1. Your FDE confirms AWS, GCP, or Azure as the gateway account, plus where OrangeLine GPUs will run.
2. Ryvn stands up the gateway environment in that account. A Ryvn Agent in the cluster pulls desired state over outbound HTTPS.
3. The API Gateway installation comes up. You set approval, maintenance-window, and release-channel policy.
4. OrangeLine is deployed on the chosen GPUs (same cloud, another provider, local cluster, or bare metal).
5. You add model routes on the gateway that point at those workers.
6. You validate dashboard access, a test request, and at least one coding agent.
7. Handoff covers day-two ownership, monitoring, and how updates are approved.

## OrangeLine only

The simpler path: we issue **registry credentials** for the OrangeLine image, and you run that container on any GPU cloud, local cluster, or bare-metal host.

Use this for trials, or if you already have a gateway. There is no Ryvn install and no Subconscious API Gateway.

OrangeLine still serves models. **You will not get context pruning visualization and intelligence** without our gateway.

See [OrangeLine](/on-prem/inference-runtime/overview).

### Walkthrough

1. Your FDE entitles your org and issues registry credentials for the OrangeLine image.
2. You pull the image and run it on your GPUs, wherever they live.
3. You point your own gateway or clients at the OrangeLine endpoint.
4. When you want keys, routing, usage, and pruning visualization, move to the full inference system.

## Choosing

Choose the **full inference system** when engineers will call a Subconscious-hosted endpoint and you want gateway features in your cloud.

Choose **OrangeLine only** when you are trialing the runtime, or you already operate a gateway and only need the GPU container.

Do not apply the gateway Helm chart yourself. The supported gateway path is Ryvn BYOC in AWS, GCP, or Azure.

## Related pages

* [How it works](/on-prem/how-it-works)
* [OrangeLine](/on-prem/inference-runtime/overview)
* [API Gateway setup](/on-prem/api-gateway/setup)