Bahama Cloud

Bahama Cloud is the first-party managed path through Bahama. One account gives your coding agent one coherent place to create the application project, configure its server environment, add a database or storage bucket, deploy source, and verify the live result.

Ask your agent for the outcome

For a supported project, you can simply say:

Use Bahama Cloud to deploy this application. Handle the configuration and
commands for me, explain important choices, and stop when Bahama needs my
approval.

Your agent reads the Bahama skill, inspects the application, confirms that the framework fits, writes bahama.yaml, and asks the CLI for a plan. You only step in to sign in and approve consequential work.

What Cloud manages

• an application project and stable project name;
• builds and deployments for supported application shapes;
• server-side project variables and secrets;
• native SQL database if needed
• S3-compatible object storage (coming soon)
• scoped access to that database during local development;
• a verified public application URL; and
• project status and usage in the Bahama dashboard.

These pieces use the same manifest, approval rules, and verified execution as every Bahama provider. Cloud is not a separate workflow your agent has to learn.

A minimal Cloud project

For a Vite application, your agent may write:

version: 1
project:
  name: hello-bahama
 
application:
  framework: vite-spa
 
environments:
  local:
    provider: local
  production:
    provider: bahama-cloud

Writing this file creates nothing. The agent runs bahama plan, shows you the project and account Bahama intends to use, and applies the plan only after you approve it.

Sign in once

When Bahama returns auth required, your agent starts:

bahama auth login bahama-cloud

You complete the consent page in your browser. In a headless workspace, the agent can add --no-browser and give you the displayed URL and one-time code. Normal planning and deployment commands never start a login silently.

Choose a Cloud guide