Skip to main content

Documentation Index

Fetch the complete documentation index at: https://libretto.sh/docs/llms.txt

Use this file to discover all available pages before exploring further.

Run Libretto workflows somewhere other than Libretto Cloud Hosting.
Libretto Cloud Hosting is the managed Libretto platform. Alternative providers are useful when you want to keep Libretto’s CLI and workflow runtime, but choose a different browser or infrastructure layer. There are two common patterns:

Managed browser providers

Kernel and Browserbase host the browser session. Libretto connects to that browser over CDP and runs the same local commands and workflow code.

Self-hosted cloud infrastructure

GCP and AWS run your workflow package as a container job. You own the runtime, scheduler, network, secrets, and artifacts.

​
Providers

Kernel

Use Kernel as the managed browser provider for open and run.

Browserbase

Use Browserbase as the managed browser provider for open and run.

GCP

Run workflows as Cloud Run Jobs with Artifact Registry, Cloud Build, and Secret Manager.

AWS

Run workflows as ECS Fargate tasks with ECR, CodeBuild, and Secrets Manager.

​
How provider selection works

Libretto chooses a browser provider in this order:
  1. The --provider flag on open or run
  2. LIBRETTO_PROVIDER in the environment
  3. provider in .libretto/config.json
  4. local
Put provider credentials in the repo root .env file. Libretto loads that file automatically before running CLI commands. Put the persistent provider choice in .libretto/config.json so open and run use the same browser provider without repeating --provider.

​
Choosing an option

Use Kernel or Browserbase when you only want to move browser execution to a managed provider. Use GCP or AWS when you want to own the full workflow hosting stack. If you want Libretto to manage hosting, workflow deployment, job APIs, schedules, and failure diagnostics for you, use Libretto Cloud Hosting.