OPENRIFT // DOCS // PUBLIC LIBRARY

Docs.

A reference library for clients in active engagements and partners building alongside us. Openrift is bespoke, so the public docs are deliberately a thin slice — concepts, security, and the surfaces you need to brief us well. Deeper material ships with your deploy.

01 / LIBRARY

Six shelves.

All in active drafting
01Drafting

Getting started

What Openrift is, what it isn't, and how a Discovery week actually runs. The shape of a Deploy. What a Run retainer covers.

  • The three-step model
  • What a kickoff looks like
  • Glossary
02Drafting

Integrations

The tools we connect to out-of-the-box. OAuth flows, scopes we request, what an agent can and can't do inside each tool by default.

  • Stripe, Xero, HubSpot, Linear
  • Slack + WhatsApp Business
  • Custom integration scoping
03Drafting

Agent architecture

How agents are scoped, sandboxed, and supervised. The trust ladder. How tool calls are gated. What lives in working memory vs persistent state.

  • Tool-call gating
  • Working memory model
  • Multi-agent coordination
04Drafting

Security

SOC 2 Type 1 details, encryption posture, workspace isolation, audit logs, and the agent action boundary. Compliance docs available on request.

  • SOC 2 Type 1 report
  • Encryption at rest + in transit
  • Audit log access
05Drafting

Deployment guide

The internal playbook we run during Deploy week, lightly redacted. Helps client tech leads brief their team and prepare access ahead of kickoff.

  • Pre-deploy checklist
  • Access requirements
  • Week-by-week breakdown
06Drafting

API

For technical partners — REST endpoints to inspect agent state, replay actions, and query the audit log from your own tooling. Bearer-token auth.

  • Auth + scopes
  • Agent state endpoints
  • Audit log query

Coming soon — request early access via the CTA below.

// EARLIER, IN PERSON

The docs ship with you, not before you.

Book a Discovery call. The relevant docs land in your shared workspace at kickoff, scoped to what you're actually deploying. No 400-page reference no one reads.