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.
Walkthrough
- Your FDE confirms AWS, GCP, or Azure as the gateway account, plus where OrangeLine GPUs will run.
- Ryvn stands up the gateway environment in that account. A Ryvn Agent in the cluster pulls desired state over outbound HTTPS.
- The API Gateway installation comes up. You set approval, maintenance-window, and release-channel policy.
- OrangeLine is deployed on the chosen GPUs (same cloud, another provider, local cluster, or bare metal).
- You add model routes on the gateway that point at those workers.
- You validate dashboard access, a test request, and at least one coding agent.
- 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.Walkthrough
- Your FDE entitles your org and issues registry credentials for the OrangeLine image.
- You pull the image and run it on your GPUs, wherever they live.
- You point your own gateway or clients at the OrangeLine endpoint.
- When you want keys, routing, usage, and pruning visualization, move to the full inference system.