Flicker runs your apps and their Postgres in one place. A project is the umbrella that owns your databases and apps together; when an app and a database live in the same project, Flicker wires the connection between them for you. Push your source as one rolling Deployment, readiness-gated when the app is enrolled — on real Postgres you can branch in seconds, with per-project environments and governed secrets driving every deploy. One CLI and a REST API drive all of it.
These docs cover the developer surface end to end. New here? Start with Getting started — it walks the project-first flow from an empty directory to a live app — and work down.
Getting started
Log in, scaffold an app, deploy it, and watch it go live.
Environments & secrets
The secrets model: environments, inheritance, managed vs user secrets, bundles.
Deploys
Push → Building → running, deploy history, and rollback.
Wiring dependencies
Dependency edges, auto-rewire, and one-click templated connection keys.
Volumes
Persistent storage that survives deploys and restarts.
Transactional email: verify a sending domain, send via the API, and watch the message log.
Tickets
AI-native work units: the v1 workflow, versioned documents, local checkout, and searchable memory.
Agents & automation
First-party skills for Claude Code, Pi, and Codex that run the plan → ship workflow on Flicker Tickets.
Assistant & RAG
A project-scoped assistant grounded in your own data — buckets, git repos, and tickets — with hybrid retrieval.
Platform health
Cached functional status for Flicker's six platform components.
CLI reference
Every command, flag, and example — mirrored from the CLI's own help.