Security and governance
Agents get a key, not the keys.
Every agent is a named user with its own scoped key. Agents draft and propose, and never accept their own proposals. The controls below show exactly what each agent key can do. Here’s exactly what’s live today and what’s next.
Controls
How Mataara keeps agents in their lane.
Live means it’s in the product today. Roadmap is direction, not a contract.
| Control | What it does | Status |
|---|---|---|
| A separate identity per agent | Each agent is its own bot user, so every change is attributed to that agent, not to the person who set it up. | Live |
| Named keys, stored as hashes | Each agent gets a named access key. The secret is shown once and stored only as a hash. Revoke a key and the agent is out. | Live |
| Allow-lists on agent keys | A key carries the Products, cards and document types it may touch. Agent keys need an allow-list: one-step setup refuses an empty one, and an agent key with an empty allow-list is denied every call. | Live |
| Proposals to the plan | Only a person accepts or rejects a stage or feature-pack proposal, and only a person starts delivery. Agents propose changes to specs, acceptance criteria and delivery stages. A key or bot cannot edit acceptance criteria directly. An edit key can still edit cards, write card documents, and delete a card that has no child cards, no Feature that still names it as its Domain, and no published document attached; creating a card needs its own access. Clearing an already-set delivery stage is a stage move only a person can make. The proposing agent can't accept its own proposal, and a stale proposal fails. | Live |
| Stage moves and publishing | An agent can't accept its own proposal. Only a person moves a delivery stage, starts delivery, accepts a stage or feature-pack proposal, or clears an already-set stage. Staging and production moves also need a deploy pin. An agent can still file that pin itself through report_bot_activity. The pin doesn't move the stage; a person still makes the move. Only a person publishes a managed or card document. That covers everything you can publish in Mataara. |
Live |
| Fail-closed tenant isolation | Planning data and documents are kept to your organisation, and agent access keys only reach your organisation’s data. Both fail closed. The planning API needs a signed-in person or a valid agent access key; the only unauthenticated endpoints are sign-in, sign-up and links you choose to share. | Live |
| Usage log per key | Owners and admins see which key called what, and when. | Live |
| Rate limits per key and per organisation | Some tools already limit how fast one agent access key may call. Organisation-wide caps are not enforced yet, so a runaway loop can still starve your organisation. | Roadmap |
| Deny-list for billing, role or key-management endpoints | A server-side deny-list already refuses most of those calls. Keys and bots cannot mint keys. | Roadmap |
| Sign in with GitHub, Google or Microsoft | Use the identity your team already has. | Roadmap |
| Single sign-on (Entra ID, Google Workspace, OIDC) | Require your organisation’s identity provider. Business and Enterprise. | Roadmap |
| Agent activity ledger | Agents report runs, tests and deploys back into an activity ledger behind the documents, so the progress pack accounts for the bots as well as the people. | Roadmap |
| Evidence pack export | One sealed file per Feature, change request or release, with a hash for every file. Signed manifests and scheduled packs are on the roadmap. | Live |
| Independent security attestation, SCIM, SIEM export | On the roadmap. Ask us where they are. | Roadmap |
Hosting and data
Where your data lives.
Hosting region and subprocessors are published here when the production service opens. Until then, ask us and we’ll tell you exactly where your organisation’s data is held. Sign-ups today go to our staging service; don't store confidential data there until production opens.
Questionnaires and reports
Need a security questionnaire answered?
Talk to us about security questionnaires or to report a vulnerability. We’ll answer with what’s live, not what’s planned.
See the controls for yourself
Set up an agent on Business or Enterprise and watch what it can and can’t do.
Register, create a scoped key, and try a call outside its allow-list. Agent keys are on Business or Enterprise.
Compare plans: Pricing. Questions? Talk to us.