Start with a working API.
Fastify, TypeScript, Prisma 6, PostgreSQL, JWT authentication, Zod validation, OpenAPI documentation, health checks, Docker and CI form the generated baseline.
RELEASED V3.0.6
Generate a Fastify, TypeScript, Prisma and PostgreSQL API—then manage project state, add capabilities, reconcile changes, generate typed clients and run isolated development or preview environments. LaunchStack is tooling for the work after scaffolding, not just the first command.
LaunchStack started with deployment and configuration tools in v1, grew into a production-minded API generator in v2, and introduced declarative lifecycle management in v3. Fresh projects include launchstack.json for desired state and .launchstack/state.json for the tool’s managed files, installed capabilities and stage metadata. Your business logic stays yours.
Fastify, TypeScript, Prisma 6, PostgreSQL, JWT authentication, Zod validation, OpenAPI documentation, health checks, Docker and CI form the generated baseline.
Plan, diff, reconcile and upgrade against managed hashes. Read-only plans expose drift before durable, journaled mutations and project-lock-protected writes.
Add Redis, BullMQ queues, cron and other capability helpers. Dependencies, generated files and Compose fragments are assembled with explicit coverage and safe removal rules.
Development orchestration allocates loopback ports, orders services, waits for readiness, limits migrations to safe local targets and cleans up its own Compose project.
Generate modules, owner-scoped resources and typed TypeScript, React or React Native clients from bounded OpenAPI 3.0 and 3.1 input.
Run bounded security audits, manage local preview stages and use deploy, status, history, rollback, secrets, Docker and GitHub workflow commands.
Provider-backed OAuth, storage, observability, WebSocket, email and webhook capabilities are helpers rather than complete third-party integrations. Docker Compose is the complete v3 preview lifecycle adapter; other adapters report unsupported operations.
Node.js 24.22.3+ on the 24 line or 26.13.1+ on the 26 line is required. Node 20 is not supported. Generated workflows use PostgreSQL or Docker.
Released v3.0.6: LaunchStack CLI is available as an open-source release. Install version 3.0.6 with npm and use the documented lifecycle commands to generate and manage backend projects.
npm install --global launchstack-cli@3.0.6launchstack --versionlaunchstack plan --jsonlaunchstack reconcilelaunchstack status --stage preview-demo --jsonReported measurements are from the v3.0.4 release benchmark suite and are workload- and host-specific. v3.0.0 is the comparison baseline where specified. These results are not a universal speedup claim.
| Workload | Measured result | Context |
|---|---|---|
| CLI startup | --version: 5.7% slower; --help: 1.4% faster | Warm p50 compared with v3.0.0; no consistent startup speedup |
| Audit & security | 100,000 paths: 111.1 ms p50 / 141.7 ms p95 | 1,290 bounded hostile-input corpus cases passed |
| Durable mutations | 10,000 files: 6.27 s p50 versus 1.98 s | Slower than v3.0.0; 8- and 32-writer tests lost no updates |
| Upgrade planning | 10,000 files: 82.1 ms p50 versus 46.9 ms | v3.0.0 baseline; additional validation and lifecycle checks |
| Capability graphs | 10,000 nodes / 99,945 edges: 9.19 ms p50 | Ten BullMQ jobs: 2.00 ms p50 / 6.65 ms p95 |
| Local orchestration | Two projects ready: 19.96 s | Two warm preview stages: 68.28 s |
| Generated resources | Two owner-scoped UPDATE queries, no pre-read | Each keyset page uses one bounded SELECT |
| Complexity | Scheduling O((V+E) log V) | Extension order O(V+E); streaming hash O(B) with bounded buffer |
| Release qualification | 250,000-file drift scan: 36.41 s versus 2.53 s | 14.41× slower than v3.0.0 on the measured host |
The release hardens managed paths, secret files, recovery journals and locks; validates remote OpenAPI DNS answers; bounds audit and SDK inputs; and improves safe concurrent capability updates and explicit template migrations.
Generated APIs use database-enforced single-use refresh token rotation and owner-scoped queries. Release qualification includes Windows portability, CodeQL, validated SBOMs, PostgreSQL integration checks and Docker health/readiness tests.
Production rate limiting defaults to an in-memory store per process; multi-replica services need a shared store. Prisma 7 migration is deferred. The CLI does not promise security against a separate same-user process concurrently swapping project parent directories.
v3.0.5 maintenance fix: project mutations use atomic directory locks with stale-owner recovery; validation accepts v3 manifests and legacy configuration; create --directory creates the named project inside the selected parent and supports progress reporting. Node.js 24/26 guidance is clarified. Hotfix details.
Released v3.0.6 maintenance fixes: concurrent capability installs no longer silently overwrite earlier state or orphan generated files; the production audit recognizes Compose-inherited CORS/JWT settings (LS021) and distinguishes non-Git folders from genuine enumeration failures (LS022). Unsupported Node versions receive clearer CLI guidance, and generated production builds document custom-CA configuration through a BuildKit secret without committing certificate material. v3.0.6 fix details.
Yes. It is maintained by Zivora Labs and published under the MIT license, with source available on GitHub.
LaunchStack CLI v3.0.6 is released. Install it with npm install --global launchstack-cli@3.0.6, then run launchstack --version to verify the installation.
No. Declarative state tracks LaunchStack-managed files and capabilities. It reports drift and preserves user-owned business and domain code.
Node.js 20 is no longer supported in v3.0.6. Generated projects remain on Prisma 6; Prisma 7 needs a separately tested migration.
Explore the launch, learn about drift-safe backend scaffolding and join the conversation around LaunchStack CLI.
Explore the launchAlso from Zivora Labs: Toolip, a local-first developer security CLI.