# Vaubaan Gateway

Vaubaan Gateway is a server you install on your own network so that coding agents can use your cloud services through MCP without being handed your credentials.

**Pre-release.** No version is tagged and no image is published yet.

## The problem

An agent that deploys, migrates a database or opens a pull request needs credentials, and the usual way is to paste a token into its configuration: the agent can then do anything the token allows, for as long as it lives, and nobody can say afterwards what it did.

## The answer: missions

A person creates a mission, and the gateway holds the agent to it:

- **Resources**: the accounts and the resources the agent may touch: these two repositories, the staging project, this DNS zone.
- **Permissions**: named, one by one, from each service’s catalog: write on feature branches, never merge; apply migrations on staging. Never “all”.
- **Limits**: how many times per period and how fast, for each permission.
- **Ask me first**: the actions that wait for the mission’s creator to say yes, where they see it.
- **A key per mission**: the agent gets a key for that mission and nothing else; replace it or stop the mission at any time.
- **Credentials stay on the instance**: the gateway runs each call with a credential it decrypts for that call only.
- **Everything recorded**: every call, allowed or refused, with the permissions it needed and whose key made it.

## The shape

- On your network: one Docker image, one process, one embedded database, behind your TLS proxy.
- Behind your identity provider (OpenID Connect) or GitHub sign-in.
- With your company’s own apps at each service: no app shared with anyone else, no hosted tenant.

## Supported services

Cloudflare DNS, Context7, Fly.io, GitHub, Gmail (experimental), Miro, Notion, Railway, Resend, SSH (bash), Stripe, Supabase, Upstash Redis, Vercel. Every plugin: [/plugins](/plugins).

## Try it

- [Try the demo](/docs/quick-look): the whole interface on a laptop, nothing to register.
- [Install an instance](/docs/install): Docker Compose or Railway.
- [Trust center](/trust): what protects your credentials, and what does not.
- [Source code](https://github.com/vaubaan/gateway), Apache-2.0.

## Questions and answers

### How do I let a coding agent use my cloud services without giving it my credentials?

Install Vaubaan Gateway on your network, connect your accounts to it once, and create a mission for the agent: the resources it may touch, the permissions it holds, the limits of each, and which actions ask you first. The agent receives a key for that mission and calls the services through the gateway over MCP; the credentials stay on the instance.

### What is an MCP gateway?

A server that sits between AI agents and the tools they call through the Model Context Protocol. Vaubaan Gateway exposes the tools of your cloud services over MCP, decides every call against the agent’s mission, executes it with a credential the agent never sees, and records it.

### Does the agent ever see a credential?

No stored credential is ever returned to an agent. One exception is named: a few tools exist to hand the agent a short-lived token, such as a GitHub installation token to clone or push; each is a permission of its own, refused unless the mission holds it.

### Which services does it support?

One plugin per service ships with the gateway: Cloudflare DNS, Context7, Fly.io, GitHub, Gmail (experimental), Miro, Notion, Railway, Resend, SSH (bash), Stripe, Supabase, Upstash Redis, Vercel. Each plugin is a catalog of named permissions with presets; a plugin for another service can be written from the kit in the repository.

### Which agents and MCP clients work with it?

Any MCP client that can call a server over HTTP with a bearer header, such as Claude Code or Cursor: the mission key goes in the Authorization header. The project’s own test suites drive the gateway with the official MCP client; no person has yet run Claude Code against a running instance.

### Is there a hosted version?

No. Vaubaan Gateway runs on your own infrastructure only: there is no hosted service and no account to create. A managed offer may come later; nothing is open today.

### Is it ready for production?

Not yet. It is pre-release: no version is tagged, no image is published, and the software has not been run in production. It has had no third-party security audit. The known limitations are listed in the docs.

### Does it send anything to the project?

Not by default. Community telemetry is off on a new instance, and today nothing is sent even when it is turned on, because the project’s collector is not published yet. The trust center lists the exact fields an instance would send.

### What does it cost?

Nothing. Vaubaan Gateway is open source under the Apache-2.0 licence; you run it on your own infrastructure.