Connect a GitHub repository, validate beanshost.yaml and deploy to Vercel, Render, AWS or Azure. Every agent gets its own API, and BeansHost keeps each release, run, secret and approval in one control plane.
production · Amazon ECS Express Mode
Your team writes the agent. BeansHost takes care of everything between the repository and production, so you spend your time on what the agent does instead of how it gets deployed.
No deployment scripts, Dockerfiles or manifests to write by hand. BeansHost generates what is missing, builds the agent and only lets it go live once it is healthy.
Agents run in the Vercel, Render, AWS or Azure account you already pay for, so existing discounts, credits and billing alerts still apply. BeansHost is a flat plan on top.
One manifest works across four providers. Moving an agent from Render to AWS is a deployment choice, not a rewrite, and your release process stays the same.
Each agent gets an HTTPS endpoint, keys limited to that agent, and ready-made code in curl, JavaScript and Python. Hand it to another team without sharing cloud access.
Every release is pinned to a commit and checksum and checked against its health path before it takes traffic. On Team, roll back to the last healthy deployment.
Success rate, p95 duration, failures and usage for every agent, plus roles, an append-only audit log and production approvals. Prompts and responses are never stored.
BeansHost sits beside your infrastructure, not in place of it. It deploys from your repository into your own cloud account and gives your applications one stable way to call every agent.
beanshost.yaml · main · a41c9e2POST /agents/{id}/invokeDecides what runs, where, and keeps the record. Never stores prompts or responses.
The console follows the same path: Organize, Connect, Define, Deploy, Operate and Govern. Each agent version keeps its commit, specification, deployment and runs connected.
Create an organization and a project. A development environment is added for you.
Sign in to GitHub, pick a repository and branch, and link the cloud account you deploy into.
Validate beanshost.yaml, or let BeansHost AI write one, then register the agent at an exact commit.
Add environment variables, review the summary and deploy while the build logs stream in.
Call the agent through its own API, then follow runs, failures and monthly usage.
Assign roles, review the audit log and approve production releases before they go live.
Walk through every screen, from sign up to the first production run.
The full workflowChoose API on an agent in the console and you get its HTTPS endpoint for Development and Production, keys limited to that one agent, and code ready to paste in curl, JavaScript or Python.
curl -X POST "https://app.beanshost.com/api/v1/runtime/agents/$AGENT_ID/invoke?environment=production" \
-H "Authorization: Bearer $BEANSHOST_API_KEY" \
-H "Content-Type: application/json" \
-d '{"message": "Hello"}'{
"executionId": "0b6c2f7e-6d2a-4a0e-9d55-2f4f1c9e8a10",
"correlationId": "req_8f2d1c",
"status": "succeeded",
"data": { "reply": "The agent's own response" }
}Deployment is one step. BeansHost keeps the operating context around every agent, so your team can answer what changed, when, and why.
Runs through BeansHost and runs your agent reports itself, with status, duration, provider and error category. Never what was sent or answered.
Runs, failures, run time and data by day, agent and project, with a warning at 80 percent.
Environment variables per project and environment, encrypted with AES-256-GCM and never shown again.
Invite teammates by email and give each one exactly the access they need.
Scope keys to calling agents or reporting runs, limit them to one agent, and set an expiry.
Members, keys, secrets, connections, deployments, governance and billing, including refused attempts. Filter, search and export as CSV.
Releases pause in Awaiting approval until an owner or admin approves or denies them with a reason. Requesters can be stopped from approving their own release.
Deployment states, rollback and governance in detail.
Explore operationsEach provider has guided setup, a deployment summary and build logs. Deployment history shows every agent across all four, so switching providers never means switching tools.
Connect your Vercel account with OAuth. BeansHost creates the Vercel project and deploys the registered commit.
Connect with a Render API key. Choose the runtime, plan, region and the build and start commands for each service.
Connect a cross-account IAM role with an external ID, or access keys. BeansHost builds the image with CodeBuild, pushes it to Amazon ECR and runs it on ECS.
Sign in with Microsoft Entra and choose a subscription. BeansHost prepares the resource group, registry and Container Apps environment, then builds with ACR Tasks.
Regions, build paths and setup for each provider.
Compare deploy targetsConnect GitHub, generate or validate beanshost.yaml, deploy, then paste the ready-made API call into your app. No deployment scripts to write.
Developer referenceWatch deployment history across providers, follow runs and failures, manage environment variables and roll back to the last healthy release.
OperationsInvite members with roles, manage the plan through Stripe, export the audit log and approve production releases.
Security and accessBuilder is $5 per month and covers everything you need to connect, deploy and call agents. Team adds production, rollback and members. Enterprise adds approvals.
For individual builders shipping their first agents.
For teams running production agent workloads.
For organizations that need approvals and longer evidence trails.
What it does, where your agents run, what it records and what it costs.
Talk to the teamBeansHost is a control plane for AI agents. You connect a GitHub repository, describe the agent in a beanshost.yaml file and deploy it to your own Vercel, Render, AWS or Azure account. BeansHost gives every agent an API endpoint and keeps deployments, runs, secrets, members, usage, approvals and audit events for your organization in one place.
In your own cloud account. BeansHost deploys to Vercel, Render, Amazon ECS Express Mode or Azure Container Apps using the connection you authorize, so the infrastructure and its bill stay with you. BeansHost does not run your agent logic inside its control plane.
Any agent that answers HTTP requests and exposes a health path. JavaScript workers built on Web-standard APIs are packaged directly. Everything else runs as a container: if your repository has a Dockerfile, BeansHost uses it, and if not, BeansHost generates one for Node.js 22 or Python 3.12 with FastAPI, Flask or a plain script. No particular agent framework is required.
beanshost.yaml is the agent specification. It sets the runtime, entrypoint, health check, triggers, secrets, resilience, governance and observability settings. If your repository does not have one, BeansHost AI analyzes the repository, writes a starting file and commits it to the branch you chose so you can review and edit it like any other file.
Every agent has its own HTTPS endpoint with Development and Production tabs in the console. Create an API key for that agent, then POST any JSON body to the endpoint. BeansHost applies your plan's rate limits, forwards the body unchanged and returns the agent's answer with an execution ID. The console gives you ready-made curl, JavaScript and Python snippets and an OpenAPI file.
Yes. Any platform that can send an HTTPS request with a header can call your agent: your own backend, API clients such as Postman, API gateways, workflow and automation tools, partner systems or another agent. Create a key limited to that agent in the console, store it as a secret on the platform, and POST JSON to the agent's endpoint. You can also import the agent's OpenAPI 3.1 file instead of configuring the call by hand. Keep the key on a server, since browser requests from other websites are blocked.
Metadata only: status, duration, provider, error category, byte counts and correlation IDs. Prompt and response content is never stored. Executions shows success rate, p95 duration and the most common failure, and Usage shows runs against your plan for the month.
Creating an account and an organization is free. Connecting a repository or cloud account, registering agents, storing secrets, calling agents and deploying need the Builder plan at $5 per month or higher. Your cloud provider bills the infrastructure your agents use separately.
GitHub is supported today, including private repositories. GitLab, Bitbucket and Azure DevOps are shown as coming soon in the console. Deployments are started from the console or the API; deploy on push is not available yet.
Every member has one of seven roles, and privileged actions are written to an append-only audit log that you can filter and export as CSV. On Enterprise, production releases wait for approval from an owner or admin, who approves or denies with a reason. You can require that the person who requested a release cannot approve it.
Not yet. Each agent is served on its provider URL and called through its BeansHost endpoint, and custom domains are not available in BeansHost today. You can still put your own gateway or domain in front of the BeansHost endpoint.