Billing & Plans
Bring Your Own Compute (BYOC)
BYOC lets you run Zapat agents on your own infrastructure — coming soon to Enterprise tier.
Updated March 5, 2026
BYOC (Bring Your Own Compute) will let you run Zapat agents on your own infrastructure using your own AI API key. Your source code would never leave your network, and you would pay your AI provider directly for model usage.
Note
BYOC is on our roadmap and will be available to Enterprise tier customers first. Today, all Zapat jobs run on managed cloud compute in isolated Fargate containers. Join the waitlist at support@zapat.ai.
How BYOC will work
- Zapat's control plane receives webhooks from GitHub and manages the pipeline state.
- When a job is dispatched, instead of running it on Zapat's compute, the job runs on your own infrastructure in an isolated container.
- Your container clones the repo, runs the AI agent using your own API key, and pushes results back to GitHub.
- Job metadata, status, and cost estimates are reported back to Zapat's control plane for dashboard visibility.
- Source code is processed entirely within your network.
Current managed compute
Today, all Zapat jobs run on managed Fargate containers in isolated VPC subnets. Each job gets a dedicated container with 2 vCPU, 4 GB RAM, and 21 GB ephemeral storage. Containers are destroyed after each job — no data persists between jobs.
Managed compute vs. BYOC (coming soon)
- Managed (available now): zero setup, pay-per-issue pricing, isolated containers, Zapat handles all infrastructure.
- BYOC (coming soon): code stays in your infrastructure, you pay your AI provider directly, lower Zapat orchestration fee, requires your own cloud account.
Was this article helpful?