Your data stays
where it is.
Grantory is a record of decisions, not a window into your infrastructure. There is nothing to connect, so there is nothing to leak.
What Grantory holds
- Names and work emails of people in the model
- Teams, workspaces, systems, and levels you describe
- Requests and the reason given
- Who approved, in which role, and when
- The note a provisioner wrote after granting
- Expiry dates, reviews, findings, and the audit trail
What it never touches
- Cloud keys, IAM roles, admin consoles
- Git tokens, repositories, pipelines
- Your user directory or SSO
- Logs, databases, customer data
- Passwords to the systems you list
- Anything beyond the Slack webhook you add
How it is built.
No outbound connectors
The only outbound call is the Slack webhook you configure. Remove it and nothing leaves.
Tenants are separated
Every query is scoped to the current organization, by URL and by MCP alike.
Keys are hashed
MCP keys are shown once and stored as a SHA-256 hash.
Read-only by default
An MCP key reads only. Allowing findings lets an owner or administrator key record audit results, nothing else.
Separation of duties
Requesters cannot approve themselves. Approvers and provisioners are recorded apart.
Audit trail
Requests, approvals, grants, removals, roles, and membership changes, with the actor.
Talk to us.
Found a vulnerability, or need answers for a vendor review?
Model access without
handing over a key.
$12 per person, per month. Every feature included.