Sites built with Turbo
Browse 1 examples of production websites using Turbo. Analyze their full stack and hosting setup.
Turbo Origins & Philosophy
Turbo emerged from the ashes of Hotwire, Basecamp's 2020 attempt to kill the SPA tyranny that had engulfed web development. The philosophical shift was brutal and necessary: stop shipping megabytes of JavaScript to render what the server already knows. Turbo intercepts link clicks and form submissions, swaps HTML fragments over the wire, and maintains the illusion of a single-page app without the React tax. It's server-rendered defiance in an era where frontend frameworks convinced everyone they needed 800KB bundles to toggle a modal. The problem it solved wasn't technical complexity but economic waste: teams were burning cycles on API contracts, state synchronization, and hydration bugs when most apps were glorified CRUD wrapped in venture capital narratives.
Turbo Strategic Dominance
CTOs pick Turbo for hiring arbitrage and velocity compression. You don't need separate frontend and backend teams arguing over GraphQL schemas. A Rails or Django shop can ship interactive interfaces with server-side developers who actually understand the business logic, cutting coordination costs by 60%. The monolith economics are undeniable: one deployment pipeline, one language context, no CORS nightmares, no duplicate validation logic living in two repositories slowly drifting apart. For B2B SaaS with complex workflows and thin margins, this is the difference between a 12-person team and a 25-person team hitting the same revenue targets. The ecosystem weight comes from Rails' maturity; Turbo isn't fighting uphill against framework churn because it bets on HTTP doing exactly what it's done for 30 years.
Turbo Technical Strengths
Turbo obliterates time-to-interactive for content-heavy applications and crushes initial page load metrics because the server sends real HTML, not a loading spinner and a promise. It handles optimistic UI updates and morphing better than most developers can hand-roll, and the Streams feature lets you broadcast real-time updates without wrestling WebSocket state management across 47 browser tabs. Mobile performance is legitimately superior because you're not parsing and executing JavaScript for every interaction; you're swapping DOM, which browsers have optimized for two decades.
Turbo Architectural Friction
The ugly truth: Turbo is state-phobic and collapses under heavy client-side interactivity. Build a rich text editor, a collaborative canvas, or anything resembling Figma, and you'll be fighting the framework's server-round-trip assumptions at every keystroke. The morphing algorithm occasionally produces UI flicker that makes designers homicidal, especially with CSS transitions mid-flight. You inherit Rails' deployment coupling; scaling means scaling the monolith, and while that's fine until 10M ARR, it eventually forces architectural conversations that SPA advocates avoided by going distributed on day one. The community is smaller, the StackOverflow answers thinner, and convincing a venture-backed board that you don't need a dedicated React team requires political capital most CTOs don't have. Turbo is the right choice only if you're disciplined enough to stay in its lane.
