Integrations

Integrations: Databases, SSH, Kubernetes

The Connector sits in front of your databases, SSH hosts, Kubernetes clusters and internal APIs. The Endpoint controls outbound agent traffic. Both connect to your identity provider, SIEM, cloud accounts and MDM, and share one control plane.

Get a demo › Read the docs ›

Postgres

PostgreSQL data masking and access control in one proxy: mask columns by label, block DDL in prod, and log every query to your SIEM. No shared passwords.

Snowflake

Snowflake access control at the proxy: per-user masking, query blocking and audit logs, even when BI tools share one service account. See Formal in action.

Kubernetes

Kubernetes access control at the API: SSO identity, MFA for kubectl exec, namespace and kind policies, impersonation, and recorded exec sessions.

SSH

Record every SSH session with Formal: engineers connect with their SSO identity, no shared host keys, and policies end risky sessions. EC2 and ECS via SSM.

Claude Code

Claude Code Security scans code. Formal secures what Claude Code does at runtime: egress rules, API keys kept off laptops, and a per-person audit log.

Cursor

Cursor security for teams: control what Cursor agents and Cloud Agents reach, keep secrets out of the sandbox, and tie every request to a person.

Devin

Devin security with Formal: short-lived OIDC identity instead of shared secrets, Slack-approved just-in-time database access, and an audit log per session.

Formal integrates where the traffic flows. PAM puts the Connector, a reverse proxy in your VPC, in front of databases, SSH hosts, Kubernetes clusters and internal APIs, so engineers and agents connect with their own identity and native clients. Endpoint controls outbound traffic from laptops and agent sandboxes. Both share one control plane for policies, identity and audit logs.

Which resources does Formal support?

Every supported resource has a setup guide in the docs. The pages below go deeper on the most common ones and on the AI agents we document.

Databases and warehouses: Postgres, MySQL, MariaDB, Amazon Redshift, MongoDB, Snowflake, BigQuery, ClickHouse (over HTTP), DynamoDB, Redis
Infrastructure: SSH and AWS SSM, RDP, Kubernetes
Cloud APIs and storage: AWS APIs, AWS S3, Google Cloud APIs
Apps and APIs: HTTP, gRPC, Web (browser apps behind Formal sign-in)
AI traffic: MCP servers through a Connector, and LLM provider APIs through the Endpoint or a Connector
Package registries: Socket Registry Firewall

At Cursor, Formal secures thousands of resources across 10+ technologies, including SSH, PostgreSQL, Redis, ClickHouse, and Kubernetes (read the case study).

Which identity, logging and cloud tools does Formal connect to?

Single sign-on: Okta, Entra ID, Google Workspace, OneLogin, JumpCloud, Rippling, Ping, or any SAML 2.0 or OIDC provider. SCIM directory sync works with the same providers or any SCIM provider.
Logs and SIEM: Datadog, Splunk and Panther, or a bucket in AWS S3, Google Cloud Storage or Azure Blob Storage.
Cloud accounts: AWS, Google Cloud and Azure, for resource autodiscovery and log delivery.
MDM: Kandji, Fleet, Jamf Pro and Mosyle, to roll out the Endpoint and use device information in policies.
BI tools: Metabase, Looker, Omni, Fivetran and custom apps pass the end user’s identity to the Connector, so each query is attributed to a person, not the tool’s shared machine user.
Slack: users request access and approvers answer without leaving Slack.
Infrastructure as code: Terraform, Pulumi, the Go SDK and the API.

Ready to (zero) trust your agents?

One network security layer for every agent and human, from the laptop to production.

Get a demo ›