PulsePoint follows an evolving release line, from the production-ready v1 generation to the experimental v2 alpha. This page gives you a quick overview of the current channels, their stability, and where each version fits in the framework's lifecycle.
Similar to the release communication style used by mature runtimes, PulsePoint separates its versions by stability level rather than treating every release equally. This makes it easier to understand what is safe for production and what is still evolving in public.
The current recommendation is simple: use v1.0 for production work, and explore v2 only when you want to test the next generation of the framework and provide feedback.
PulsePoint Release Channels
Each release line communicates both maturity and expectation. Stable versions aim for predictable development and long-term reliability, while alpha versions signal that APIs, patterns, and internals are still being refined.
Recommended for production apps and long-term projects where consistency matters most.
Public early-stage work intended for exploration, testing, and community feedback.
This structure can grow naturally to include Beta, Maintenance, or End-of-Life phases later.
Below is the current release timeline for PulsePoint, presented in a clear version-by-version format.
Alpha
First released
In active development
Last updated
Ongoing
PulsePoint v2 is the next evolution of the framework, currently in alpha and actively being shaped.
New APIs and internal improvements are being explored
Breaking changes may happen while the architecture stabilizes
Best suited for experimentation and early feedback
Production Ready
First released
Available now
Last updated
Stable line
PulsePoint v1.0 is the stable production-ready release for building reactive HTML-first applications.
Tiny browser runtime with backend-agnostic architecture
Reactive state with pp.state, pp.effect, refs, loops, and portals
Ideal for production workloads and long-term apps
A concise comparison of the current PulsePoint release lines and what they are best used for.
| Version | Channel | Recommended Use | Risk Level |
|---|---|---|---|
| v2 | Alpha | Experimentation, testing, early feedback | High |
| v1.0 | Production Ready | Real-world applications and stable products | Low |
* As PulsePoint evolves, additional lifecycle states such as Beta, Maintenance, or End-of-Life can be added to this same timeline model.
If stability is the priority, choose the v1 line. It represents the mature and recommended path today.
The v2 alpha line is where the next ideas are validated before they are ready for broad adoption.
A dedicated timeline helps users quickly understand maturity, expectations, and upgrade confidence.
This page structure is ready for more releases later without needing to redesign the documentation.
If you are new to PulsePoint, start with the introduction and core concepts first, then come back to this timeline page when deciding which version line you want to build on.
Understand the mental model, the architecture, and how PulsePoint fits between server rendering and reactive UI.
Learn state, effects, refs, components, loops, portals, and the runtime primitives that define the framework.
Use this page to decide whether you need the proven stability of v1 or want to explore the evolving v2 alpha line.