Skip to content
AuthProxy

Integrations without the authentication plumbing

AuthProxy gives your application one place to create, secure, use, and operate connections to third-party APIs.
Try the live demoRun it locally

One integration boundary

Section titled “One integration boundary”
flowchart LR
    Host["Your application"] -->|Actor and namespace context| AP["AuthProxy"]
    AP -->|OAuth, API key, or no-auth request| APIs["Third-party APIs"]
    Admin["Your operators"] -->|Configure and monitor| AP

Choose your path

Section titled “Choose your path”
Add integrationsMap host users and tenants, embed the Marketplace, and make proxied requests.
Deploy and operateInstall AuthProxy, configure its dependencies, and monitor production traffic.
Review securityEvaluate trust boundaries, permissions, encrypted credentials, and logging risk.
Evaluate the architectureUnderstand connectors, connections, actors, namespaces, and the build-versus-buy boundary.

Start with a working system

Section titled “Start with a working system”
Explore the hosted demoUse fake accounts, connect an app, inspect the Admin UI, and explore Grafana.
Run AuthProxy locallyClone the repository and start the full stack with Docker Compose.
Make a proxied requestSend an authenticated request through a connection without handling its credentials.
Install with HelmDeploy AuthProxy to Kubernetes and connect production dependencies.