From connected source to validated deployment, tenant-scoped runtime and execution visibility.
BeansHost is not an agent builder and it is not a thin cloud provider dashboard. It is the operating layer between the code your team owns and the runtime that serves real users and products.
Organizations, projects, environments, agents, versions, deployment plans, provider capability checks, health results and access decisions stay together in the BeansHost control plane.
Agent logic runs in isolated provider runtimes. BeansHost routes requests, applies limits, captures execution context and keeps development traffic separate from production.
Each capability is API-first and connected through versioned contracts, so teams can use the control plane directly or integrate BeansHost into their own products and delivery pipelines.
Connect supported source providers and define runtime, models, triggers, secrets, storage, health and governance in a versioned beanshost.yaml contract.
Explore agent definitionsValidate artifacts, create deployment plans, enforce approvals, run health checks, promote releases and roll back safely.
See the deployment lifecycleInvoke the active agent version through tenant-scoped HTTP APIs with rate limits, circuit breakers, timeouts and execution IDs.
Explore runtime accessFollow deployment health and execution metadata including status, latency, correlation IDs, trace IDs and provider context.
Explore observabilityDeclare models and triggers through portable contracts. Model adapters, scheduled work, queues, webhooks and durable jobs are planned expansions.
Explore agent executionSeparate organizations, projects and environments with role-based foundations, then connect fail-closed production decisions to ZonalGuard360 where configured.
Explore governanceEvery version keeps its source commit, specification, artifact, deployment state, health result and operating evidence connected.
Create an organization, project and isolated development and production environments.
Connect GitHub, GitLab, Bitbucket or Azure DevOps and register the agent, its owner and business purpose.
Describe runtime needs in beanshost.yaml and reject unsupported capabilities before deployment.
Verify the artifact, execute a deployment plan and activate traffic only after health checks pass.
Invoke the active version through tenant-scoped HTTP APIs with rate limits, timeouts, circuit breakers and execution IDs.
Monitor executions and usage, enforce approvals, publish evidence and roll back when required.
See how the services behind the control plane fit together.
Explore the platformBeansHost currently deploys supported workloads through its Cloudflare runtime integration. Portable specifications and provider adapters create a clear path to additional environments.
Describe runtime, models, triggers, storage, security and health through a portable agent specification.
Deploy supported agent workloads through the Cloudflare provider adapter with health-gated activation and rollback.
BeansHost validates the agent specification, artifact and required provider capabilities before deployment begins.
Additional provider adapters and an in-app runtime selector are planned without changing the logical agent definition.
Contact BeansHost for current runtime availability. The product will show selectable environments when additional provider integrations are ready for customer use.
Keep connected source, runtime configuration, releases and execution history connected.
Explore the operating lifecycleApply environment separation, role-based controls, provider checks, health gates and governance integration consistently.
Explore the control planeProducts such as Clintra and OptoGlide can integrate with BeansHost-managed agents while scoped machine access continues to expand.
See the Zonopact ecosystemBuilder, Team and Enterprise describe the intended product packaging. Final prices, limits and entitlements are confirmed during onboarding until in-app plan management is available.
A focused path from an agent repository to a validated development runtime.
Shared release and operational controls for teams running production agents.
Organization-level control for secure APIs, governance and complex agent estates.
From agent repository to secure runtime, monitoring and governance in one control plane.
Open BeansHostBeansHost is a vendor-neutral control plane for registering, validating, deploying and operating AI agents and AI-powered services. It connects source, portable configuration, deployment state, tenant-scoped runtime access and execution metadata without placing customer execution logic inside the control plane. Broader runtime, observability and governance capabilities expand through adapters and staged product releases.
BeansHost does not replace your agent framework or repository. You connect agent source from GitHub, GitLab, Bitbucket or Azure DevOps, describe its operational requirements in a BeansHost Agent Specification and use BeansHost to validate, deploy and operate the resulting service.
The BeansHost Agent Specification is a portable YAML or JSON contract for runtime type, source, health checks, scaling, models, triggers, secrets, storage, resilience, governance and observability. BeansHost validates the contract against capabilities implemented by the current provider integration before deployment begins. Declaring a capability does not mean every provider implements it.
BeansHost currently deploys supported workloads through its Cloudflare runtime integration. The portable agent specification and provider-adapter architecture are designed to add more environments without changing the logical agent definition. Additional provider adapters and an in-app runtime selector are planned. Contact BeansHost for current runtime availability.
BeansHost validates the agent specification and checksummed artifact, creates an idempotent deployment plan, checks supported provider capabilities, deploys through the current provider integration, runs health checks and activates traffic only after the release is healthy. Teams can promote versions between environments or roll back to a previous working version.
BeansHost currently records deployment state, health results and execution metadata such as status, duration, correlation IDs, trace IDs, provider context and byte counts. Full log browsing, model and token usage, cost estimates, quotas and alerts are planned expansions. Prompt and response content is not captured by default.
BeansHost separates organizations, projects and environments with tenant-scoped controls and role-based access foundations. ZonalGuard360 can provide fail-closed production decisions where configured. Complete service-account management, API-key lifecycle workflows, a governance workspace and broader audit evidence are planned expansions.
Builder, Team and Enterprise describe the intended BeansHost product paths. Final availability, prices, limits and entitlements are confirmed during onboarding until in-app plan management is available.