Log inBook a demo

Docs

How to build on Nebbos.

How to deploy a Pearl. How to define an approval graph. How to wire your existing systems into the substrate. The reference documentation engineering teams need to operate Nebbos in production.

Where you build

The six surfaces every deployment touches.

  1. Pearl

    The runtime a workload runs on. Reference for defining a Pearl, scoping its context, and deploying it into your Nebbos platform.

  2. Approval graph

    How Nebbos routes consequential actions through the humans who must sign off. Reference for graph structure, delegation, and audit contract.

  3. Integrations

    How the systems you already run wire into Nebbos — SIS, HR, ERP, CRM, ticketing, comms. Reference adapters and the shape of a custom integration.

  4. Ingest

    How your policy documents, procedures, and structured data get resolved into the Pearl's context. Reference for connectors, ingest cadence, and provenance.

  5. Audit ledger

    How every consequential action lands as an append-only event with a hash chain. Reference for the schema, retention, and export contract.

  6. SDK & API

    How your services talk to Nebbos. Reference for the MCP surface, the client SDK, authentication, and the tool-call shape.

Four steps. Same shape at every deployment.

Every Nebbos deployment follows the same shape: (1) scope the Pearl and its context — what department, what actions, what boundary; (2) wire the integrations that feed it and the systems it acts on; (3) define the approval graph — who signs off on what, and how delegation flows; (4) run it in shadow mode, measure, then promote. The docs are structured around this path. Read them in order or jump to the surface you're wiring right now.

Full reference is gated to signed engagements.

Deep reference material — schemas, replay tools, red-team playbooks, EU AI Act Annex IV artifacts — ships with the deployment package to teams under signed engagement. The public docs cover the shape of the work; the production docs cover the specifics. Reach out to engineering to open the full reference.

Ready to build?

Engineering runs the technical intake and confirms fit before the deployment package ships. One email opens that conversation.

engineering@nebbos.aiBook a demo
Docs · How to build on Nebbos — Nebbos