Origin Docs
Getting Started

Choose Your Path

Persona-based routing for ORGN — developers (CDE/Studio), integrators (Gateway API), and compliance evaluators (trust + Scanner verification).

Pick the path that matches your job. Each section links to a ≤15 minute first-success doc sequence. You do not need all four products on day one.

Developer

You want to write code with AI agents inside a confidential environment — desktop IDE or browser workspace.

Pick your surface

PreferenceProductWhy
Daily-driver IDE, local folders, cloud worktreesORGN CDEVS Code fork, id-orgn sign-in, Origin Agent, Git worktrees
No install, repo import, team collaborationORGN StudioProjects, tasks, worktrees, Shannon code security

CDE Quickstart

Install, sign in with id-orgn, open local or cloud project.

Studio Quickstart

Import a repo, start a worktree, collaborate with agents.

  1. Sign in with id-orgn — Studio UNLOCK or CDE Continue with id-orgn (SSO)
  2. Open or import a project (CDE install or Studio projects)
  3. Open a worktree and use Origin Agent — see Glossary — worktree, session
  4. Optional: run Code security on your repo (vulnerability scan — not ORGN Scanner)

Sign in with GitHub at id-orgn is the usual way to create your ORGN account. The ORGN GitHub App is a separate step when you need repository access for import, clone, or push — see Teams — GitHub integration.

Open apps

Integrator

You want to call AI models from an application, agent framework, or CI pipeline with governed routing and optional hardware attestation.

Start with Gateway

ORGN Gateway exposes an OpenAI-compatible API at https://api.gateway.orgn.com/v1.

Gateway Quickstart

Create an API key, send first chat completion, pick TEE or ZDR model.

Authentication

API keys vs console SSO — separate credentials.

Model catalog

TEE (near_*, phala_*) vs ZDR (vercel_*) execution types.

  1. Sign in to gateway.orgn.com with id-orgn (manage keys in console)
  2. Create an sk-ollm-* API key — API keys
  3. Send a test request with a TEE model if you need attestation (phala_deepseek_r1, near_qwen3_30b, etc.)
  4. Verify the receipt in Scanner — proof is independent of Gateway UI
  5. Integrate with OpenAI SDK, Vercel AI SDK, or API reference

Model IDs use underscores, not slashes.

When to read trust docs

Integrators often need a one-paragraph answer for security reviewers: TEE routes produce hardware attestation; ZDR routes are contractual zero retention without attestation receipts. Canonical detail: Trust model — Execution environments.

Open apps

Compliance

You are a security engineer, auditor, or procurement lead evaluating ORGN for regulated work — finance, healthcare, defense, or high-IP commercial environments.

You need to answer: What can ORGN prove? What crosses the boundary? What is our responsibility?

Do not start with a quickstart

Start with the trust narrative, then verify one attestation yourself.

Trust model

Canonical security story — TEE, ZDR, Trust Domains, data boundaries.

Verify a request

Independently confirm TEE inference attestation in Scanner.

Enterprise

VPC, air-gap, FAR 9.5 OCI positioning (not legal certification).

  1. Read Trust model — four-layer stack, shared responsibility, identity boundary
  2. Disambiguate terms in Glossary — Trust Domain (not enclave), Scanner vs code security
  3. Walk through Scanner verify with a real TEE request ID
  4. Review Pricing and Teams for commercial structure
  5. If federal or air-gap: Enterprise + legal review of OCI disclaimer

Documentation describes architecture and common procurement patterns. It is not a compliance certification. Your CO, counsel, and AO determine fit for your contract.

Evidence map

QuestionDoc
Does ORGN see my code in a workspace?Trust model — Data boundaries
Was inference in a real Trust Domain?Scanner verify
Vulnerabilities in my repo?Studio code security
Who signs in and how?SSO
Sandbox attestationCDE attestation, Scanner attestation

Open apps

Still exploring?

→ Stack overview — how CDE, Studio, Gateway, and Scanner compose

→ Getting started home — product cards and platform links

Getting Started

Start with ORGN — the Confidential Agentic Stack. Route to CDE, Studio, Gateway, or Scanner, then pick a persona path.

Stack Overview

The four-layer ORGN stack — CDE, Studio, Gateway, and Scanner — and how they compose a verifiable confidential development platform.

On this page

Pick your surfaceRecommended sequenceOpen appsStart with GatewayRecommended sequenceWhen to read trust docsOpen appsDo not start with a quickstartRecommended sequenceEvidence mapOpen appsStill exploring?