Stability
What alpha means here.
Nextly is in alpha. This page says what that means, what has a stability promise and what doesn't, and what to do if you run it in production.
- Updated 26 Oct 2026
- Release 0.0.2-alpha.71
At a glance
- Release
0.0.2-alpha.71, published 25 Oct 2026- Before it
0.0.2-alpha.70, 25 Oct 2026;0.0.2-alpha.69, 24 Oct 2026- Needs
- Node.js 22.12+ or 24+ (Node 24 LTS recommended), Next.js 16 with the App Router, React 19
- Databases
- PostgreSQL 15 or later, MySQL 8 or later, SQLite 3.38 or later for local work
- Install
npx create-nextly-app@alpha my-app- Release notes
- GitHub releases
Packages
Versions and stability promises
| Topic | What is true today | Source |
|---|---|---|
| Versions | Every Nextly package is released together, at the same version. | Source [1] |
| Ledgers | Two packages keep a stability ledger that marks each export @public or @experimental: @nextlyhq/plugin-sdk and @nextlyhq/ui. | Source [2] Source [3] |
| Before 1.0 | The @public surface becomes semver-protected at 1.0; until then, and for every other package, pin exact versions. | Source [2] Source [3] |
| Plugin SDK | Alpha plugin SDK. The @public surface becomes semver-protected at 1.0; until then, pin exact versions. Plugin API stability | Source [2] |
Sources
Upgrading
Before you upgrade
Read the release notes
Most releases list steps to take before you upgrade; read them in the release notes.
Release notesMigrate before you deploy
Apply schema changes with
Production migrationsnextly migratein your build or CI, before the new code deploys.Pin versions
Pin exact versions in production.
Questions
Releases, security and data
Releases
Which release does this page describe?#
This page describes Nextly 0.0.2-alpha.71, the release this site runs. npm's alpha tag may point to a newer one; read its release notes for what changed.
In our test on Nextly 0.0.2-alpha.67, Claude Code and Codex each set up a working Nextly project from an empty folder, from a plain request and the public docs, with no Nextly knowledge loaded beforehand. Changelog
Is there a beta?#
There is no beta yet, and no date for one.
Security and data
How do I report a vulnerability?#
Report a vulnerability privately through GitHub, or by email to contact@nextlyhq.com.
We aim to acknowledge within 48 hours and to patch Critical issues within 7 days, High within 14 and Medium or Low within 30; these are best-effort targets, not a contract. Fixes land on the newest alpha; older alphas get none. Security policy