Governed by architecture, not just policy.
Frege's security foundation comes from how the system is built, not from a list of promises. Tenant isolation, explicit access relationships, encrypted credentials, supervised runtimes, and versioned auditability are properties of the architecture — enforced at the data, authorization, and runtime layers.
Data layer
Tenant isolation
Frege uses PostgreSQL row-level security (RLS) to restrict access to tenant data at the database layer. Requests run inside tenant-scoped transactions, so cross-tenant access is blocked by the data layer itself — not left to application code.
Ory Keto
Fine-grained authorization
Ory Keto governs access to tools and documents. Access is expressed as explicit relationships — per-key, per-project, per-document, per-tool — so internal staff and external clients live under different rules in the same workspace.
- API keys can receive specific tool grants and denials.
- Documentation is scoped separately from tools.
- Organizations and temporary grants layer additional rules on top.
At rest
Encrypted credentials
Organization-specific target credentials are encrypted at rest and decrypted only during outbound authentication, so plaintext exists only on the necessary request path. This supports B2B SaaS and enterprise partners that authenticate to the upstream API with their own credentials.
Runtime
Isolated MCP runtimes
Each project's MCP server runs as a supervised child process. That gives runtime isolation between projects and versions, contains failures to a single runtime, and makes operational behavior easier to reason about.
Auditability
Audit trails and version history
Frege records tool calls, access changes, version actions, webhook events, and project activity, combined with immutable versioning — a transparent, replayable record of what changed, who did it, and which runtime surface is live.
Web interface
Transport and form protection
The web interface ships standard browser security headers, CSRF protection on state-changing forms, and secure cookie defaults appropriate to the environment for session handling.
Events
Webhook verification and event flow
Webhook verification adapters and event routing validate external events before they are accepted, stored, and bridged into MCP notifications — so untrusted inbound events can't drive the system unverified.
Kratos + Hydra
Identity and OAuth building blocks
Ory Kratos (identity) and Ory Hydra (OAuth) provide governed user onboarding, shareable connect pages, and organization-aware access — without every team building a custom auth layer.
Need a deeper technical review?
This page is a high-level overview. For an enterprise evaluation, the model is best understood as row-level security, Ory Keto authorization, encrypted credentials, versioned rollout, and isolated MCP runtimes working together — one governed surface over the API you already operate.
Read the model, then inspect the product.
Frege is built for teams that want an inspectable MCP runtime around their existing APIs.