--- title: What the First TYPO3 Summit North America Says About Enterprise CMS url: "https://b13.com/blog/atlanta-typo3-summit-north-america-enterprise-cms" description: "A field report from Atlanta: predictable releases, non-extractable governance, the FAIR project, and a North American market where the bottleneck is awareness, not technology." date: 2026-05-21 modified: 2026-05-26 lastUpdated: 2026-05-26 --- # What the First TYPO3 Summit North America Says About Enterprise CMS ![Presentation screen displaying "TYPO3 Summit North America" with a blue aquatic background and a podium in front.](https://b13.com/fileadmin/_processed_/6/3/csm_cms-summit-na-0_df7ed73fa4.webp)On 19 May 2026, the first-ever TYPO3 Summit North America took place at the Georgia Aquarium in Atlanta. One day, one room, a tightly curated lineup. For an open source project that has quietly powered enterprise digital infrastructure in Europe for two decades, this was a statement. Not “we’re launching in the U.S.”—TYPO3 has been around there for years—but “we’re getting serious about a market where awareness is the bottleneck, not technology.” I spent the day there, and I want to share what stuck. Not a session-by-session recap—the schedule is online for that. What I want to put on paper is the underlying message that ran through the whole program, because it lines up almost exactly with how we think about building software at b13: pick the long road, not the shiny one. From Platforms to Ecosystems ---------------------------- **Karim Marucchi (Crowd Favorite)** opened with the framing that set the tone for the day: stop thinking in platforms, start thinking in ecosystems. The CMS market has spent fifteen years building monoliths, then ten years selling people on headless and DXP suites that often just relocate the lock-in. Meanwhile, enterprises have been quietly accumulating data debt, integration debt, and migration debt. ![A speaker in a red blazer presents at the TYPO3 North America Summit, discussing governance and community engagement. Text on the screen highlights key points about industry patterns and TYPO3's governance.](https://b13.com/fileadmin/_processed_/5/9/csm_cms-summit-na-1_3d03b3193b.webp) Karim Marucchi (Crowd Favorite) at his opening talk at the TYPO3 North America Summit My colleague **Benni Mack** followed up with TYPO3’s answer to that: an architecture engineered for the kind of complexity enterprises actually carry. Multi-site, multilingual (including RTL), granular per-element permissions, audit trails, content scheduling at the element level, a relational data model that holds up at scale. None of this is new in TYPO3. That’s the point. It’s been hardened for years, and now there’s a coherent story to wrap around it: ECM, not just CMS. Content as a long-term asset, content design (structure, metadata, governance) as the architecture that makes it findable and compliant, visual presentation as the disposable layer on top. That separation is what makes redesigns cheap and content durable. It’s also what makes TYPO3 “AI-ready” in the only way that actually matters—not because there’s a magical AI feature in the core (there isn’t, and Benni was clear that’s deliberate), but because the data underneath is structured enough that you can feed it to whatever model you want without first untangling it. The Suite, the Association, and the Long Game --------------------------------------------- Jeffrey A. ‘jam’ McGuire walked through the governance keynote that **carried the most weight of the day.** The TYPO3 Association plus the TYPO3 Company (legally TYPO3 GmbH), with the Company owned 100% by the Association, is a quiet but unusual setup in open source. It can’t be acquired. It can’t pivot to a closed source model under pressure from investors. Roles are clearly delineated, and non-competition with the agency ecosystem is baked in. On top of that sits the release cadence: 18 months between major versions, three years of community LTS, and up to four more years of Extended LTS for organizations that want to stay on a version longer. Up to seven years of support, planned and predictable. For an enterprise that has to budget upgrades against a five-year IT roadmap, that predictability is worth more than any feature checklist. The TYPO3 Suite—GPL-licensed, subscription-funded—is the piece that ties this together commercially. Features get vetted in Suite, generate revenue that funds forward innovation, and flow into core in subsequent releases. In Europe, the Suite also takes on “manufacturer” liability under the Cyber Resilience Act for approved configurations, which is a real differentiator as the CRA, the EU AI Act, and the Accessibility Act all start to bite. The phrase Jam used was “a third way”—not extractive open core, not VC-funded SaaS, just a sustainable commons with a present-tense revenue stream. This is the part that resonates with how we operate at b13. We don’t sell the quick fix; we sell the thing that still runs in six years without a migration project. And the reason this matters more than another vendor roadmap pitch is that it isn’t one: the cadence, the LTS commitments, the Association-owned governance—that has been TYPO3’s actual operating model for years, with release dates hit and support commitments honored release after release. A platform whose governance is structurally aligned with that timeline is not a coincidence we can ignore. Real Projects, Real Work ------------------------ **Three case studies** anchored the morning, and they’re worth naming because they show what mature TYPO3 actually does in production. **Viviane Gebelein** presented toujou, the TYPO3-based website builder from DFAU, with the Rotkäppchen-Mumm rollout as the headline case: forty brand websites, mixing new builds, relaunches, and migrations, delivered over two and a half years from a single platform. The interesting part isn’t the count. It’s that the standardization didn’t kill brand individuality, and the platform kept getting cheaper to maintain as each new brand came on board. That’s the composability story made concrete. **Kai Unterberg’s** “Great Content Rescue” walked through a legacy migration on the order of tens of thousands of fragmented content elements across three languages, restructured into clean TYPO3 content blocks through pattern-based automation. This is the unglamorous work that decides whether a relaunch ships on time or turns into a two-year content cleanup. Done right, it’s repeatable. Done wrong, it eats the project. **Fabian Stein** (punkt.de) closed the morning block with a modular ECM system built on top of TYPO3, focused on what he called “content observability”—knowing what content you have, where it lives, who edits it, and whether it still belongs. At enterprise scale, content chaos is a security and compliance problem, not just an editorial one. Tools that surface it are increasingly necessary. FAIR: A Distribution Layer Worth Watching ----------------------------------------- **Brent Toderash** and **Karim Marucchi** presented **FAIR** (Federated and Independent Repositories), a Linux Foundation project that started in the WordPress ecosystem and has now pivoted toward TYPO3 as its anchor partner. The idea is straightforward: a federated, decentralized way to distribute and verify software packages, so enterprises can run private mirrors of approved extensions and updates instead of trusting a single central repository. ![Two men sit on stage during a discussion, one in a red blazer holding a microphone, the other in casual attire gesturing while speaking.](https://b13.com/fileadmin/_processed_/1/8/csm_cms-summit-na-2_be2a86bd75.webp) Brent Toderash and Karim Marucchi discussing the FAIR project ![Two men sit on stage during a discussion, one in a red blazer holding a microphone, the other in casual attire gesturing while speaking.](https://b13.com/fileadmin/_processed_/1/8/csm_cms-summit-na-2_e7f23c903b.webp) Brent Toderash and Karim Marucchi discussing the FAIR project If you’ve ever had a security review block a plugin install because nobody could vouch for the source, you know why this matters. For TYPO3, the integration work is happening at the Tailor CLI level and against the existing extension ecosystem. It’s early, but the direction—sovereign distribution as a first-class concern—is the kind of thing that earns enterprise trust. The North American Opportunity, Honestly Framed ----------------------------------------------- **Pat Ramsey’s solo session on TYPO3 versus WordPress** was the most unhurried block of the day—and exactly because of that, the most useful. The architectural gap is real: WordPress’s two-table content model gets messy at scale; TYPO3’s relational schema doesn’t. The extension ecosystem trade-off is real too: WordPress has more plugins, TYPO3 has fewer but better-tested ones. And migrating from WordPress to TYPO3 is, honestly, an ETL project (extract, transform, load) — custom scripts, careful mapping from text blobs and shortcodes to structured content types, AI assistance for the scaffolding but humans on the cleanup. ![A speaker presents on stage, discussing multilingual governance and features of WordPress and TYPO3, with a slide titled "Improve the Foundation.](https://b13.com/fileadmin/_processed_/a/b/csm_cms-summit-na-3_7fa141e669.webp) Pat Ramsey compares the foundations of CMS ecosystems. The follow-up fireside chat with **Robert Jacobi** covered what the slides couldn’t—and that’s where both of them landed on the point I think is right: switching CMSes wholesale is rarely the right move. Augmentation, then gradual migration, is. Identify the specific friction—editorial workflow, governance gap, integration pain—and replace that piece first. Make the financial and operational case incrementally. **Luisa Sofie Faßbender** closed the day with the business side: how the TYPO3 Association and the TYPO3 Company actually work, what membership and certification get you, where the ideal U.S. client profiles sit (enterprise, government, education, transport, healthcare—the same sectors where TYPO3 dominates in DACH). The U.S. challenge, she said clearly, is awareness, not capability. That’s a more solvable problem than the inverse. What I’m Taking Home -------------------- The day in Atlanta confirmed something we’ve been saying to clients in Europe for years: the technology that wins long-term enterprise work isn’t the loudest one. It’s the one with predictable releases, a non-extractable license, a governance structure that can’t be bought out, and a community that ships features into a core that’s still around in ten years. The North American push is overdue, and the partnership with Crowd Favorite plus the FAIR pivot makes it concrete. If you’re running a CMS in the U.S. or Canada and the words “compliance,” “long lifecycle,” or “migration risk” come up in your quarterly reviews, this is the moment to take a closer look at TYPO3—not as a replacement for what you have, but as the system you augment toward. If you want to walk through what that path could look like for your stack, [let’s talk](https://b13.com/lets-connect). We’ve done this transition in all shapes and sizes (and in most languages), and we’re happy to share what we’ve learned. [ previous article: How to Prevent UX Sprawl in Existing Digital Products ](https://b13.com/blog/how-to-prevent-ux-sprawl-in-existing-digital-products)