Every action is checked, approved where required, and recorded.
Controls for your people and your AI agents: where Marrinn runs, who can do what, what is recorded and what an AI model is sent.
One action passes a permission check, an approval and a ledger entry.
A Squid, Marrinn's AI agent, holds a role in the same permission matrix as a person. The platform checks the role, asks a person to approve where required and writes the record.
- Priya ShahOpened the supplier record for Northway SuppliesAllowed
- Reconciliation SquidMatched 42 invoices to purchase ordersAllowed
- Procurement SquidDrafted purchase order PO-0231Allowed
- Tom EllisonGranted the Member role to Leila KhanAllowed
- Reconciliation SquidRelease payment PAY-0412, £18,400Held
- Finance DirectorApproved PAY-0412, written to the LedgerApproved
Above £5,000, a person decides. The platform writes the row.
Marrinn runs where you decide.
Your security and procurement teams choose where it runs.
- Our cloudHosted and run by Marrinn
- Your cloud accountIn your own tenancy, under your keys
- Your own serversOn your premises, with your records on your hardware
The same system in each place. You choose where it runs.
You choose the AI model, and Vault holds the credentials.
One Kernel setting sets the provider for every AI feature. The credentials your agents use sit in Marrinn Vault.
- OpenAI
- Anthropic
- OpenRouter
- A private model
The controls, one line each.
Each line points to a capability described on its own page. If your questionnaire asks for something not listed here, send it to us and we answer in writing.
- Access control
- One permission matrix: five roles (Owner, Admin, Member, Viewer, Guest) against 235 actions, each tagged for risk. Narrowed or widened per department, project or record type.
- Agent permissions
- A Squid is granted a role in the same matrix as a person, on the same screen, with the same audit row. There is no separate path for an agent.
- Approvals
- A person approves or rejects what a Squid prepares where your rules require it. Only the organisation owner can switch self-improving skills on.
- Audit trail
- Every grant, override, revocation and policy change is a row in an append-only log. No administrator can edit it.
- Ledger
- Every run and every piece of work writes a row with six required fields: actor, work type, span, cost, artefact and thread. Reading it is a permission. Exports carry the query and the time they ran.
- Offboarding
- Removing a person or a Squid removes every connection, scope and standing order it held, in one action, and logs it.
- Credentials
- Held in Marrinn Vault: client-side encryption, per-vault keys, rotation reminders, version history and a complete access log. The server stores ciphertext only.
- Single sign-on
- Vault supports SAML and OIDC single sign-on and enforced two-factor authentication.
- Data sent to a model
- Titles and progress go to the model. Descriptions and attachments do not, unless a tool says so. The provider key is stored encrypted and never written to code or a log.
- Company
- Marrinn Ltd, registered in England and Wales, company number 17374329. Registered office: 20 Wenlock Road, London N1 7GU.
- Contact
- Security questions and reports: sales@marrinn.co.uk.
Take your security questions to the team that builds it.
Thirty minutes with the Marrinn team on your hosting, your roles and your audit needs. You can also write to sales@marrinn.co.uk. We reply within one UK business day.
