Sugar Calendar
Events can finally ask attendees a question at the moment they sign up.
A side-by-side editorial comparison of Blue and NocoBase — release velocity, themes, recent moves, and the top alternatives to consider.
Blue's feed is capturing a Cloudflare timeout page instead of a changelog
There is no product content here. Both captured rows are fragments of a Cloudflare error interstitial — a 'What happened?' block reporting that the connection between Cloudflare's network and the origin web server timed out, and a 'What can I do?' block advising a retry. Neither has a date or a source URL. The crawl reached the CDN and never reached Blue.
Both NocoBase branches spend the same day on the same workflow fixes.
Development stays split across a 2.3 beta line and a 3.0 alpha line, and both spent 31 August on the same workflow rollup: a composite index on job status and ID for pending-job recovery, a fix for schedule workflows running once more after endsOn, and a mobile pass giving workflow task detail a full-width drawer and a responsive task centre. The 3.0 alpha adds what the maintenance branch does not take, including client-v2 association field rendering, duplicate submit actions in public forms, GigaChat startup on iOS 15.6 and earlier, and a knowledge-base access check that wrongly told AI employees they had no access for root users. Neither release carries a feature section.
There is no product content here. Both captured rows are fragments of a Cloudflare error interstitial — a 'What happened?' block reporting that the connection between Cloudflare's network and the origin web server timed out, and a 'What can I do?' block advising a retry. Neither has a date or a source URL. The crawl reached the CDN and never reached Blue.
Nothing about the product can be read from an error page. The only conclusion supported is operational: whatever URL is configured for this product was returning a 522-class timeout at capture time, so either the origin was down or the configured endpoint is wrong.
Unclear, and not answerable until the source is fixed. The next crawl will either return real entries if the origin recovers, or the same interstitial if the endpoint itself is misconfigured.
Development stays split across a 2.3 beta line and a 3.0 alpha line, and both spent 31 August on the same workflow rollup: a composite index on job status and ID for pending-job recovery, a fix for schedule workflows running once more after endsOn, and a mobile pass giving workflow task detail a full-width drawer and a responsive task centre. The 3.0 alpha adds what the maintenance branch does not take, including client-v2 association field rendering, duplicate submit actions in public forms, GigaChat startup on iOS 15.6 and earlier, and a knowledge-base access check that wrongly told AI employees they had no access for root users. Neither release carries a feature section.
The two branches now ship within hours of each other with overlapping content, which makes 2.3 less a frozen maintenance line than a trailing mirror of the alpha. Workflow is absorbing most of the attention this cycle: approvals, scheduling, notification recipients and job recovery all moved together, and the repeated variable parsing failed fixes point at one shared user-selector defect being pulled out rather than patched per node. The AI employee, multi-space and knowledge-base work stays exclusive to 3.0, so the branches keep diverging on capability while converging on fixes.
Expect 2.3 to keep taking the workflow and approval fixes within hours of each alpha while the AI employee surfaces stay 3.0-only. The mobile drawer and narrow-viewport work landing on both branches suggests the next alpha continues the responsive pass into the remaining workflow and approval configuration screens.
Other PM products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Blue or NocoBase.
Events can finally ask attendees a question at the moment they sign up.
Hive is building the plumbing its Buzz AI snippets need to run on real team data
Notesnook ships fast across three platforms and points every release note at its blog
Celoxis publishes buyer-guide content on a schedule; its releases are elsewhere
Teamhood's feed is a competitor-comparison engine, not a changelog
Process Street's feed is a content engine, and its releases are not in it
See all Blue alternatives → · See all NocoBase alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NocoBase is currently shipping more aggressively (velocity 7.5 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NocoBase is currently shipping more aggressively (velocity 7.5 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Blue alternatives in PM are ranked by recent ship velocity. Browse the "Blue alternatives" section above for the current picks, or visit /alternatives/blue for the full list with editorial commentary on each.
Top NocoBase alternatives in PM are ranked by recent ship velocity. Browse the "NocoBase alternatives" section above for the current picks, or visit /alternatives/nocobase for the full list with editorial commentary on each.