Resources
Resources
Writing, guides, case studies, release notes, roadmap and service status for teams putting enterprise AI under operational control.
What is actually here
5 of 7 resource types are empty, and each says why on its own page. The written material is substantial — it is just shaped like documentation rather than like a blog.
Documentation pages
9
Platform pages
25
Stated before you click
5 of these 7 are empty. Here is which.
A hub that routed cheerfully into six empty rooms would waste your afternoon. So the state of each resource type is on this page rather than discovered one click later, and the substantial material comes first.
- Documentationhas contentNine pages: introduction, quickstart, concepts, platform mechanics, integrations, governance, security and the API reference.Open
- GuidesemptyNone written. All six subjects a guide would cover are answered on their own pages, and that page says which.Open
- WritingemptyNo posts. Six arguments that would be posts are already published inside the product pages where each question comes up.Open
- Case studiesemptyNone, and no anonymised ones either. What exists instead is a fully documented fictional estate where every figure is checkable.Open
- ChangelogemptyNothing shipped publicly yet. The page publishes the standard entries will be held to, before the first one rather than after fifty.Open
- Roadmaphas contentAssembled from the gaps this site already admits elsewhere, so nothing on it is aspirational. No dates.Open
- Service statusemptyA statically exported page cannot show live status, and a row of green ticks would be the most misleading thing on the site.Open
Why the empty ones exist at all
Each says what will be in it, why it is not there yet, and what to read instead. That is more useful than a 404 and considerably more useful than three thin posts written to make a section look alive.
Resource types
7
in this section
With content
2
documentation and roadmap
Empty
5
each explains why
Dates promised
0
on any of them
The substantial material
The written material is not small. It is shaped like documentation.
Which is arguably the right shape for a product whose value is mechanical. A reader who wants to understand how governance attaches at a boundary is better served by the page explaining it than by writing about that page.
Getting started
3Read in order. Each one assumes the previous.
Introduction
OpsAI decides whether an action an AI system proposes is allowed, before it reaches a system of record, and files the decision either way.
Quickstart
The shortest path from nothing to a governed action: connect a system, send an event, write a policy, evaluate an action, read the trace.
Concepts
Definitions for the vocabulary the rest of the documentation assumes: what an AI system is here, what a policy compiles to, and how the pieces relate.
Platform
2How the mechanics work once the vocabulary is in place.
Platform
How connecting a system works in practice, what the inventory records about it, and how its activity becomes a trace and then an auditable record.
Integrations
Connect AI providers, agent frameworks, enterprise systems, data systems and identity providers, and receive events over webhooks and MCP.
Governance and security
2The two areas a reviewer opens first, so they are their own group.
Governance
Policy syntax and lifecycle, risk evaluation and approval flows, plus how accountability is modelled when an AI system is the thing doing the work.
Security
How authentication and authorization work, how secrets are held centrally rather than distributed, and what tenant isolation and data residency mean here.
Reference
1Returned to rather than read. Deliberately last.
The rest of this section
Every page here, including the empty ones.
Listed rather than hidden. A resources section that quietly dropped its empty pages would be tidier and would leave a reader wondering whether a changelog exists at all.
Blog
Writing on AI governance and agent security, on the infrastructure underneath it, and on what we are shipping. Engineering and research notes included.
Guides
How to govern AI agents, introduce AI permissions, implement human approval, audit AI actions, manage multiple models and discover shadow AI.
Case studies
Operational stories: the existing AI environment, the control gap, what OpsAI was asked to do about it, and what changed.
Changelog
Release notes by area, covering governance and connections through to risk, observability, integrations and developer tooling. Factual, not promotional.
Roadmap
What we are building now, what is next, and what we are still exploring. Without dates we cannot commit to.
Status
Live status for every OpsAI service, from the API and the policy engine through to MCP, the integrations and this documentation site.
Where to start
Start with the documentation. It is where the material actually is.
Nine pages, read in order or dipped into, and the introduction is the one place the positioning is unambiguous — the AI already exists and belongs to somebody else.