> ## 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.

# Onboarding

> From kickoff to pilot users on the Subconscious Inference System

Onboarding turns the evaluation plan into a working customer-hosted deployment. A Subconscious FDE works with your technical champion to choose a mode, stand up the stack, connect pilot users, and hand off day-two operations.

Use [Methods](/on-prem/deployments/methods), [Configurations](/on-prem/deployments/configurations), and [API Gateway setup](/on-prem/api-gateway/setup) for the mechanics.

## Summary

* **Kickoff to first pilot use**: usually about **1-2 weeks**, assuming customer technical resources are available.
* **Technical champion effort**: usually less than **8 hours** of focused configuration time when the environment is ready.
* **Admin training**: usually less than **1 hour**.
* **Broader team training**: usually less than **1 hour**.
* **Communication channel**: Dedicated Slack channel.
* **Onsite support**: available when it helps accelerate setup.

Strict change management, private registries, custom networking, or new GPU procurement can extend the timeline. OrangeLine-only trials are usually shorter.

## Stakeholders

* **Subconscious**: CEO and assigned FDE.
* **Customer executive sponsor**: Owns business value, rollout priority, and commercial alignment.
* **Customer technical champion**: Drives deployment planning, environment readiness, and technical coordination.
* **Core admin team**: Manages API Gateway access, API keys, routes, limits, monitoring, and day-two operations.

## 1. Kickoff

Kickoff aligns the people, communication channels, and success criteria before deployment work begins.

* **Ceremony**: 30 min meeting or async.
* **Purpose**:
  * Establish communication channels, expectations, and executive sponsorship.
  * Confirm implementation timeline and success criteria from evaluation.
* **What happens**:
  * A dedicated Slack channel or customer-approved support channel is created.
  * A Subconscious FDE becomes the primary onboarding point of contact.
  * The customer identifies the technical champion, admin team, security reviewers, and pilot sponsor.
  * The team confirms success criteria, timeline, and responsibilities.

## 2. Deployment planning

* **Ceremony**: 60 min meeting plus async follow-up.
* **Purpose**: Choose the mode and the GPU home.
* **Topics to define**:
  * Full inference system vs OrangeLine only.
  * For the full system: AWS, GCP, or Azure as the gateway account; Ryvn environment, approvals, and maintenance windows.
  * OrangeLine GPU location: same cloud, NeoCloud, inference platform, local cluster, or bare metal.
  * Endpoint strategy, DNS, TLS, and network path to workers.
  * Observability, logging, alerting, and support access expectations.

See [Methods](/on-prem/deployments/methods) and [Ryvn](/on-prem/ryvn/overview).

## 3. Deploy

* **Ceremony**: 30-60 min meeting plus async follow-up.
* **Full inference system**: Ryvn deploys the API Gateway. OrangeLine is stood up on the chosen GPUs and attached as model routes.
* **OrangeLine only**: pull the image with the credentials we issue and run it on your GPUs.
* **Customer responsibilities**: provision or approve GPU and (for the full system) cloud-account access; approve the Ryvn Agent install when using the gateway.
* **Subconscious responsibilities**: guide the install, validate health, and prepare admins for setup.

See [Configurations](/on-prem/deployments/configurations).

## 4. API Gateway setup and admin training

Skip this step for OrangeLine-only. For the full system, see [API Gateway setup](/on-prem/api-gateway/setup).

* **Ceremony**: 30-60 min meeting plus async follow-up.
* **What gets configured and taught**: admin users, API keys, model routes to OrangeLine, limits, test requests, usage, monitoring, and upgrade expectations.

## 5. Coding agent integration and team training

* **Ceremony**: One 30 min live training session, with optional recording and written setup material.
* **Purpose**: Point coding agents at the customer endpoint (our gateway, or OrangeLine directly if you brought your own).
* **Topics**: base URL, keys, model slugs, OpenAI- and Anthropic-compatible configuration, limits, and support.

Rollout usually starts with a small pilot group.

## 6. Handoff

* **Ceremony**: 30 min meeting with stakeholders for sign-off.
* **Sign-off checklist**:
  * The chosen mode is running and a test request succeeds.
  * For the full system: admins can operate the API Gateway; keys, routes, and limits work; at least one coding agent is connected.
  * Monitoring and logging ownership is clear.
  * Support and escalation paths are understood.
  * Upgrade and rollback expectations are documented, including the pruning-visualization caveat for OrangeLine-only.

After handoff, the relationship continues through [Customer success](/on-prem/integration-journey/customer-success).