# Pushleft > Pushleft is a source-available deployment platform, free to self-host. Run `pl up` in a checkout and get an isolated HTTPS URL on your own servers, with builds, private networking, managed databases, logs, errors, mail, an AI proxy and teardown handled for you. The full manual as one file: https://pushleft.dev/llms-full.txt Agent skill to set up a deployment (installs pl, writes .pl.yaml, makes the Dockerfile non-root, sets secrets, deploys): https://pushleft.dev/skill.md (page: https://pushleft.dev/skill/) Deployment recipes (network diagrams with their .pl.yaml): https://pushleft.dev/recipes/ Prices: https://pushleft.dev/pricing/ (self-hosted €0; Cloud on your own servers €10/month; Cloud €10/month plus usage). ## Features - [Deployments](https://pushleft.dev/features/deployments/): Push a branch and get a live HTTPS address for it. You see every step in the console, from the build to the first request. - [Your own servers](https://pushleft.dev/features/own-servers/): Our cloud runs Pushleft, and your apps run on servers you own. Add a server with one command, and follow each step of the install in the console. - [Logs and metrics](https://pushleft.dev/features/logs-and-metrics/): Your services write to stdout and stderr, and the console shows every line. Each instance also gets charts for its CPU, memory and network. - [Errors and tracing](https://pushleft.dev/features/errors/): Keep the Sentry SDK you use today and change one setting. Pushleft groups your errors into issues and shows each stack trace in your own source code. - [Databases](https://pushleft.dev/features/databases/): Add PostgreSQL, ClickHouse or Valkey to .pl.yaml. Each environment gets its own database, your services get the credentials, and backups run every day. - [Domains and DNS](https://pushleft.dev/features/domains/): Search, buy and renew domains in the console. Pushleft hosts the DNS and issues the certificates, so a new domain serves your app within minutes. - [Mail](https://pushleft.dev/features/mail/): Send receipts, sign-in links and notifications from your own domain. Pushleft signs each message with DKIM and stops mail to addresses that bounce. - [AI proxy](https://pushleft.dev/features/ai/): Your apps call Anthropic, OpenAI, Gemini, OpenRouter, DeepSeek or your own Ollama through one proxy. You keep your provider keys, and each provider bills you directly. - [Usage and budgets](https://pushleft.dev/features/usage/): Pushleft counts compute, database storage, mail, AI tokens and error events every hour. Set a monthly budget to get alerts, or to stop new work when you reach it. - [Team and security](https://pushleft.dev/features/team/): Your team signs in with a code by email, a passkey or your single sign-on. Admins invite people, set their roles and see every change in the audit log. - [Fleet admin](https://pushleft.dev/features/fleet/): Operators get one desktop app for the whole fleet. It shows every server, what runs on it, the build queue and what needs attention first. ## Handbook - [Handbook](https://pushleft.dev/manual/handbook/): Start here. This page tells you what Pushleft is and how its parts fit together. It also tells you how to run it on a laptop and on servers, and how we… - [Pushleft](https://pushleft.dev/manual/readme/): Pushleft is a source-available deployment platform for small teams, free to self-host under the Functional Source License. You run pl up in a checkout and… - [Architecture](https://pushleft.dev/manual/architecture/): This page explains how Pushleft is built and which rules every change must keep. Read it before you change the control plane, the agent or the network. It… ## Operate - [Install the control plane](https://pushleft.dev/manual/deploy/): This page shows you how to install the Pushleft control plane on servers. It covers which hosts run which units, the ports, service users, database roles,… - [Your own servers](https://pushleft.dev/manual/own-servers/): Our cloud runs Pushleft, and your apps and databases run on servers you own. One command on a Debian or Ubuntu server installs the agent and adds the server… - [Fleet](https://pushleft.dev/manual/fleet/): Add hosts to the Pushleft fleet, keep their certificates current, update their agent and retire them. Developers never see these tools: operators run… - [Operations and alerts](https://pushleft.dev/manual/operations/): Watch the Pushleft control plane, answer its alerts and recover it after a failure. This page also lists the service level targets, the audit trail,… - [Authentication](https://pushleft.dev/manual/authentication/): Sign in to Pushleft from the CLI and the console, invite members and protect your organization. Pushleft has no passwords. You sign in with a single-use… - [Domains and DNS](https://pushleft.dev/manual/domain-registration/): Buy a domain in the Pushleft console, and Pushleft registers it and hosts its DNS for you. You then manage its DNS records on the same page and serve the… - [Usage and budgets](https://pushleft.dev/manual/billing/): Pushleft measures what your organization uses each hour and prices it in EUR with your organization's plan. Each month closes into a statement. Set a… - [Scheduled jobs](https://pushleft.dev/manual/scheduled-jobs/): A scheduled job runs a script from your repository on a schedule, in a throwaway VM that can run Docker. Pushleft sends mail when the script fails. A run… - [Abuse controls](https://pushleft.dev/manual/abuse/): This page lists the limits of each trust tier and the events that pause mail or suspend an organization. Operators use it to review abuse reports and to… - [AI provider proxy](https://pushleft.dev/manual/ai-proxy/): The Pushleft AI proxy lets your applications call large language models with your organization's own provider keys. The application holds only a Pushleft… - [Customer mail](https://pushleft.dev/manual/mail/): Your applications on Pushleft can send transactional mail, such as receipts, sign-in links and notifications, from your own domains. Pushleft creates the… - [Errors and performance](https://pushleft.dev/manual/errors/): Pushleft collects the errors and request timings of your applications through any Sentry SDK. The console groups errors into issues with stack traces, and… - [Logs and metrics](https://pushleft.dev/manual/logs/): Pushleft collects what your web, private and worker instances write to stdout and stderr. It also records their CPU, memory and network use. You see the… - [Retention](https://pushleft.dev/manual/retention/): Choose how long Pushleft keeps your releases, sources and deployment events, and when it tears down idle previews. Retention never releases a deployment… - [Object storage](https://pushleft.dev/manual/storage/): This page shows how you give an environment its own private S3 bucket. Each bucket has an access key that works on that bucket only. Any S3 client works… - [Container registry](https://pushleft.dev/manual/registry/): Pushleft includes a private container registry for each organization. Push your own images from a laptop or CI, pull public images through a cache, and… - [Git server](https://pushleft.dev/manual/git/): Pushleft hosts private git repositories for your code and deploys every push. Push the production branch to update production, and push any other branch to… ## Develop - [The .pl.yaml manifest](https://pushleft.dev/manual/manifest/): This page shows you how to describe your app to Pushleft in a .pl.yaml file: its roles, databases, secrets and routes. Put the file at the root of your… - [Onboard with an AI agent](https://pushleft.dev/manual/onboarding-skill/): This page shows you how to let an AI coding agent set up a Pushleft deployment. The Pushleft skill installs pl, reads your checkout, writes .pl.yaml, makes… - [The pl up demo](https://pushleft.dev/manual/pl-up-demo/): This page shows how to run the full pl up journey on your own machine, and what that run proves. npm run test:pl-up-demo (scripts/pl-up-demo-e2e.sh, also in… - [Build executor](https://pushleft.dev/manual/build-executor/): A build_image job turns one verified source snapshot into one pushed OCI image. It publishes that image's digest through the lease-fenced… - [Source ingestion](https://pushleft.dev/manual/source-ingestion/): pl up packages your local checkout and uploads it to Pushleft before the build starts. This page shows what the CLI sends and which files it leaves out. It… - [Agent gateway](https://pushleft.dev/manual/agent-gateway/): The agent gateway is how fleet nodes get work from the control plane. This page explains how a node proves its identity, leases jobs, receives secrets and… - [Managed databases](https://pushleft.dev/manual/managed-databases/): Pushleft runs PostgreSQL, ClickHouse and Valkey for each environment of your project. You declare the databases in .pl.yaml, and every role that lists one… - [Security findings](https://pushleft.dev/manual/security-findings/): Pushleft scans every build and the live source of each project once a day. This page shows what mail you get and how to mute a finding. - [Tunnels and shells](https://pushleft.dev/manual/developer-access/): Three commands and a console terminal give your machine access to one environment's private services. Your machine does not join the environment network,… - [Dev workspaces](https://pushleft.dev/manual/dev-workspaces/): A dev workspace is a private Linux VM for one person. It has root and sudo, a persistent disk and a private network. Rust, C and C++, ESP-IDF, Arduino,… - [Private hostnames](https://pushleft.dev/manual/private-hostnames/): Built and passing on staging (2026-11-01, staging.sh names). Decided the same day: the agent answers the names, and containers take the new DNS setting at… - [Mesh coordinators](https://pushleft.dev/manual/mesh-coordinators/): Each deployment environment gets its own private network (a tailnet), run by its own Headscale coordinator. This page shows how pushleft-mesh runs those… - [Design baseline](https://pushleft.dev/manual/design-baseline/): This page gives the design rules for the developer console and the public site. Use it when you build or change a screen, so that new work matches the… ## Runbooks - [Control-plane host failover](https://pushleft.dev/manual/runbooks/control-plane-host-failover/): Use this runbook when the host that runs the control-plane services is lost and service_not_ready fires for every service. - [Control-plane PostgreSQL failover](https://pushleft.dev/manual/runbooks/control-plane-postgres-failover/): Use this runbook when the control-plane database primary is lost: service_not_ready fires for every service, or control_plane_replication_lag pages. - [Control-plane PostgreSQL restore](https://pushleft.dev/manual/runbooks/control-plane-postgres-restore/): Use this runbook when the control-plane database on box 2 is lost, or when bad data reached it (a wrong migration, an operator UPDATE). - [Custom domains and certificates](https://pushleft.dev/manual/runbooks/custom-domain-verification/): Use this when a tenant's custom domain stays pending_verification, turns failed, or is verified but not served. It also covers the alerts… - [Gateway key compromise](https://pushleft.dev/manual/runbooks/gateway-ca-compromise/): Use this when one of the agent gateway keys may have leaked. For example, failed_auth_burst fires, unknown certificates appear, or a gateway host or node is… - [Ingress host failure](https://pushleft.dev/manual/runbooks/ingress-host-failure/): Use this when public hostnames stop answering while /readyz is green, or when ingress_publication_stuck or ingress_route_failed fires. - [Node busy](https://pushleft.dev/manual/runbooks/node-capacity-high/): Use this when node_cpu_busy or node_memory_high fires. A node of ours used 90% or more of its CPU, or of its memory, in each of the last 5 minutes. Requests… - [Node disk full](https://pushleft.dev/manual/runbooks/node-disk-full/): Use this when node_data_disk_low, node_disk_high, node_disk_full, host_disk_high or host_disk_full fires. A filesystem is over 80% full, or the data disk… - [Node drain and replacement](https://pushleft.dev/manual/runbooks/node-drain-and-replacement/): Use this for planned maintenance, a provider host alert, or when node_heartbeat_stale or node_data_disk_low fires. - [Node lost](https://pushleft.dev/manual/runbooks/node-lost/): Use this when node_heartbeat_stale fires and pushleft-controller fleet list then shows a node as lost. - [Registry outage](https://pushleft.dev/manual/runbooks/registry-outage/): Use this when builds fail with push errors, or when build_failures_infrastructure, build_duration_slow or registry_image_release_failing fires. - [Hetzner Robot hosts](https://pushleft.dev/manual/runbooks/robot-hosts/): Use this runbook to add a Hetzner Robot (dedicated) server to the fleet. - [Secret rotation](https://pushleft.dev/manual/runbooks/secret-rotation/): Use this runbook when a secret leaks, when a person with access leaves, or when you rotate on a schedule. - [Security incident](https://pushleft.dev/manual/runbooks/security-incident/): Use this checklist for a suspected credential leak, tenant data exposure, a compromised node or control-plane host, or abuse. The alerts failed_auth_burst… - [Staging fleet on Proxmox](https://pushleft.dev/manual/runbooks/staging/): Use this runbook to test a change on the staging fleet before you ship it. Run it for changes to the agent, the units, deploy/postgres or the node bootstrap… - [Staging build cache](https://pushleft.dev/manual/runbooks/staging-build-cache/): Use this runbook to turn on, check or roll back the build cache on the staging fleet. - [Stuck deployment](https://pushleft.dev/manual/runbooks/stuck-deployment/): Use this runbook when a deployment stays queued, building or deploying and its event trail stops. The alert deployment_stuck fires after 30 minutes. - [Vault/OpenBao backup and recovery](https://pushleft.dev/manual/runbooks/vault-recovery/): Use this runbook to set up Vault snapshots, to answer the vault_snapshot_stale alert, or to restore Vault after its host or data is lost.