Episode Summary
Executive Summary: Irina Nazarova explains how AnyCable evolved from an open-source, drop-in Rails Action Cable replacement into a resilient real-time infrastructure product with its own protocol, commercial licenses, and broader ambitions. The conversation covers product strategy, community-led growth, hiring, scalability, roadmap prioritization, and how AI agents may change developer tooling adoption.
Main Topics: AnyCable’s origin as an open-source Rails replacement (Priority: 5/5): AnyCable began as an MIT-licensed open-source, drop-in replacement for Rails Action Cable, designed so customers could adopt it by changing configuration rather than application code. Evolving from drop-in replacement to own protocol (Priority: 5/5): As customer needs expanded, the team extended the protocol and built client/server components beyond the original compatibility layer to support more advanced use cases. Community-led product development and roadmap (Priority: 4/5): Roadmap decisions were driven by conversations with Ruby/Rails users, customer case studies, blog posts, and demand signals from real production use rather than hobby use cases. Business model and commercial licensing (Priority: 4/5): The company monetizes via AnyCable Pro licenses for clustered, larger-scale deployments, while keeping the core open source and offering a free SaaS trial version. Team culture and hiring philosophy (Priority: 4/5): Irina emphasizes self-organized, proactive, humble people who think deeply about technology, value others' perspectives, and fit the team socially and professionally. Scalability, self-service, and feature focus (Priority: 4/5): The team delayed self-service too long but later built it quickly in Rails; now they prioritize features based on market signals and avoid overinvesting in low-priority integrations. AI agents and the future of developer tooling (Priority: 5/5): Irina believes the next frontier is improving the agent experience so AI tools can more easily understand and use complex developer libraries and frameworks.
Key Arguments: Open source is the default best approach for developer tooling because it lowers adoption friction and fits community-driven products. A drop-in replacement strategy reduces switching costs by letting users adopt via config changes instead of code rewrites. Product direction should come from real customer pain, not abstract ideas; strong use cases and paying customers should influence prioritization. Roadmaps should be guided by which customer cohorts the company wants to attract, not just by feature requests. Commercializing advanced cluster-mode capabilities is a good fit for infrastructure software, even when the core remains open source. Hiring should prioritize proactive, humble, deeply technical people who can collaborate across perspectives. The technical/non-technical founder divide is a mistake for developer products; everyone involved should understand the product technically. AI agents will increasingly become the “users” of developer tools, so products need better agent experience and clearer guidance. Long-term success comes from building genuine relationships with the audience, not chasing overnight growth or hype.
Data Points: First production deployment: 2018 - Irina says AnyCable’s first production deployment was around 2018. Evil Martians team size: 52 people - Irina mentions Evil Martians has 52 people, with SREs, backend, frontend, and others supporting AnyCable from time to time. Time to build self-service checkout funnel: a couple weeks - The self-service funnel for permissions, teams, and billing was built in a couple of weeks after years of postponement. Years at Evil Martians: 9 years - Irina says she has been with Evil Martians for nine years. Company age: 20 years - She notes Evil Martians has existed for 20 years. Customer reach example: 80% of doctors in the United States - She cites Doximity as a large AnyCable customer serving roughly 80% of U.S. doctors.
Pivotal Quotes: "I think if you're building tooling for developers, just going with open source is a very good option." — Irina Nazarova: She describes the product philosophy behind AnyCable’s initial launch and adoption strategy. "My advice is to find the people that you are passionate to build for. I call them your audience." — Irina Nazarova: Her closing advice to entrepreneurs focuses on audience love and long-term relationship building. "Everybody has to be technical, regardless if you are, I see, kind of like a CEO, CTO, or whatever, it doesn't matter." — Irina Nazarova: She reflects on a mistake she made by over-separating technical and non-technical founder roles.
Implications: The episode suggests developer tools win by minimizing adoption friction, listening closely to real users, and staying flexible as markets shift. AI may make complex infrastructure more accessible, but teams still need strong technical judgment, community trust, and tight product focus.
About Code Story
Code Story is a podcast featuring startup founders, tech leaders, CTO's, CEO's, and software architects, reflecting on their human story in creating world changing innovation, disruptive digital products. Their tech. Their products. Their stories.