Hosting Options

The easiest and best way to use Arcade.dev is via our cloud service - sign up for free at https://api.arcade.dev . However, you might need to connect your tools to local resources (e.g. a local database or filesystem) or keep data within your own infrastructure. Don’t worry, Arcade has you covered!

MCP Server Deployment

You can route and manage tool calls from your agents to MCP servers hosted anywhere - on your machine, on your own infrastructure, in a private cloud, or on our cloud service. This allows you to mix the best public tools with your own private tools.

See On-premise MCP Servers for more information about how to use your own MCP servers running anywhere and see Arcade Deploy to learn how to deploy to Arcade’s cloud.

Customizing Auth

You don’t have to self-host Arcade to customize your auth experiences. Arcade’s cloud service supports a number of auth providers out of the box, and you can provide your own OAuth app credentials to brand your end-user experience. We recommend doing this for all production use cases, so that you can have isolated rate limits with the OAuth service provider and you can give your users a consistent experience when they go through an auth flow. You can still use the same tools when you customize your auth, no code changes are required.

See Customizing Auth for more information.

On-Premise Deployments

Fully on-premise deployments of the Arcade platform are available! Arcade can be deployed on Kubernetes via our Helm chart and Docker images as part of our enterprise offering. Contact us to learn more.

The requirements for deploying Arcade on-premise are:

• Kubernetes cluster (1.30+) (We have tested this helm chart on AKS, GKE, and EKS).
• Helm 3.x
• kubectl configured to access your cluster
• Cert Manager for securing Redis and Postgres and public ingress (see below)
• Nginx Ingress for accessing Arcade.dev from outside the cluster (see below)