Skip to main content

Choose your path

Culvii's docs are written for two readers. Pick the path that matches what you'll actually do.

I'm a developer​

You'll write code using Culvii Kit, run the CLI, and ship workflows.

Start here:

  1. Get Started — install the kit, log in, and run your first workflow end to end.
  2. Concepts — read these in any order, but Architecture overview, Authentication, and Primitives at a glance before anything else.
  3. SDK reference and CLI reference — once you know the shape of things, these are the source of truth.

If you'll be governing the agents you build, also read the Operator's Guide — it's short.

I'm an operator​

You'll govern agents and workflows from the Console. You may or may not write code.

Start here:

  1. Operator's Guide → Welcome — what the operator surface does and what's in scope for v1.
  2. Concepts → Governance is the differentiator — why the product is shaped the way it is.
  3. Operator's Guide → Console tour — the actual UI, page by page.

You don't need to read the SDK or CLI references. If you find yourself there, something has gone sideways.

I'm both​

The two paths overlap. Read the developer track first if you'll be writing code, then come back to the operator track for runtime work. The Concepts section is shared between the two and worth the time either way.

I'm evaluating Culvii​

You want to know whether this kit fits your team before you commit any code.

Read, in order:

  1. What Culvii is — positioning and what we're opinionated about.
  2. How the pieces fit — the architecture in one diagram.
  3. Concepts → Governance is the differentiator — the strategic case.
  4. Versioning and status — what's stable, what's not, and what's on the roadmap.

That's enough to decide whether Culvii belongs in your stack. If the answer is yes, talk to us — see Get access.