Sulu

A PHP developer’s CMS, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (MIT) PHP content management system built on Symfony — designed for agencies and developers who need to manage complex, multi-site, multilingual content without stitching together plugins [README][website].
• Who it’s for: PHP/Symfony developers and digital agencies building enterprise websites. Not a tool for non-technical founders. This is explicitly positioned as an “agency platform” [website].
• Cost savings: The software is free. The cost is developer time. Compared to proprietary CMSs (Contentful at $300+/mo for growing teams, Sitecore at enterprise pricing), Sulu self-hosted costs only the VPS and the PHP developer who sets it up.
• Key strength: Multi-site and multilingual out of the box, without plugins or workarounds. A single Sulu instance can manage hundreds of locales and multiple domains through its “Webspaces” architecture [README][website].
• Key weakness: 1,320 GitHub stars is modest for a CMS in 2026. The project has niche traction — heavy in the German-speaking market, relatively unknown elsewhere. If your developer doesn’t already know Symfony, the learning curve is steep [README].

---

What is Sulu

Sulu is a PHP CMS built on top of the Symfony framework, developed by Massive Art Web Services, an Austrian digital agency. The project started as an internal tool, open-sourced under MIT, and has since grown into a product the company actively markets to other agencies and enterprise clients [website].

The core pitch is in the tagline: “Open Source. Fit for Enterprise.” [website]. That’s not a Zapier-style “any non-technical person can use this” pitch — it’s a signal that this tool is aimed at organizations that have already outgrown WordPress, need multi-site management across dozens of domains, and want a clean Symfony codebase their developers can extend without fighting the framework.

What makes it different from generic PHP CMSs: Sulu is not a plugin ecosystem. It’s a framework. Content types, page templates, and navigation are defined in XML and PHP rather than point-and-click. This is either a feature or a dealbreaker depending on whether you have a Symfony developer on hand [README].

The tech stack: PHP 8.2+, Symfony 6.4–7.4, a React-based admin interface, and a REST API exposed for headless or hybrid use [README][website]. As of this review, the GitHub repository sits at 1,320 stars — modest by open-source CMS standards, but the project has active CI, regular commits, and real enterprise case studies behind it.

---

Why people choose it

The third-party review landscape for Sulu CMS is thin. Unlike Wordpress or Drupal, Sulu doesn’t have a large community generating independent benchmarks and comparison posts in English. What we have are the Sulu team’s own blog posts and a handful of case studies. This is itself a signal: Sulu is a specialist tool with specialist adoption, not something you pick up from a Reddit thread.

The case studies on the website reveal who actually deploys it: Zangersheide (equestrian industry site with complex UX customization), Lech Zürs (Austrian ski resort with seasonal content segmentation), and Allianz Cinema (Swiss open-air cinema managing scheduling, ticketing, and sponsorship for 100,000 attendees per season) [website]. These are not hobby projects or startup landing pages. They’re custom, complex, high-traffic websites with demanding content structures — exactly the use case Sulu targets.

Sulu’s own documentation on integrations [1] reveals a philosophy: rather than bundling every integration as a plugin, Sulu exposes standard Symfony HTTP clients, REST APIs, webhooks, and event dispatchers. You wire up your own connections to HubSpot, Salesforce, Mailchimp, or Sylius (an open-source e-commerce framework). The upside is a clean, maintainable architecture. The downside is that there’s no plugin marketplace to click through — you need a developer to build each integration [1].

On AI: the Sulu team published an explicit “AI Manifesto” [2] positioning themselves carefully. Key commitments: the core stays 100% open source, AI features are optional add-ons, they won’t force AI on users. Their new Sulu.ai product (updated in March 2026 with Symfony AI Foundation, Agents support, and Sulu 3 compatibility) is a separate commercial layer on top of the MIT core — AI content assistance, translations, SEO suggestions [website][2]. Whether that commercial separation is reassuring or suspicious depends on your risk tolerance for open-source-core / commercial-features business models [2].

The developer testimonials collected on the website are consistently from PHP/Symfony shops: “It’s great how easy it is to set up a simple website and keep focus on custom development instead of template development” (Michel Falke, Friday B.V.) and “The capabilities to handle even hundreds of localizations in one instance and the great integration with Symfony, made it easy to choose Sulu” (Tobias Niebergall, e3n GmbH) [website]. Nobody says “I switched from WordPress and set it up myself in an afternoon.”

---

Features

Core CMS:

• Multi-site management via “Webspaces” — one instance, multiple domains, independent navigation trees and configurations [website][README]
• Native multilingual support: multiple locales per content item, change management for translations, no third-party plugin required [README][website]
• Page templates defined in XML, giving developers explicit control over content structure [README]
• Navigation management, task automation, shareable preview links, form management, SEO fields built-in [website]
• Full content lifecycle management [README]

Flexibility:

• Traditional (Twig-rendered), headless (REST API only), or hybrid modes [website]
• REST API for decoupled frontends [website]
• Symfony event system for loose coupling between services [1]
• Symfony HTTP client for consuming third-party APIs [1]
• Webhooks for receiving events from remote systems [1]

Enterprise integrations (DIY, not plugin-click):

• CRM: HubSpot, Salesforce — via API integration [website]
• E-commerce: Sylius headless integration for real-time product data [1]
• SSO: supported via Symfony bundles [1]
• Search engine integration possible via API [website]

AI add-on (Sulu.ai — commercial, separate from MIT core):

• Symfony AI Foundation integration [website]
• AI Agents support [website]
• Sulu 3 compatibility confirmed as of March 2026 update [website]
• Writing assistance, translations, SEO — per the AI Manifesto [2]
• Explicitly optional; never bundled into core [2]

Deployment:

• Deployment-agnostic: single-server scripts or Kubernetes for horizontal scaling [website]
• Git-versioned configuration [website]
• Full test suite [website]

What’s not built-in:

• Plugin marketplace (you write extensions as Symfony bundles)
• One-click integrations with SaaS tools
• Visual page builder in the Elementor sense
• Any AI features without the commercial Sulu.ai add-on

---

Pricing: SaaS vs self-hosted math

Sulu’s pricing model is straightforward on paper: the software is MIT-licensed and costs nothing. The actual cost equation is developer time.

Sulu self-hosted:

• License: $0 [README]
• VPS: $10–40/mo (Sulu is more resource-intensive than a simple blog — PHP, MySQL/PostgreSQL, ElasticSearch for full-text search, web server)
• Developer time: significant. Setting up Sulu from the skeleton template, configuring webspaces, defining content types, and deploying is not a weekend project for a PHP beginner

Sulu.ai (commercial add-on):

• Pricing not publicly listed on the website — contact sales [website]

What you’re replacing:

• Contentful (headless SaaS CMS): free tier caps at 2 users and limited content; paid starts at ~$300/mo for teams
• Sitecore: enterprise licensing in the tens of thousands per year
• Craft CMS: $299/site or $59/mo (perpetual license, not open source)
• Statamic: $259/site or $259/site/year for teams

For an agency running 10–20 client sites, self-hosting Sulu on a single Hetzner server at $40/mo and managing all sites in one instance is a genuinely compelling proposition against paying per-site CMS licensing fees. That math is why the case studies are agencies, not individual founders.

For a solo non-technical founder: this comparison is irrelevant. Sulu is not in your shortlist.

---

Deployment reality check

The README’s recommended starting point is the sulu/skeleton repository — a pre-configured Composer project template [README]. From there:

What you actually need:

• PHP 8.2+ and Composer
• MySQL or PostgreSQL
• A web server (Apache or Nginx)
• ElasticSearch (optional but needed for full-text search)
• Symfony CLI for local development
• A Linux server with at least 2–4GB RAM for production

What can go sideways:

• Sulu’s content type system requires defining templates in XML before content editors can create pages. There’s no “just start adding content” path — you configure structure first, then editorial workflow second. Non-technical teams will hit a wall immediately.
• The admin interface is React-based and generally well-received by developers, but it’s not a drag-and-drop page builder. Content editors familiar with WordPress Gutenberg or Webflow will find it more constrained.
• Multisite and multilingual are genuinely powerful, but configuring webspaces involves editing YAML files. This is not the kind of thing you Google your way through in an hour.
• The community is real (Slack, GitHub Discussions, StackOverflow sulu tag) but smaller than WordPress or Drupal [README]. Stack Overflow answers for niche Sulu issues may not exist yet.
• Third-party extensions exist but the catalog is thin — you’re expected to write Symfony bundles, not install plugins from a marketplace.
• The Sulu.ai commercial layer introduces a dependency on an external service if you use AI features, which tensions against the self-hosted model [2].

Realistic time estimate for a Symfony developer: 1–2 days to a working site with basic content types. For a team with no Symfony experience: budget a week to understand the architecture before writing production code. For a non-technical founder: not recommended without hiring a Symfony developer or a Sulu partner agency.

---

Pros and Cons

Pros

• MIT license, no commercial restrictions. You can self-host, embed in client projects, and redistribute without a commercial agreement. No “Fair-code” restrictions, no “3-server limit” on community edition [README].
• Multi-site from one instance. Webspaces architecture handles dozens or hundreds of sites, each with independent domains, navigation, and configurations — without separate installs [website][README].
• Multilingual built-in. Handling hundreds of locales in one instance without plugins is a documented, tested capability — not a bolt-on [website][README].
• Symfony foundation means real extensibility. Any Symfony bundle works. Any PHP developer with Symfony knowledge can extend it. No fighting a plugin API with its own conventions [README][1].
• Deployment-agnostic scaling. From a $10/mo VPS to Kubernetes — the architecture supports both without platform lock-in [website].
• Responsible AI stance. The AI Manifesto [2] is an unusually transparent document. The commitment to keeping core 100% open source while offering commercial AI add-ons is a cleaner model than vendors who retrofit AI into existing pricing tiers.
• Active corporate backing. Massive Art is a real company with a real services business around Sulu. The project isn’t maintained by one volunteer who might disappear [website].

Cons

• Not for non-technical users. Content type configuration is code, not clicks. The admin interface serves editors well but setup and deployment requires a PHP developer. This is a feature for agencies and a dealbreaker for everyone else.
• 1,320 GitHub stars is modest. For comparison, Strapi (Node.js headless CMS) has 65,000+ stars, Ghost has 47,000+. Sulu has a niche. That means a smaller community, fewer Stack Overflow answers, and a higher risk that the tool loses momentum [README].
• No plugin marketplace. Every non-core integration is a Symfony bundle you write yourself or commission. Compared to WordPress (60,000+ plugins) or even Craft CMS (hundreds of commercial plugins), Sulu has very little click-to-install functionality.
• Heavy on configuration. XML template definitions, YAML webspace configuration, Composer dependency management — the initial setup surface area is wide. Mistakes at configuration time surface late.
• No published pricing for Sulu.ai. The commercial AI layer has no public pricing. “Contact sales” for a developer tool aimed at agencies is mildly annoying and suggests either very variable pricing or a deal-by-deal model [website].
• English documentation and community lag behind German. The project originates from an Austrian agency and has strongest traction in the DACH market. English-language resources are improving but thinner than for comparable CMSs.
• ElasticSearch dependency for search adds operational complexity. Running ElasticSearch alongside PHP and a database server means higher memory requirements and one more service to monitor.

---

Who should use this / who shouldn’t

Use Sulu if:

• You’re a PHP/Symfony developer or agency building enterprise websites that require multi-site management from a single instance.
• Your client has multilingual requirements across 10+ locales and you’ve watched WordPress multilingual plugins fail at scale.
• You want MIT-licensed software you can include in client deliverables without per-site licensing fees.
• You’re replacing a proprietary enterprise CMS (Sitecore, Adobe Experience Manager) and need the flexibility to match complex content models.
• Your team already uses Symfony for other projects and wants to leverage that investment.

Skip it (use WordPress or Ghost) if:

• You’re a non-technical founder building your first website or blog.
• You need a point-and-click page builder, visual editing, or a plugin marketplace.
• Speed of setup matters more than long-term maintainability.

Skip it (use Strapi or Directus) if:

• You want a headless CMS and your team is Node.js-first, not PHP-first.
• You need a large community, extensive API documentation, and existing integrations out of the box.
• You want a REST/GraphQL API CMS without the overhead of a full multi-site content management platform.

Skip it (use Craft CMS or Statamic) if:

• You need a PHP CMS with a polished plugin ecosystem and strong community in English.
• Budget for a commercial license ($259–$299/site) is acceptable and you’d rather pay for polish than configure.

---

Alternatives worth considering

• WordPress — still the dominant PHP CMS with 60,000+ plugins and the largest community. More technical debt, more security surface, but near-infinite flexibility and a non-technical editor experience [general knowledge].
• Strapi — Node.js headless CMS, 65,000+ GitHub stars, stronger ecosystem for API-first projects. Not multi-site by default.
• Directus — Another Node.js headless CMS wrapping your existing database. Faster to set up than Sulu for pure API use cases.
• Ghost — Clean, minimal publishing platform (MIT) for blogs and newsletters. Not a general-purpose CMS.
• Craft CMS — PHP CMS with the best developer experience in its tier, but $259/site commercial license, not open source.
• Statamic — PHP flat-file CMS with elegant developer tooling, commercial licensing.
• Drupal — The other serious PHP CMS for enterprise. Steeper learning curve than Sulu, larger community, older architecture.

For PHP agencies with Symfony expertise: the realistic shortlist is Sulu vs Craft CMS. Sulu wins on license (MIT vs commercial) and multi-site architecture. Craft wins on plugin ecosystem and community depth.

---

Bottom line

Sulu is a legitimate enterprise CMS that solves a real problem: managing complex, multi-site, multilingual content in PHP without proprietary licensing or plugin soup. The MIT license, Symfony foundation, and multi-site-from-one-instance architecture are genuine differentiators for the agency and enterprise market. The trade-offs are real and honestly disclosed by the project itself — this requires PHP/Symfony expertise, has a modest community outside the German-speaking market, and offers no plugin marketplace for non-developers.

The tool is not positioned for non-technical founders, and pretending otherwise would be dishonest. If you’re a solo founder looking to escape expensive SaaS, Sulu is not your answer — Ghost, WordPress.com, or a managed Strapi instance will serve you better. But if you’re an agency or an engineering team that has watched multilingual WordPress installs fail, or you’re replacing a Sitecore license that costs more per year than your team’s hardware budget, Sulu is worth a serious look. The 1,320 stars don’t reflect the quality of the tool — they reflect the specificity of the audience it’s built for.

---

Sources

1. Thomas Schedler, Sulu Blog — “Third-party integrations with Sulu CMS: Backend Synergies”. https://sulu.io/blog/backend-synergies-seamless-3rd-party-integrations
2. Thomas Schedler, Sulu Blog — “The Sulu AI Manifesto: How Sulu Enables CMS and LLM Synergies”. https://sulu.io/blog/the-sulu-ai-manifesto-inducing-synergies-between-ai-and-cms

Primary sources:

• GitHub repository and README: https://github.com/sulu/sulu (1,320 stars, MIT license)
• Official website: https://sulu.io
• Sulu Skeleton starter template: https://github.com/sulu/skeleton
• Official documentation: https://docs.sulu.io/en/latest/book/getting-started.html