Read access becomes full access
Fine-grained roles rarely exist, so troubleshooting a production database means a role that can also write and delete.
Sits between people, agents and your databases, servers and clusters. It decides on each query and command, with no app changes or SDK.
Securing 1M+ requests per second in production
The problem
To fix one bug in production, an engineer gets a role that can do much more. Scripts and agents get the same keys.
Fine-grained roles rarely exist, so troubleshooting a production database means a role that can also write and delete.
A ticket says who asked. It doesn't say what they'll run, on which resource, or for how long.
One database password ends up in scripts, laptops and agent configs. When something goes wrong, the log shows the account, not the person.
# Without Formal, all three go through.
How it works
Runs in your VPC as several instances behind a load balancer, on Kubernetes or Amazon ECS, and scales with your traffic.
Engineers use SSO. Agents use short-lived OIDC identities. A Native User on the Connector holds the real password, key or IAM role.
Policies check what's about to run and what comes back: block, mask, limit or ask for approval. Every query and command is logged.
Why it's different
| Without Formal | With Formal PAM | |
|---|---|---|
| Credentials | Shared passwords and long-lived keys | Native Users hold them; people and agents never see them |
| Permissions | A different model per system: SQL GRANTs, cloud IAM, Kubernetes RBAC | One policy language for every resource |
| Approvals | A ticket that grants a role, with no limit | One action, on one resource, ending on its own |
| Audit | Logs scattered across systems | One log of every query and command, by person or agent |
Capabilities
Formal reads each query before it runs and each result before it comes back.
Ask in Slack for one query on one resource. Approve it for a single run or a time window, and it ends on its own.
Every SSH session and kubectl exec session is recorded and can be replayed.
Native Users hold the upstream credential. People and agents never see it.
Backtest a new policy on up to 31 days of past traffic, then dry-run it, then enforce it.
Coverage and trust
Customer data never goes through Formal's cloud.
If the Control Plane is unreachable, running Connectors keep their last configuration.
Connector metrics over OpenTelemetry, with a ready-made Datadog dashboard.
Control Plane hosted by Formal, or self-hosted on AWS. SOC 2 Type II, ISO 27001, SSO and SCIM.
Customer proof
“With Formal, we can finally manage least privilege access across our entire infrastructure through a single control plane.”

Keep exploring
FAQ
No. psql, mysql, mongosh, ssh and kubectl keep working. The Formal CLI sets up the local connection.
No. The Native User on the Connector holds it, or fetches it from your vault at connection time.
Yes. Agents connect as machine users with short-lived OIDC identities, mapped to the human they work for, and follow the same policies.
No. The Connector runs in your infrastructure. The Control Plane only holds configuration and logs.
It controls each query and its results, not only the session, and the same policies apply to agents. See the compare pages for details.
Not automatically today. Native Users can fetch credentials from your vault at connection time.
See how Notion and Cursor run production access through Formal.