Roadmap
The roadmap below explains where PulseForge is headed next. It separates current hardening work, the next upgrade wave, and the larger v4 direction so release planning stays realistic and transparent.
Current Release Track: v3.4.x
This track focuses on hardening auth, deploy hygiene, public SEO, documentation quality, and dashboard reliability.
Eliminate recurring auth regression classes through worker-side token verification hardening.
Make public pages richer, indexable, and release-ready instead of placeholder-heavy.
Improve endpoint testing behavior with timeout-aware responses and cleaner UX messages.
Tighten release verification so build and typecheck failures surface earlier.
Next Upgrade: v3.5.0
The next minor release will turn operational cleanup into product leverage by improving observability, onboarding, and support quality.
Add a dedicated onboarding checklist for new users after first login.
Ship deeper endpoint diagnostics such as DNS, TLS, and HTTP phase timing.
Introduce richer alert channel management and incident acknowledgment flows.
Expand documentation with step-by-step Cloudflare, Firebase, and Razorpay deployment guides.
Major Platform Upgrade: v4.0.0
Version 4 is planned as a product maturity release that moves PulseForge from a strong monitoring tool to a more complete reliability workspace.
Unified setup wizard for auth, billing, projects, endpoints, and first successful monitor run.
Advanced SLO and service health views for teams managing multiple projects.
Role-aware organization spaces with cleaner permission boundaries.
Expanded audit history, release markers, and recovery tooling for production incidents.
Structured docs and policy center with stronger metadata on every public page.