Operate Arcade

These docs are for platform operators: the people who deploy Arcade, connect identity providers, and govern how use across a company.

If you build agents or custom servers, start with Get Started and Build.

Choose your path

Quickstart: stand up Arcade for your org

Platform operator quickstart: deploy Arcade, connect identity, create a gateway, and turn on governance

Compare hosting options

Learn about the different ways to host and deploy Arcade

What operators configure

Deploy

Run Arcade Cloud, deploy through a cloud marketplace, or self-host with Helm.

Deployment & hosting

Learn about the different ways to host and deploy Arcade

Arcade Cloud

Learn about the infrastructure, data storage, and data sovereignty options for Arcade Cloud

Self-host with Helm

Deploy and run the Arcade platform yourself on your own Kubernetes cluster

Hybrid MCP servers

Run a self-hosted MCP server worker in your own private network or VPC and connect it to Arcade Cloud. Hybrid worker deployment for on-premises and private cloud environments.

Identity

Connect your end- identity provider and configure how gateways authenticate users.

User Sources

Connect an OIDC identity provider to an MCP Gateway so your end users sign in with their existing identities

Auth providers

Registry of all auth providers available in the Arcade ecosystem

Secure auth in production

How to secure and brand your auth flows in production

Governance

Federate tools, enforce access policies, and review administrative actions and the runs they produced.

MCP Gateways

Connect multiple MCP servers to your agent, application, or IDE with Arcade MCP Gateways

Remote MCP servers

Contextual Access

Control who can see and use which tools, validate requests, and filter outputs — per user, per org, per project

Audit Logs

Arcade.dev now captures every administrative action across the platform automatically — who did it, how, what changed, and when.

Tool Executions

Review every tool run in a project: what ran, for whom, and why it failed, with tool inputs and outputs held to project admins.

Glossary: Account, Tenant, Project, User, and
API reference: Administrator and runtime APIs
FAQ: common operator and developer questions