The governance layer.

You control the governance. Claims set what a person is allowed to do. Roles and organisations apply those rules, and every product asks before it trusts a session. The authority stays with you: who signs in, what they can open, and which organisation they are acting for.

Governance for your products.

1
Organisations scope the rules
An organisation is who the work belongs to. Claims are evaluated inside it. The same person can be allowed a different set of things in a different organisation, and every console switches with that scope.
2
Claims are the rules
A claim is a permission: who can see usage, manage a team, open billing, or work in a product. Products ask Signet, and a role is the set of claims a person holds.
3
OAuth clients must ask
Connected products are OAuth clients. Signet issues the session and says which claims it carries. A product asks Signet before it trusts who someone is.
4
One authority for the tenant
With no organisation selected, Signet is the tenant catalogue: users, roles, claims, clients, and integrations. Pick an organisation and the same rules follow into each product.

How a rule takes effect.
Name the claim
Claims are defined on the tenant, and on the client they belong to. That is the list of things a product is allowed to check.
Bind it to a role
A role carries the claims. Assign the role and the person can open the matching screens. Change the role and every product changes with it.
The products enforce it
The session is Signet's. Logging out of one console ends the session the others trust, because they all asked the same authority.
Subscription vs self hosted.
One monthly subscription for the hosted directory, or run Signet in your own environment.
Cybersecurity & data governance.
Data assessment.
Where does your data live, where does it flow, and what happens when AI touches it? We map every interaction between your systems and AI services to understand the real exposure before anything else.
Which models see your data, what gets stored, what gets logged, what leaves the building. You can't govern what you can't see — so we make every data path visible before a single workflow goes live.
Smart scanning.
AI-generated code introduces new risks — secrets leaked into outputs, OWASP vulnerabilities woven into suggestions, production data surfaced where it shouldn't be. Traditional scanners weren't built for this.
We run AI-aware scanning across your codebase and outputs, catching what gets introduced by the same tools that are supposed to be helping. Continuous, not one-off — every output checked and reviewed.
Governance by design.
Human-in-the-loop isn't a feature — it's an architecture decision. We design new systems with approval workflows, escalation paths, and audit trails built into every layer from day one.
Every agent action traceable, every decision logged, every critical path routed through a human checkpoint. When something needs reviewing, the system stops and asks — it doesn't assume.
UK data residency.
Inference routed through UK and EU regions. Your data persisted in UK data centres, with processing across nearby European availability zones. An evolving landscape as regional coverage expands.
We architect around the current constraints so compliance isn't an afterthought. For regulated industries, public sector, or any organisation where data sovereignty isn't optional, this is the foundation.
FAQs
Start the journey
Ready to ignite a spark? Everything we build starts here — a focused discovery engagement that maps your landscape and delivers a clear plan forward. Whether you're launching something new, reigniting an existing platform, or rewiring how your team works with AI.