Get started
How BeansHost works

From a GitHub repository to a governed production agent.

Fifteen steps across five phases, in the same order the BeansHost console walks you through them. Here is exactly what happens at each one.

Get startedStart at step one
  1. PHASE 1 · WORKSPACE

    Set up your workspace.

  2. PHASE 2 · BUILD

    Bring in the agent code.

  3. PHASE 3 · SHIP

    Deploy into your own cloud.

  4. PHASE 4 · OPERATE

    Connect it to your product.

  5. PHASE 5 · GOVERN

    Keep control as you grow.

Phase 1 · Workspace

Set up your workspace.

An account, an organization that holds everything, a plan and a first project. About five minutes.

  1. STEP 01

    Create your account

    Sign up with your full name, work email and a password of at least eight characters, then confirm the six-digit code BeansHost emails you.

    • Invited teammates get a code by email and set their own password
    • Sign-in attempts are throttled to slow down guessing
  2. STEP 02

    Create an organization

    Give it a name and a URL slug. The organization is your tenant boundary: members, projects, usage and audit history live inside it, and nothing crosses into another organization.

    • Belong to several organizations and switch between them
    • Requests for another organization's resources answer not found
  3. STEP 03

    Choose a plan

    Builder at $5 per month unlocks connections, agent registration and deployment. Team at $49 per month adds production, rollback and members. Checkout runs through Stripe, and promotion codes are accepted.

    • Coming from the pricing page preselects the plan you chose
    • Manage the card, invoices and cancellation in the Stripe portal
  4. STEP 04

    Create a project

    A project groups related agents, their environment variables and deployments. Every new project gets a Development environment straight away, and Team plans add Production.

    • Environment variables are kept per project and environment
    • Usage can be broken down by project
Phase 2 · Build

Bring in the agent code.

BeansHost works with the code you already have. Connect the repository, describe the agent once and register an exact version.

  1. STEP 05

    Connect GitHub

    Authorize BeansHost with GitHub, then choose the project, the repository and the branch. Private repositories are listed and clearly marked.

    • GitLab, Bitbucket and Azure DevOps are shown as coming soon
    • Deployments start from the console or API, not on every push
  2. STEP 06

    Define it in beanshost.yaml

    The specification sets the runtime, entrypoint, health path, triggers, secret names, retries and timeout, risk level and observability. BeansHost validates it before anything else happens.

    • No file yet? BeansHost AI analyzes the repository, writes one and commits it to your branch
    • The runtime is detected from the repository, not guessed
  3. STEP 07

    Register an immutable version

    Registering resolves the branch to an exact commit, validates the manifest and stores the version with a SHA-256 checksum. Every later deployment is checked against both.

    • Start from source, or try the platform with the Hello Agent sample
    • Agents with an active deployment cannot be deleted by accident
Phase 3 · Ship

Deploy into your own cloud.

Pick the provider, add environment variables and release. The agent runs in your account and only goes live once it is healthy.

  1. STEP 08

    Connect a cloud account

    Vercel connects with OAuth, Render with an API key, AWS with a cross-account IAM role and external ID or access keys, and Azure with a Microsoft Entra sign-in and a subscription choice.

    • AWS and Azure run a build readiness checklist first
    • AWS deployments run in one of eight supported regions
  2. STEP 09

    Add environment variables

    Store each variable once per project and environment. Values are encrypted in BeansHost, synchronized to Vercel and Render or injected as Azure Container App secrets, and never displayed again.

    • beanshost.yaml lists secret names only, never values
    • Separate values for development, preview and production
  3. STEP 10

    Deploy and watch it go live

    Review the deployment summary and deploy. Worker agents are packaged directly. Containers use your Dockerfile, or a generated one for Node.js 22 or Python 3.12, built with CodeBuild on AWS or ACR Tasks on Azure.

    • Build and deployment logs stream into the console
    • The release turns active only after the health path answers
    • Redeploy at any time from deployment history
Phase 4 · Operate

Connect it to your product.

Every deployed agent is an API your applications can call, with its runs and usage recorded as they happen.

  1. STEP 11

    Call the agent through its own API

    Choose API on the agent to see its endpoint for Development and Production, create keys limited to that agent and copy the call in curl, JavaScript or Python. Download an OpenAPI file for other tools.

    • Keys start with bhk_, are shown once and stored only as a hash
    • Expiry of 30 days, 90 days, one year or never
    • Test run calls the agent without leaving the console
    • Use the same key from any server, API client, gateway or workflow tool
  2. STEP 12

    Follow runs and usage

    Executions lists every run, whether BeansHost made the call or the agent reported it, with status, timing, size and provider. Usage shows this month or last against your plan.

    • Filter by agent, status, provider and source over 24 hours, 7 days or 30 days
    • A warning appears at 80 percent of your monthly runs
Phase 5 · Govern

Keep control as you grow.

Bring in your team with the right access, keep a record that cannot be rewritten and put a person in front of production.

  1. STEP 13

    Invite your team

    On Team and above, invite members by email and assign one of seven roles, from Organization Owner to Viewer. Only an owner can change another owner, and the last owner cannot be removed.

    • Settings shows what each role can access
    • Nobody below owner can change their own roles
  2. STEP 14

    Review the audit log

    Privileged actions on members, API keys, projects, secrets, connections, agents, deployments, governance and billing are written to an append-only log. Filter, search and export it as CSV.

    • Recorded on every plan, readable for 90 days on Team and 365 on Enterprise
    • Secret values are never written to the log
  3. STEP 15

    Approve production releases

    On Enterprise, choose which risk levels need a person. Matching production releases wait in Awaiting approval until an owner or admin approves or denies them with a reason, and every decision joins the evidence timeline.

    • Optionally stop requesters from approving their own release
    • If governance cannot answer, production fails closed