Resources
Guides, API documentation, security details, and release notes. Start with the first-week path if you are new.
Start here
Four steps, roughly one per day. Most teams have a working inventory on day one and a governance model by the end of the week.
Link one platform, read the inventory. Nothing changes yet.
Promote the assets the team depends on. Leave the rest personal.
Two or three people. More than that and the queue stops moving.
Push one asset and watch it land. That is the whole loop.
Everything we have published, grouped by what you are trying to do.
Nine walkthroughs from first connection to approval chain design.
LearnInventory, governance, and deployment explained end to end.
LearnWhat each of the four roles can and cannot do, in one table.
BuildEndpoints, authentication, pagination, errors, and rate limits.
BuildTyped Python and TypeScript clients, regenerated each release.
BuildTen event types delivered as they happen, signed and retried.
OperateStream the audit log into Splunk, Datadog, or any HTTPS collector.
OperateAccess control, data handling, and what we have not built yet.
OperateUptime by component, open incidents, and how we measure it.
OperateWhat shipped and when, plus our breaking-change policy.
DecideSeats, credits, and exactly what counts as billable.
DecideDPA, subprocessor list, and transfer mechanisms.
For evaluators
These four pages answer most questionnaires. If something is missing, ask — we will answer directly rather than send you a portal link.
Build on the control plane
Everything visible in the interface is available through the API, because the interface uses the same endpoints you do. There is no private path that makes our client faster or more capable than yours.
Connect one workspace and see every skill, rule, and memory your team has in play — in about ten minutes.
No credit card. Works with what you already run.