# Lizard

Lizard Pro costs $19 a month with $19 in monthly credits for apps, databases, Sandboxes, storage and egress. Once you use your credits, pay as you go at the published rates. There are no seat fees. New accounts start with a 7-day trial and $5 in trial credits; starting the trial needs a card. Resource rates and plan terms: https://lizard.build/pricing

> Deploy apps from Claude Code, Codex, Cursor or another coding agent with Lizard CLI. Lizard builds and runs the apps alongside Managed Postgres, Managed Redis and Managed Object Storage. Agents can read each command's schema with `--json` and load the usage guide that matches the installed CLI. Errors and exit codes let an agent check what failed and choose the next step.

## For AI agents (start here)

- Install Lizard Skill with `npx skills add lizard-build/skill -g`. It guides the agent through CLI installation, login and platform commands.
- Load the full, version-matched guide: `lizard skills get core --json` (the `content` field is the complete platform guide: build pipeline, env precedence, addons, exit codes)
- Discover any command at runtime: `lizard <cmd> --help --json`
- Deploy from the current directory: `lizard up` (or `lizard add -r owner/repo` for a GitHub source)
- Resource hierarchy: `workspace → project → service (+ managed addons)`
- Always pass `--json` on non-interactive calls; confirm destructive actions; scope secrets to the consuming service.
- Prefer Markdown over HTML: append `.md` to any docs URL for the page as plain Markdown, no nav or footer: `https://lizard.build/docs/cli/` becomes `https://lizard.build/docs/cli.md`. Docs only; the marketing pages have no `.md` form.
- Every docs page, with a one-line summary, in sidebar order: https://lizard.build/docs/llms.txt
- All docs pages in one file: https://lizard.build/docs/llms-full.txt
- [AI Agents & MCP](https://lizard.build/docs/agents.md): how agents install and use Lizard
- [Deploy from Claude Code, Codex or Cursor](https://lizard.build/docs/guides/deploy-from-coding-agent.md): Lizard Skill and Lizard CLI from a coding agent, GitHub or local source, a database, and checks

## Docs

- [Introduction](https://lizard.build/docs/index.md): what Lizard is and how it fits an agent workflow
- [Quickstart](https://lizard.build/docs/getting-started.md): install, log in, first deploy
- [CLI reference](https://lizard.build/docs/cli.md): all commands, per-command flags and examples
- [JSON & automation](https://lizard.build/docs/cli/json.md): `--json` output shapes and streaming events

## Deploying

- [Deploy from GitHub](https://lizard.build/docs/deploy/github.md): git source with git push to deploy webhooks
- [Deploy from local code](https://lizard.build/docs/deploy/upload.md): tarball upload via `lizard up`
- [Background workers](https://lizard.build/docs/deploy/workers.md): non-HTTP services (`containerPort=0`)
- [Scaling](https://lizard.build/docs/deploy/scaling.md): replicas and resources
- [Regions](https://lizard.build/docs/deploy/regions.md): where services run
- [Service never becomes healthy](https://lizard.build/docs/deploy/troubleshooting/service-never-healthy.md): ports, health checks and start commands

## Framework guides

- [Overview](https://lizard.build/docs/framework-guides.md): build commands, adapters and ports for each framework
- [Next.js](https://lizard.build/docs/framework-guides/nextjs.md): Node.js server with `next start` on port 3000
- [FastAPI](https://lizard.build/docs/framework-guides/fastapi.md): Uvicorn, a Procfile and port 8000
- [Django](https://lizard.build/docs/framework-guides/django.md): Gunicorn, migrations and static files
- [React (Vite)](https://lizard.build/docs/framework-guides/react.md), [Vue (Vite)](https://lizard.build/docs/framework-guides/vue.md), [Astro](https://lizard.build/docs/framework-guides/astro.md), [Nuxt](https://lizard.build/docs/framework-guides/nuxt.md), [SvelteKit](https://lizard.build/docs/framework-guides/sveltekit.md): frontends and full-stack frameworks
- [Docusaurus](https://lizard.build/docs/framework-guides/docusaurus.md), [VitePress](https://lizard.build/docs/framework-guides/vitepress.md), [Hugo](https://lizard.build/docs/framework-guides/hugo.md): static documentation sites
- [Tested versions & results](https://lizard.build/docs/framework-guides/validation.md): what each guide was checked against

## Guides

- [Host a remote MCP server](https://lizard.build/docs/guides/deploy-mcp-server.md): Streamable HTTP, bearer-token checks and a health endpoint
- [Run a Telegram bot](https://lizard.build/docs/guides/telegram-bot.md): a long-polling bot as a worker with one replica
- [Run Umami](https://lizard.build/docs/guides/umami.md): web analytics with Managed Postgres
- [Run Flowise with PostgreSQL](https://lizard.build/docs/guides/flowise.md): keep the credential encryption key across restarts
- [Variables & secrets](https://lizard.build/docs/variables.md): scoping and precedence
- [Cross-service references](https://lizard.build/docs/variables/references.md): connect services and addons with `${{...}}`
- [Networking & custom domains](https://lizard.build/docs/networking.md): attach and verify domains
- [Run & SSH](https://lizard.build/docs/cli/run.md): run local commands with a service's variables; shell access to services is turned off

## Managed addons

- [Overview](https://lizard.build/docs/addons.md): provision with `lizard add <type>`, reference via `${{<name>.KEY}}`
- [Postgres](https://lizard.build/docs/addons/postgres.md): Managed Postgres (`DATABASE_URL`, `PG*`)
- [Redis](https://lizard.build/docs/addons/redis.md): Managed Redis (`REDIS_URL`)
- [Object storage (S3)](https://lizard.build/docs/addons/storage.md): S3-compatible storage; the default bucket is private

## Sandboxes

- [Overview](https://lizard.build/docs/sandboxes.md): runtime, templates, lifecycle, resource limits, storage and billing
- [Quickstart](https://lizard.build/docs/sandboxes/quickstart.md): create a sandbox with the Lizard SDK, run Python, work with files
- [SDK reference](https://lizard.build/docs/sandboxes/sdk-reference.md): every Lizard SDK method for JavaScript and Python
- [Code interpreter](https://lizard.build/docs/sandboxes/code-interpreter.md): run LLM-generated Python in the interpreter template
- [Persistent Volumes](https://lizard.build/docs/sandboxes/volumes.md): keep files at /workspace across sandbox runs
- [`lizard sandbox`](https://lizard.build/docs/cli/sandbox.md) and [`lizard agents`](https://lizard.build/docs/cli/agents.md): sandboxes and coding agents (Codex, Claude Code, OpenCode) from the CLI

## Limits & operations

- [Billing](https://lizard.build/docs/platform/billing.md): trial, pay as you go usage, failed payments, cancelling
- [Limits](https://lizard.build/docs/platform/limits.md): replicas, Sandboxes resources and timeouts, regions, quotas
- [Storage & recovery](https://lizard.build/docs/platform/storage-and-recovery.md): what survives a restart, a redeploy or a host failure
- [Known issues](https://lizard.build/docs/platform/known-issues.md): current caveats to check before relying on a workflow

## Observability

- [Logs](https://lizard.build/docs/observability/logs.md): runtime and build logs
- [Metrics & cost](https://lizard.build/docs/observability/metrics.md): CPU, memory, network, disk, and cost tracking
- [Events & history](https://lizard.build/docs/observability/events.md): deploy history and replica status

## Concepts

- [Architecture](https://lizard.build/docs/concepts/architecture.md): pods, regions, and nodes
- [Build pipeline](https://lizard.build/docs/concepts/build-pipeline.md): lizardpack auto-detect, Dockerfile handling
- [Deployments](https://lizard.build/docs/concepts/deployments.md): how a deploy proceeds

## Product

- [Lizard CLI](https://lizard.build/cli): deploy any app from the terminal with `lizard up`
- [Sandboxes](https://lizard.build/sandboxes): Firecracker microVMs, each with its own kernel, for agent commands and files; attach a volume at /workspace for persistent files, set a lifetime, and stop each sandbox after use
- [Managed Postgres](https://lizard.build/postgres): provisioned and wired into your services; see storage & recovery for what to back up yourself
- [Managed Redis](https://lizard.build/redis): in-memory store for caching, queues, and sessions
- [Managed Object Storage](https://lizard.build/object-storage): S3-compatible buckets for uploads, assets, and backups
- [Lizard Studio](https://lizard.build/studio): free Chrome extension for Claude Code and ChatGPT to inspect a live page and edit a local project
- [Pricing](https://lizard.build/pricing): plans and what each resource costs

## Comparisons

Each comparison uses the other platform's published prices and lists the date we last checked them.

- [All comparisons](https://lizard.build/compare): the index, 9 platforms
- [Lizard vs Vercel](https://lizard.build/compare/vercel): Compare container limits, first-party Postgres and Redis, and per-vCPU price
- [Lizard vs Netlify](https://lizard.build/compare/netlify): Netlify bills in credits and runs no long-lived processes. Compare backends, databases and cost
- [Lizard vs DigitalOcean App Platform](https://lizard.build/compare/digitalocean): compare droplet sizing and app specs with a one-command deploy, including setup, databases and price
- [Lizard vs Firebase](https://lizard.build/compare/firebase): Firestore bills per read and provides no server process. Compare Postgres, Redis, S3 and server hosting
- [Lizard vs Supabase](https://lizard.build/compare/supabase): Supabase hosts the database; your app runs elsewhere. Compare hosting both in one project with PostgreSQL 18
- [Lizard vs AWS](https://lizard.build/compare/aws): a container on AWS needs ECS, a VPC, an ALB, IAM and a registry. Compare setup and egress at $0.045/GB
- [Lizard vs AWS Lambda](https://lizard.build/compare/lambda): Lambda caps at 15 minutes and bills per request. Compare long-running work and cold starts
- [Lizard vs Cloudflare Workers](https://lizard.build/compare/workers): Workers run V8 isolates rather than Node. Compare native modules and long-lived processes
- [Lizard vs self-hosted PaaS](https://lizard.build/compare/self-hosted): what Coolify and Dokploy do on your own VPS, and what they cost to run

## Templates

Deploy an app and its addons together in one click, with their connections set up.

- [All templates](https://lizard.build/deploy): the catalogue
- [Deploy n8n](https://lizard.build/deploy/n8n--n8n): workflow automation, with its database provisioned and connected
- [Deploy OpenClaw](https://lizard.build/deploy/openclaw--openclaw): self-hosted agent runtime

## Blog

- [Blog index](https://lizard.build/blog): build notes, product updates, and what we learn running other people's apps on Lizard
- [E2B vs Daytona vs Modal: 1,200 sandbox starts compared](https://lizard.build/blog/e2b-vs-daytona-vs-modal): We timed 300 sandbox starts each on E2B, Daytona, Modal and Lizard. Compare the results, resource costs and limits, with the method and raw data.
- [Claude Code --dangerously-skip-permissions: usage and limits](https://lizard.build/blog/dangerously-skip-permissions): Use Claude Code without routine approval prompts. See what bypass mode changes, how auto mode differs, and how to run a bounded job in a disposable workspace.
- [Vercel Sandbox pricing: costs, limits, and alternatives](https://lizard.build/blog/vercel-sandbox-pricing): Calculate what Vercel charges for CPU and memory, compare four providers, and see when Lizard costs less.
- [Cheap Postgres Hosting: What Small Databases Really Cost](https://lizard.build/blog/cheap-postgres-hosting): Compare six Postgres hosts for a small project, work through two cost examples, and check storage, backups and upgrade costs before you choose.
- [Codex Exec: Automate Deployment Checks from the Terminal](https://lizard.build/blog/codex-exec): Build a non-interactive Codex workflow with HTTP evidence, JSONL events and a validated final report. Includes working and failing application tests.
- [Claude Code Headless: Check Your Deployment from the Terminal](https://lizard.build/blog/claude-code-headless): Run Claude Code without a chat session. Check HTTP responses and real app behavior, generate a JSON report and fail the job when a route breaks.
- [Redis MCP: Connect Your AI Agent to Your Database](https://lizard.build/blog/redis-mcp): Connect Cursor or Claude Desktop to Redis through the official MCP server. Read demo keys, inspect TTLs and verify that Redis blocks writes and unrelated data.
- [AI Agent Memory with Redis: Remember Users Across Sessions](https://lizard.build/blog/redis-agent-memory): Build an agent that remembers a user's preference after an app restart. A tested Python example with Redis, session history, TTLs and a forget command.
- [Postgres MCP: connect your AI agent to a database](https://lizard.build/blog/postgres-mcp): Connect Cursor to Postgres through MCP with a reader role, tested package versions and queries that verify both data access and write restrictions.
- [Fly.io pricing in 2026: free tier, app costs and alternatives](https://lizard.build/blog/fly-io-pricing): Fly.io app budgets from $2.14 to $57.39, free trial terms, and a worked comparison with Lizard for an always-on app, with and without a database.
- [ChatGPT Chrome extensions for developers: what to check](https://lizard.build/blog/chatgpt-chrome-extension-for-developers): Choose a ChatGPT Chrome extension by its page tools, project connection and source review workflow. Includes a repeatable CSS trial.
- [ChatGPT website editor: fix an existing site in Chrome](https://lizard.build/blog/chatgpt-website-editor): Connect ChatGPT to your local website, fix a reproducible mobile layout bug and check the source diff and rendered result.
- [Claude Code GUI: choose an interface for your workflow](https://lizard.build/blog/claude-code-gui): Compare five Claude Code interfaces by where you work, how you attach page context and how you review source edits. Includes a repeatable evaluation.
- [Claude Code visual editor: select an element and fix its CSS](https://lizard.build/blog/claude-code-visual-editor): Use Lizard Studio to select a page element, change a CSS gap in your local source and verify the result after a refresh. Includes a downloadable exercise.
- [How to deploy a Cursor app with PostgreSQL](https://lizard.build/blog/deploy-cursor-app-postgres): Deploy a Next.js app from Cursor with Managed Postgres. Use a ready-to-paste prompt, connect the database, run migrations, and check saved data.
- [n8n webhook to Postgres: a deployment example on Lizard](https://lizard.build/blog/n8n-webhook-postgres-example): A reproducible n8n example: receive JSON, store it in Postgres and return the saved row. Includes authentication and checks after a service restart.
- [AWS App Runner: current status, pricing and alternatives](https://lizard.build/blog/aws-app-runner): What App Runner's new-customer restriction means, how to estimate an existing service's bill, and how to evaluate a replacement without rushing the data move.
- [Replit alternatives: replace the editor, agent or hosting](https://lizard.build/blog/replit-alternatives): Replit combines building and publishing. This guide separates those jobs so you can choose a replacement and move your app without losing data or configuration.
- [Best PaaS providers: choose by workload and total cost](https://lizard.build/blog/best-paas-providers): Choose a PaaS for your workload. Compare costs with worked Render and Fly.io examples, database charges and the limits of free plans.
- [Container as a service: how it works and what it costs](https://lizard.build/blog/container-as-a-service): A developer's guide to container hosting: the responsibilities a provider takes over, the ones you keep, and the inputs a cost estimate needs.
- [Heroku alternatives: how to choose and migrate safely](https://lizard.build/blog/heroku-alternatives): Evaluate Lizard, Railway, Render, Cloud Run and a VPS as Heroku alternatives. Includes a migration checklist for processes, databases and add-ons.
- [E2B sandboxes: pricing, lifecycle and alternatives](https://lizard.build/blog/e2b-sandbox): Current Sandboxes runtime, templates, lifecycle, resource limits, storage, and billing. Includes an illustrative E2B cost comparison.
- [Kubernetes alternatives: choose the control you need](https://lizard.build/blog/kubernetes-alternatives): A Kubernetes alternative should remove work you do not need while keeping the controls your app relies on. Compare seven practical approaches.
- [How to deploy a Django app on a VPS with Gunicorn and nginx](https://lizard.build/blog/deploy-django-app-vps): A Django VPS deployment walkthrough with a dedicated app user, PostgreSQL, a managed process, reverse proxy, HTTPS and checks for updates and recovery.
- [Python app hosting: deploy Django, Flask and FastAPI](https://lizard.build/blog/python-app-hosting): Match a Python host to WSGI or ASGI, workers, persistent data and your budget. Includes production command examples and checks for a working deployment.
- [Firebase alternatives: match the backend you need](https://lizard.build/blog/firebase-alternatives): Choose a Firebase replacement by the services your app uses. Compare backend products with hosting your own API, and understand the migration work.
- [Google Antigravity: how to deploy your app to production](https://lizard.build/blog/google-antigravity-how-to-deploy-your-app-to-production): Deploy to a public HTTPS URL, connect your database and check saved data: four steps from your Antigravity project to a working app.
- [Deploy from Claude Code: a practical Lizard workflow](https://lizard.build/blog/deploy-from-claude-code): Give Claude Code a repeatable deployment workflow: inspect the repository, read current CLI help, deploy the right service and test the result.
- [Vercel alternatives: choosing a host for your backend](https://lizard.build/blog/vercel-alternative): Choose a Vercel alternative by runtime, database needs and total cost. Includes checked billing terms and a migration plan for APIs and workers.
- [Welcome to the Lizard blog](https://lizard.build/blog/welcome-to-the-lizard-blog): Read practical deployment guides and hosting comparisons, with sources for product claims and clear assumptions behind cost examples.