Frazer
Start building
Integrationsfrazer.ai

Connect once.
Use it everywhere, with grants.

215 integrations in one catalog, from source control and identity to model providers and agent tools. An admin connects each one once for the organization; projects, devboxes, agents and knowledge bases use it through grants. Credentials stay in Frazer Secrets, and every page says what leaves Frazer.

Browse the catalogRequest an integration
00 · The catalogFig. 1 · catalog UI, demo organization

The catalog

Featured

curated, not paid
  • GitHubBy Frazer

    Environments, builds on push, Reviewer, GitHub runners; MCP tools for agents.

    installedMCP
  • SlackBy Frazer

    Alerts, approval links, agent channels, Knowledge source.

    installedMCP
  • OVHcloudBy Frazer

    Bring servers from your account with their private network.

    BYO servers
  • AnthropicBy Frazer

    LLM gateway upstream, Messages passed through natively.

    installedupstream
  • Hugging FaceBy Frazer

    Model and dataset imports, gated models with your access.

    upstream
  • OktaBy Frazer

    SSO and SCIM; groups follow the directory.

    identity
  • LinearBy Frazer

    Issues for agents and incidents; MCP server through your connection.

    MCP
  • Google Artifact RegistryBy Frazer

    Import images into Frazer Registry in a migration window.

    import
  • DatadogBy Frazer

    Export metrics, logs and traces; Frazer keeps the original.

    export

Agent tools (MCP)

14 · read-only by default
  • Frazer MCP serverBy Frazer

    Frazer’s own tools for any MCP client, scoped tokens.

    MCP
  • Context7By partner · verified before listing

    Library documentation for coding agents.

    MCP
  • Custom remote MCP serverYours

    Any Streamable HTTP server by URL; scanned before it is allowed.

    MCP

Fig. 1: the integrations catalog, product UI with a demo organization (the installed marks are its own).
A
Who built it, on every tileBy Frazer, by a verified partner, or yours. Featured is chosen by us, never bought.
B
A section for agentsEvery MCP server is verified before listing and read-only until a grant says otherwise.
C
An exact count215 entries in 21 categories, from the same registry as the console.
01 · How outside services fitFig. 2

Six roles, written down.
Nothing else runs outside.

Your images, secrets, logs and metrics live on Frazer. Other services connect in one of six roles, and the catalog shows which. Model providers are the one deliberate exception: requests leave Frazer through the LLM gateway, labeled with their data policy.

  • Frazer: registry, secrets and observability, the only runtime backends.
  • Import source: read once, or sync for 90 days (artifact registries, secret stores, buckets).
  • Upstream: pull-through; Frazer keeps the copy (container hubs, Hugging Face, Helm repos).
  • Your DNS: the DNS controller writes one zone (Cloudflare, Route 53, Cloud DNS, OVHcloud).
  • Identity provider: people sign in, groups sync (Google Workspace, Entra ID, Okta, SAML, OIDC).
  • Export destination: a copy goes out, the original stays (OTLP, Datadog, Splunk, FOCUS billing files).
  • Your servers: machines join Frazer (OVHcloud, Hetzner, Linux in your clouds).
  • Six roles: an outside service is never a runtime dependency of your workloads.
Fig. 2The roles an integration can play
02 · Every integration page has the same partsFig. 3

What it does, what it needs,
and what leaves Frazer.

Slack

Alerts, approval links, agent channels and a Knowledge source

What Frazer does with it

Sends alerts and incident updates to the channels you pick, carries agent conversations through Frazer’s channel gateway, and indexes public channels into Knowledge with Slack’s own permissions.

Capabilities, and the scopes they need

notify.send
Post alerts and agent messages to chosen channels
chat:write
channels.read
List channels to pick from
channels:read
knowledge.read
Index public channels into Knowledge
channels:history
agents.channel
Talk to agents in threads, sender verified
app_mentions:read

Data flow

Leaves FrazerAlert titles, states and links; agent replies. Never secret values or log bodies.
Frazer storesChannel IDs, the bot token in Frazer Secrets, message metadata for 30 days; indexed text only if Knowledge is granted.
Publisher
By Frazer
Categories
Communication · Knowledge sources
Auth
OAuth app, bot token rotated every 12 h
Scope
Organization connection, granted per project
Works with agents
Yes, through Frazer’s channel gateway
Health
Healthy · Expiring · Needs re-auth · Degraded · Error · Paused
Docs
/docs/integrations/slack
Fig. 3An integration page · Slack as the examplefields from the catalog registry
03 · Governed connections

One place to see, rotate
and revoke every outside credential.

  • Connect once

    An admin installs it for the organization, with the organization’s app or bot identity, not a person’s account.

  • Grant, narrowly

    Projects, devboxes, agents and knowledge bases get capabilities, not tokens; more scope needs a new consent.

  • No stored credentials outside

    Boxes and agents get tokens of an hour or less from the broker, or none at all: the gateway injects them.

  • Health you can see

    Hourly checks, six states, emails 30, 7 and 1 days before anything expires.

  • Owned, not orphaned

    Every connection has an owner; it survives the installer leaving, and ownership transfers with a plan.

  • Uninstall with a preview

    See every project, agent and dashboard that uses it before you remove it.

04 · Events out

Every change,
signed and delivered.

About 60 event types across servers, clusters, deploys, data, AI, agents, security, access and billing, signed with Standard Webhooks and shaped like CloudEvents. Events carry identifiers and states, never secret values.

event.json
{
  "specversion": "1.0",
  "type": "ai.frazer.releases.rollout.v1.succeeded",
  "source": "projects/acme-production",
  "subject": "environments/production/apps/checkout-api",
  "id": "evt_01J9W3…", "time": "2026-10-02T10:52:11Z",
  "data": { "revision": "checkout-api-00042", "image": "sha256:4e1c…", "by": "users/noah" }
}
Delivery
POST https://hooks.acme.example/frazer
webhook-id: msg_2mQ8…
webhook-timestamp: 1759402331
webhook-signature: v1,K5oZfzN95Z9UVu1EsfQmfVNQhnkZ2pj9o9NDDsrqsHU=
retries for about 3 days · delivery log 30 days · redeliver failed since T

$ frazer webhooks listen --forward-to localhost:8080
$ frazer webhooks trigger ai.frazer.releases.rollout.v1.succeeded
05 · Build on Frazer

Missing something?
Ask for it, or build it.

API and SDKsGo, TypeScript and Python from one contract; every console action is an API call.
OpenTofu and TerraformA provider for every Frazer resource, with the same plans.
MCPmcp.frazer.ai for any agent, read-only by default, scoped tokens.
Frazer OAuth appsBuild a product on Frazer: your app asks for scopes, the org approves.
Verified publishersList your integration with a “By” line people can trust.

Request an integration

Tell us the service and what Frazer should do with it.

A request goes by email to support@frazer.ai.

Send request by email

215 integrations, one set of rules.
Connect what you already use.

Browse the catalogRead the docs