TeamRetro is an agile collaboration platform that powers team retrospectives, health checks, and planning poker estimation. Teams use it to reflect on sprints, identify improvements, and estimate work collaboratively – all in realtime with tens to hundreds of concurrent participants.
When a team member adds feedback, votes on an action item, or reveals their estimation card, everyone else needs to see it instantly. High-performance, reliable realtime infrastructure isn't a feature: it's the foundation of the entire experience.
"Our team's primary focus is enabling rich, fluid, and engaging online meeting experiences," explains Brad Ward, Co-founder and CTO of GroupMap Technology. "As a product SaaS company, our focus is on developing compelling meeting experiences – our ideal is to rely on trustworthy partners to provide the backbone to those experiences."
TeamRetro had been using Pusher, but mounting concerns prompted a reevaluation. After MessageBird's acquisition, they told us three issues emerged
1. Product stagnation
Pusher's direction became unclear, with limited innovation beyond core Channels. For a company building sophisticated collaborative features, this misalignment was problematic.
2. Security uncertainty
SOC2 reports were unavailable and security documentation was sparse. "It was important that the partners we work with have the same level of security robustness, care and reliability that we do," Brad explains
3. Limited flexibility
Beyond basic pub/sub, Pusher offered little for building advanced collaboration features like presence management, synchronised state, and regional compliance.
Evaluating alternatives
When it came to looking at alternatives, TeamRetro considered several options:
AWS API Gateway offered maximum flexibility but would require building message fan-out, subscription management, and all infrastructure logic from scratch. "This is a core building block, but is not our unique value proposition," Brad notes.
AWS AppSync provided more out-of-the-box functionality but introduced new authentication patterns, infrastructure paradigms, and data patterns that would require significant rework.
Ably addressed all three concerns without new risks:
Product alignment: Roadmap focused on collaborative editing, presence, locking, and synchronization. Direct conversations with Ably's product team gave them confidence their paths aligned
Clear security posture: SOC2 Type 2 accredited, AWS infrastructure, comprehensive public documentation
Flexibility: Region-locking, message deduplication, batching, and plugins like LiveObjects for rapid prototyping
"We've had several meetings with Ably product and developer teams who have been genuinely interested in our specific needs and feedback, giving us confidence our paths are aligned," Brad recalls.




