# Lizard documentation

Lizard builds and runs applications from a GitHub repository or a local folder. Use Lizard CLI or the dashboard to deploy a web service, run a background worker, connect Managed Postgres or Managed Redis, and inspect logs. Use Lizard SDK to create Sandboxes for code execution.

## Choose a task

| I want to… | Start here |
|---|---|
| Deploy my first app | [App quickstart](https://lizard.build/docs/getting-started) |
| Deploy Next.js, React, Vue, or a Python app | [Framework guides](https://lizard.build/docs/framework-guides) |
| Deploy from Claude Code or another coding agent | [Coding agent guide](https://lizard.build/docs/guides/deploy-from-coding-agent) |
| Host a remote MCP server | [Remote MCP guide](https://lizard.build/docs/guides/deploy-mcp-server) |
| Keep a Telegram bot running | [Telegram worker guide](https://lizard.build/docs/guides/telegram-bot) |
| Connect a database | [Managed Postgres](https://lizard.build/docs/addons/postgres) |
| Run generated code in a separate environment | [Sandboxes quickstart](https://lizard.build/docs/sandboxes/quickstart) |
| Keep files after a sandbox ends | [Persistent Volumes](https://lizard.build/docs/sandboxes/volumes) |

## Deploy an app

Install Lizard CLI and sign in, then deploy a repository you can access:

```bash
npm install -g @lizard-build/cli
lizard login
lizard add -r your-org/your-app
```

Lizard builds the image on its servers, so this path does not need local Docker. [lizardpack](https://lizard.build/docs/concepts/build-pipeline) detects supported projects; projects with special build needs can use explicit commands or a Dockerfile. Check the build logs and verify the application URL after deployment.

## Understand your resources

A **workspace** groups members and projects. A **project** groups services, databases, and Sandboxes. A **service** runs an application or worker. Managed Postgres, Managed Redis, and Managed Object Storage provide data services that applications connect to through environment references.

Apps and Sandboxes have different runtime and storage rules. Read [limits](https://lizard.build/docs/platform/limits) and [storage and recovery](https://lizard.build/docs/platform/storage-and-recovery) before depending on a resource's size, lifetime, or data retention.

## Find the right level of detail

- [Guides](https://lizard.build/docs/guides) cover a task from setup to a check of the result.
- [Framework guides](https://lizard.build/docs/framework-guides) give build commands, adapters, ports, and checks for each stack.
- [Core concepts](https://lizard.build/docs/concepts/architecture) explain projects, builds, and deployments.
- [Lizard CLI reference](https://lizard.build/docs/cli) lists commands, flags, and exit codes.
- [Troubleshooting](https://lizard.build/docs/deploy/troubleshooting/service-never-healthy) helps diagnose a failed start.
- [Known issues](https://lizard.build/docs/platform/known-issues) records limits and recovery cases to check before a release.