# Enterprise: a dedicated Agentboxd deployment

Source: https://agentboxd.com/docs/self-hosting

> A dedicated Agentboxd deployment run by us in the EU or US, or in your own cloud or on-premises under a support contract.

The hosted service at api.agentboxd.com suits most teams. When you need infrastructure of your own, the Enterprise plan gives you a dedicated Agentboxd deployment. There are two ways to run it.

## Dedicated, run by us

The usual choice. We run a separate copy of Agentboxd for you alone:

- **Your own server and sending IPs**, in the region you choose: EU or US.
- **Your own domain and storage bucket**: your MX host and DKIM keys on your domain, and mail and attachments in a bucket that holds only your data.
- **Isolated from other customers**: no database, queue, storage or sending IP is shared with anyone else.
- **Run by us**: we install, update and monitor it.

## In your own cloud or on-premises

Under a support contract, the same deployment can run in your cloud account or your own data centre. It runs on containers (Docker Compose, or your orchestrator), PostgreSQL, Redis and S3-compatible object storage; a single mid-size VM handles most teams.

> **Careful:** Receiving mail needs inbound port 25 to reach your MX host. Sending needs outbound port 25 with reverse DNS for your sending IPs, or a relay. Many clouds block outbound port 25 by default; we plan this with you.

## Either way

- **The same API**: the SDKs, the MCP server, webhooks and the dashboard work unchanged. Point `AGENTBOXD_BASE_URL` at your deployment.
- **Your AI settings**: keep AI processing off, categorisation only, or point it at the model provider your security team approves.
- **No plan limits**: inboxes, volume and retention are sized to your contract.

## Talk to us

Write to [hello@agentboxd.com](mailto:hello@agentboxd.com) with your requirements (region, expected volume, compliance needs), or use **Request higher limits** under Settings in the dashboard. We answer within one business day.