Frameworks

Framework support belongs to provider drivers. Bahama does not claim that every host can run every application.

Your agent combines two live sources before choosing:

bahama inspect --json
bahama providers --format agent

Inspection reports evidence from the repository. The provider catalog reports what the installed Bahama version can operate and verify.

Current supported paths

This table is a snapshot of the current official drivers, not a permanent list. The targeted provider guide remains the source of truth:

bahama providers bahama-cloud --format agent

The manifest records the agreement

application:
  framework: nextjs
 
environments:
  production:
    provider: vercel

Every hosted environment must support the application framework. If the live provider framework disagrees with the manifest, the next deployment pauses for review instead of silently correcting production.

For a monorepo, application.dir identifies the deployable application:

application:
  framework: vite-spa
  dir: apps/web

Cloud framework contracts

Cloud static targets need a deployable index.html. Vite targets need Vite, a build script, and one supported lockfile. Hono targets export an application from server/index.* rather than starting a Node server.

See Applications and deployments for the complete build, routing, and packaging contracts.

Vercel maps both vite-spa and vite-hono to its native vite project preset, while hono-api maps to hono. The manifest still records the real application shape. A Vite + Hono repository must already expose its backend through Vercel’s supported Hono entry or function-routing conventions; Bahama does not generate provider-specific entry files or rewrite source. Vite + Hono and Hono API deployments also declare a public config.healthPath, allowing Bahama to verify the backend rather than only the frontend root.

When the application does not fit

Your agent should explain the mismatch and offer only technically sensible choices:

• keep the application and choose another supported provider;
• deliberately convert the framework when that work serves the product; or
• explain that Bahama cannot manage this deployment yet.

It should not convert Next.js to Vite merely to prefer Cloud, nor select a provider that cannot run the application’s required server behavior.