[Infrastructure]

Dozens of providers. Infinity if you count yours.

Ship with Gmail, Slack, Stripe, Notion — then add your own connector in 2 minutes. Any HTTP API. Your internal APIs too.

Read the docs Try Cloud

[01 · Why it matters]

Integration catalogs are a race you can't win — and don't need to.

Zapier has thousands of connectors. n8n has hundreds. Playing catalog-count is the wrong game: what actually matters is whether your agents can reach every service you depend on — including the ones no vendor will ever package for you.

Appstrate ships a growing catalog of production-ready providers (OAuth2, OAuth1, API key, Basic, multi-field custom). Everything else — your internal API, a niche SaaS, a legacy backend — becomes a first-class provider via a form. No code, no deployment, no registry. Credentials are isolated by the sidecar automatically, same as the built-ins.

Dozens

ready-to-use providers

∞

custom providers

to add yours

auth modes supported

[02 · How it works]

Built-in or built-by-you. Same pipeline.

Users connect a provider in the UI or via the API. Credentials encrypt at rest (AES-256-GCM) and store per-application. Agents never see them — they call the sidecar proxy, which injects auth and enforces the URI allowlist.

Gmail providerAFPS · OAuth2 connector

{
  "$schema": "https://afps.appstrate.dev/schema/v1/provider.schema.json",
  "name": "@appstrate/gmail",
  "version": "1.0.0",
  "type": "provider",
  "displayName": "Gmail",
  "categories": ["email", "productivity"],
  "definition": {
    "authMode": "oauth2",
    "oauth2": {
      "authorizationUrl": "https://accounts.google.com/o/oauth2/v2/auth",
      "tokenUrl": "https://oauth2.googleapis.com/token",
      "defaultScopes": [
        "https://www.googleapis.com/auth/gmail.readonly"
      ],
      "pkceEnabled": true
    },
    "credentialHeaderName": "Authorization",
    "credentialHeaderPrefix": "Bearer",
    "authorizedUris": ["https://gmail.googleapis.com/*"],
    "allowAllUris": false
  }
}