The platform is sold as offerings in three groups. The self-serve group is the developer door: the plugins, a bundle of them, and a free plugin that any agent can use. The assessment group is the compliance and executive door: an enterprise assessment, a quick scan that leads into it, and a standalone certification. The third group is a single deliverable, the Architecture Pack. Every offering reads the same governed knowledge and the same engine, which is what lets them compose. No price appears in this document, because prices move and the pricing page is their single source.
Each offering is described the same way: who it is for, what you get, how it composes with the rest, and the evidence a reader can open.
Knowledge Graph #
#Who it is for. Developers and architects who want an agent, or themselves, to ask architecture and governance questions in plain language and get answers grounded in a governed body of knowledge, with the provenance attached.
#What you get. Search over the governed knowledge base; lookup of an entity and the things it depends on and relates to; the governance constraints that bear on a decision; and the evidence behind a particular claim. It works from the first call on the shared corpus across the seven governance domains, and it reads an organization's own knowledge, kept private to that organization, once another offering has loaded it. It only reads; it changes nothing it draws on. A free developer tier carries a generous monthly allowance. Free-tier queries return results from the client-safe tier of the knowledge base.
#How it composes. The Knowledge Graph is the kernel the other plugins read. The Governance Evaluator's reading and the Projection Engine's projection are computed over the same graph an agent searches, so an answer from any of the three can be traced to the same knowledge. The registry identity graph-query exposes the same capability as a standalone server, and knowledge-cartographer tells an agent where that knowledge is thin before it relies on it.
Governance Evaluator #
#Who it is for. A platform or architecture lead who needs a maturity reading they can defend, and an agent that needs to know an organization's posture before it acts on it.
#What you get. A rung on the Governance Ladder with the dimensions that put the organization there, the gap to the next rung and what would close it, and a brief that can be handed upward. The reading is computed, not surveyed: it is the engine of Part I applied to the governed knowledge.
#How it composes. Its reading is the one the certifications are issued from, so a self-serve evaluation and a certified assessment read the same Ladder; the assessment adds evidence, scope and a human review, not a different engine. An organization that evaluates itself first arrives at an assessment knowing what it will find.
Projection Engine #
#Who it is for. Transformation leads and architects choosing between paths, and agents planning a change with more than one step, who want to know where a change would leave the governance posture before anyone commits to it.
#What you get. A forward projection: the rung a proposed change would reach, the dimensions that would move, and the gaps that would open or close along the way. The projection is computed over governed knowledge, not over a template, and it is stated at the altitude a decision needs: direction and consequence, not internals.
#How it composes. The projection reads the same graph and the same engine as the evaluation, so a projected rung means the same thing as an evaluated one. The Transformation Roadmap delivered with an enterprise assessment describes the same kind of path a self-serve projection describes: what moves the posture. Projection is available on the plugin tiers; it is not part of the free tier.
Governance Intelligence Bundle #
#Who it is for. Teams that want the whole loop in one subscription: know the architecture, evaluate the posture, project the change.
#What you get. The Knowledge Graph, the Governance Evaluator and the Projection Engine together, under one key at the one front door. The bundle is where the phrase governance intelligence belongs: it names the capability the operating system delivers, the ability to know, evaluate and project from one governed source, and it is the capability the three plugins deliver as a set.
#How it composes. The bundle is the three plugins, nothing more and nothing less, so everything said of each above holds for the set. An organization that later commissions an assessment keeps the bundle; the assessment reads the same knowledge the bundle has been reading.
The free decision-intelligence plugin #
#Who it is for. Any team running agents that wants the habit of consulting governance before acting, at no cost; and any developer who wants to see the platform answer before buying anything.
#What you get. A governed, auditable record to which an agent logs a consequential decision; an evaluation of a proposed decision before it is acted on, returning the earlier decisions that bear on it and a pass, warn or block verdict with reasons and suggested fixes; and a request for a full assessment when the record says one is due. Each organization's record is kept apart from every other's.
#How it composes. The decision record is the trail the audit asks for, and an organization that has been logging and evaluating its decisions arrives at an assessment with evidence instead of recollection. The plugin is the same decision-intelligence identity listed on the public registry.
Enterprise Governance Assessment #
#Who it is for. An executive, compliance or transformation lead who needs a defensible, board-ready reading of the whole enterprise, and the documents to act on it.
#What you get. A reading across all seven governance domains and three deliverables. The Governance Assessment Report states what was found in each domain and how it connects, where evidence is missing, where the organization stands overall and by domain, and how that standing would move if the leading gaps were closed; it opens with an executive summary and closes with a prioritized gap inventory, an action plan and a statement of what the analysis does and does not cover. The Readiness Certificate states the rung reached, with its credential name, in a form anyone can verify. The Transformation Roadmap sets out the path to the next rung. Timeline: Diagnostic by request; Full Assessment in 2–4 weeks.
#How it composes. The assessment is the Governance Evaluator's engine applied with full evidence, full scope and human review, so its rung is read on the same Ladder as the self-serve evaluation. The Decision Integrity Scan leads into it; the Agentic Readiness Certification can be taken from it or on its own.
Decision Integrity Scan #
#Who it is for. A leadership team that wants a quick, directional read on how well its consequential decisions are governed before committing to a full assessment.
#What you get. From a structured interview, a concise, board-readable report: a governance tier in the scan's own terms, the leading remediation themes, such as who holds the authority to decide, whether past decisions can be reconstructed, how exceptions escalate and how AI agents are overseen, a recommended window for the next assessment, and a business case an internal champion can carry to procurement. It is a directional read, not a formal assessment and not a credential, and its tier is not a rung on the Governance Ladder.
#How it composes. The scan is the entry point: a directional reading that becomes the case for the full assessment.
Agentic Readiness Certification #
#Who it is for. An organization that needs to show a board, a buyer or a regulator that it is ready to let agents act on its governance, and wants the standalone L4 credential without a full enterprise assessment.
#What you get. The L4 Resonant reading across the governance domains the standalone credential evaluates (the full assessment evaluates all seven), the Readiness Certificate at Agentic Readiness, and a certification badge. Every certificate is engine-validated, publicly verifiable: it carries an identifier, its verification page shows its status and offers a route to challenge it, and the badge leads back to that page, so a lapsed or replaced certificate is visible as such. Delivery is 5–7 business days. Issuance of the highest credentials is designed to follow a recorded human approval: the engine proposes, a person signs.
#How it composes. It is the same engine and the same Ladder as the enterprise assessment, read over the domains the standalone credential covers; an organization that later takes the full assessment is read across all seven.
Architecture Pack #
#Who it is for. Architecture leads who need a board-ready, standards-based model of their governance architecture, and teams at the start of a transformation who want to see the architecture they have before they plan the architecture they want.
#What you get. A one-time set of architecture deliverables built from the material the organization hands over and checked by a person before delivery: an ArchiMate viewpoint document, a posture report, a roadmap, an implementation brief, a private web viewer of the model, and a machine-readable export of the full model in the open ArchiMate exchange format. Secrets and personal data are screened out of submitted material on intake, as a best effort; what is submitted remains the customer's responsibility. The exemplar shows the shape of the model: 353 elements, 317 relationships and 4 viewpoints. Computed against our exemplar calibration corpus — a synthetic reference architecture, not customer data.
#How it composes. The pack produces the standards-based model of an organization's own architecture: the form in which that architecture is ready to be read as governed knowledge rather than as a shelf of documents.
#How the pack is made. The customer hands over its own architecture and governance material: the documents, diagrams and records it already holds. Before anything is built from it, that material is screened on intake: secrets and personal data are screened out, and a person checks that what remains is enough, in scope and quality, to build from. The screen is a best effort, not a certainty, so what a customer submits remains its own responsibility. The model is then built to the relationship rules of the ArchiMate specification and to our own standard for a complete, connected and traceable model. The exemplar that calibrates the engine is held to that standard, and its regeneration is reproducible. Where the exemplar falls short of a rule today, the shortfall is repaired in the model, never by relaxing the standard, and no conformance is claimed until the checks pass. The deliverable is rendered into the viewpoints an architecture team expects, current state, target state, network topology and migration among them. A person signs off before anything is delivered, for a customer's pack and for each public release of the exemplar. The model leaves the platform as an export in the open ArchiMate exchange format.
None of this came ready-made. The open standard says what a valid relationship is. It does not say how to turn a shelf of documents into a model that is complete, connected and traceable. We built that part ourselves, over successive releases of the exemplar: the standard for a complete model, the discipline that holds a model to it, and the sign-off that puts a person between the process and the customer. The open tools and formats we draw on are used as published; the process that joins them is our own, and it is the part a customer cannot get by downloading the standard.
Anything that needs time with our team, a diagnostic session above all, is by request rather than self-serve; the closing chapter says how to ask.