Session vs Chat Data
Side-by-side trajectory, velocity, and editorial themes.
Session shipped a protocol rewrite and a paid tier, then went publicly broke — the founder is asking users to bail it out.
Session is simultaneously in its most ambitious technical phase and an open funding crisis. Protocol V2 — re-implementing forward secrecy and layering post-quantum cryptography on top of Session's onion-routed transport — has been announced, and the Session Pro paid tier exited beta planning into a December development update. Then in March, cofounder Chris McCabe published a personal appeal saying the project cannot continue developing without user support, and the public feed has been quiet since.
The product roadmap that was meant to fund itself via Session Pro is colliding with the underlying problem the appeal makes plain: the Loki/Oxen-era token economics and donations aren't covering ongoing development. Protocol V2 and Pro are the bets that have to land for Session to remain viable; if Pro doesn't convert a meaningful share of the user base, the next twelve months are about scope reduction, not feature growth. The Feb 1 APT key rotation in January suggests the core infrastructure is still being maintained — for now.
Watch for either a hard Session Pro launch and conversion announcement, or a more explicit wind-down / handoff post. A long stretch of silence after a funding appeal usually resolves one way or the other within a quarter; the absence of any new posts since mid-March is itself a signal.
Chat Data is turning its chatbot platform into a workflow runtime with payments built in.
Chat Data is no longer just a custom-chatbot builder — recent shipments push it toward an end-to-end agent platform. The last two weeks added cron-driven workflow triggers, native Stripe OAuth, deeper page-context tiers, and access to GPT-5.5. Each move targets a different gap that previously forced customers to bolt on outside tooling.
The arc is unmistakable: chatbot to agent to autonomous workflow with monetization wired in. Scheduling decouples Chat Data's automations from live user prompts; direct Stripe handles the revenue side; richer page context closes the gap with retrieval-heavy competitors. Pricing is shifting in lockstep, with a per-node credit charge for non-AI workflow steps replacing the prior all-or-nothing model.
Expect the next releases to focus on workflow observability — run history, retries, conditional branches — and likely an agent marketplace or template gallery to drive adoption of the scheduled-trigger surface.
See more alternatives to Session →
See more alternatives to Chat Data →