First step towards downscaling for keeping the platform alive
Starting today, we are stopping all code changes to PulseWatch. No new features, no refactors, no experiments. The platform keeps running exactly as it is, and we are focusing our effort on keeping it alive for as long as possible.
This is the first step towards downscaling. PulseWatch runs on donations only, and the current level of support is not enough to sustain active development alongside hosting and operations. Downscaling is how we stretch the remaining resources as far as they can go.
What stays the same
The service itself does not change today. Monitors, alerts, status pages, probes and dashboards keep working as before. Existing accounts keep their data and their checks. We are not taking anything away; we are simply stopping the work that adds new things.
What changes
From now on, the roadmap is frozen. Security-critical fixes may still happen if something breaks, but feature work stops. The goal is to reduce costs and obligations so that the platform survives on the donations it already receives, instead of spending time and money we do not have.
If support recovers, we can revisit this decision. For now, this pause is the responsible first step.
The PulseWatch Team
💬 Comments
Questions, corrections or thoughts on this post? Join the thread below.