← Back to home
Comparison · Comms

Session vs Front

Side-by-side trajectory, velocity, and editorial themes.

S
Session
COMMS
0.0

Session shipped a protocol rewrite and a paid tier, then went publicly broke — the founder is asking users to bail it out.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Front logo
Front
SUPPORTCOLLAB
6.3

Front is doubling down on AI as the primary surface, not a side feature.

◆ Current state

The release stream is dense with AI work: knowledge-source connectors (Guru, Confluence) feeding Copilot and Autopilot, fact invalidation controls so admins can curate what AI cites, AI Translate landing across SMS/WhatsApp/Messenger/Chat, and new agent-runtime integrations like One that bridge Front to thousands of external tools. Non-AI work (Salesforce/Asana templates, Zoom Contact Center, analytics) is still landing but plays second fiddle to the AI cadence.

◆ Where it's heading

Front is positioning as an AI-native customer comms hub rather than a shared-inbox tool with AI bolted on. The pattern — grounding AI in private knowledge, exposing admin governance over what AI says, broadening channel coverage — is the playbook for moving AI from gimmick to production-trusted. The integration push (Zoom CC, One, omnichannel surfaces) suggests Front wants to be the operator console for AI-mediated support, not just one of many inboxes.

◆ Prediction

Expect the next directional move to be deeper Autopilot autonomy — measurable AI-resolved ticket metrics, escalation rules tied to confidence, or AI-led drafting that promotes itself to send-without-review under specific governance gates. The fact-invalidation feature is a precondition for that.

See more alternatives to Session
See more alternatives to Front