Get started
The BeansHost platform

The control plane between your repository and your cloud.

BeansHost connects your GitHub repository, validates the agent specification, deploys the agent into your own cloud account, gives it an API and keeps its releases, runs, secrets and approvals in one organization workspace.

Get startedEvery step explained
app.beanshost.com
AAcme Inc.
Build
Ship
Operate
Govern
Deployment

support-triage

production · Amazon ECS Express Mode

Active
Regioneu-west-1
Versionv1 · a41c9e2
Health/health
Deployment logsLive
  1. Environment variables synced
  2. Image built with AWS CodeBuild
  3. Image pushed to Amazon ECR
  4. Health check passed
  5. Deployment active
A control plane, not a hosting platform

One operating model across every provider.

BeansHost records what should run, which commit it came from and who approved it. Your Vercel, Render, AWS or Azure account runs the agent. AWS connections can use an IAM role with an external ID instead of long-lived keys.

Source
acme/support-triage
beanshost.yaml · main · a41c9e2
Your applications
Web app, backend, workflows
POST /agents/{id}/invoke
BeansHost control planeOrganization scoped
  • Agent registry
  • Deployments
  • Secrets
  • Agent API and keys
  • Runs and usage
  • Roles
  • Audit log
  • Approvals

Decides what runs, where, and keeps the record. Never stores prompts or responses.

Your cloud account
VercelVercel Edge Networkagent
RenderRender managed servicesagent
AWSAmazon ECS Express Modeagent
AzureAzure Container Appsagent
BeansHost keeps

Configuration, coordination and the record.

OrganizationsProjectsEnvironmentsAgent versionsDeploymentsEnvironment variablesAPI keysRunsUsagePlansApprovalsAudit events
Your cloud keeps

Execution, scaling and the infrastructure bill.

Vercel projectsRender servicesECS servicesECR imagesCodeBuild projectsContainer AppsAzure Container RegistryLog Analytics
Capabilities

What you can do in BeansHost today.

Each capability is in the console now. The label shows the lowest plan that includes it. BeansHost is in early access, and the console marks preview features clearly.

Builder

GitHub connections

Authorize with GitHub, pick a repository and branch, and BeansHost resolves the exact commit. Private repositories are supported and marked.

Builder

Generated beanshost.yaml

When a repository has no specification, BeansHost AI analyzes its structure, writes a tailored file and commits it to your branch for review.

Builder

Immutable agent registry

Register from source or start with the Hello Agent sample. Every version is pinned to an exact commit and a SHA-256 checksum.

Builder

Encrypted environment variables

Per project and environment, encrypted with AES-256-GCM, synchronized to the provider and never displayed again.

Builder

Multi-cloud deployment

Vercel, Render, Amazon ECS Express Mode or Azure Container Apps, with build logs and health-checked activation.

Builder

An API for every agent

Development and Production endpoints, agent-scoped keys, ready-made code and an OpenAPI file for each agent.

Builder

Executions and usage

Runs, success rate, p95 duration and failures by category, plus monthly usage against your plan.

Team

Production and rollback

Separate development and production environments, health-gated promotion and rollback to the last healthy deployment.

Team

Roles and audit log

Seven built-in roles and an append-only audit log of privileged actions with search, filters and CSV export.

Enterprise

Production approvals

Risk-based policy, approve or deny with a reason, optional separation of duties and an evidence timeline.

Deploy targets

Four providers. One deployment history.

Every provider has guided setup, a deployment summary and a live view of the release. Deployment history shows every agent, wherever it runs.

VercelVercel Edge Network
Connect
Connect your Vercel account with OAuth.
Build and run
BeansHost creates the Vercel project and deploys the registered commit.
  • Environment variables synchronized to the Vercel project
  • Build and deployment logs in the console
  • Served on the project's Vercel production URL
RenderRender managed services
Connect
Connect with a Render API key.
Build and run
Choose the runtime, plan, region and the build and start commands for each service.
  • Environment variables synchronized to the Render service
  • Build and deployment logs in the console
  • Served on the service's Render URL
AWSAmazon ECS Express Mode
Connect
Connect a cross-account IAM role with an external ID, or access keys.
Build and run
BeansHost builds the image with CodeBuild, pushes it to Amazon ECR and runs it on ECS.
  • Images built inside your own AWS account
  • Eight supported regions in the US, Europe and Asia Pacific
  • Build readiness checklist before the first deployment
AzureAzure Container Apps
Connect
Sign in with Microsoft Entra and choose a subscription.
Build and run
BeansHost prepares the resource group, registry and Container Apps environment, then builds with ACR Tasks.
  • Secrets injected as Container App secrets
  • Build and deployment status in the console
  • No passwords or long-lived keys to paste
AWS regions: us-east-1, us-east-2, us-west-2, eu-west-1, eu-central-1, ap-south-1, ap-southeast-1, ap-northeast-1. Azure deployments default to East US. Your provider bills the infrastructure your agents use.
Release safety

Known code in, healthy agent out.

Before a deployment touches your cloud, BeansHost checks that the commit and checksum still match the registered version. After it deploys, the release only becomes active once the agent answers on its health path.

See every deployment state

Pinned

Every version records its repository, branch, commit and SHA-256 checksum.

Health-gated

Activation waits for the health path, with a timeout you set from 1 to 30 seconds.

Logged

Build and deployment logs from Vercel, Render and AWS, and build and deployment status from Azure, sit with each release.

Recoverable

Team plans can roll back to the last healthy deployment through the API.

Coming next

What we are building next.

BeansHost labels unfinished work in the console instead of hiding it. These capabilities are on the way and are not available yet. Agents call their model providers directly today.

  • GitLab, Bitbucket and Azure DevOps source connectionsPlanned
  • A model gateway with routing, budgets and token usagePlanned
  • Scheduled and queue-triggered runsPlanned
  • Service accounts for product integrationsPlanned
  • Google Cloud as a deploy targetPlanned