SilverStripe CMS
Hosting

SilverStripe CMS is one of those platforms that is much better-known in some markets than others. In New Zealand and Australia it's genuinely mainstream, with central and local government departments running SilverStripe sites at scale. In the UK it's smaller but growing, and I host a couple of UK clients who picked SilverStripe specifically because their senior developers had used it during a stint working in Auckland or Melbourne.

The platform sits in roughly the same conceptual space as Drupal: a developer-oriented PHP CMS with a strong editorial admin, granular permissions, and a real framework underneath. Where SilverStripe differs is the framework feel, it's closer to a Laravel or Yii than to Drupal's Symfony-derived architecture, and the developer experience reflects that. Templates are clean, the data layer is approachable, and the project is well-engineered.

What works well: the admin UI is polished and editor-friendly. The permissions system is granular without being overwhelming. The DataObject model for content is intuitive once you've defined two or three. Multi-language support is built in. The Composer-based deployment story is clean. New Zealand government clients have driven the platform towards strong accessibility and security standards, which benefits everyone.

"SilverStripe is the right answer for editorial teams that need real structured content and a calm admin, where the developer team is happy with a Composer-based PHP framework workflow. It's a smaller community than Drupal, but the platform is well-engineered and respects developer time."

Mark McNeece, Founder, 365i Hosting

What's annoying: smaller community in the UK means smaller ecosystem of UK-based developers who know it. The module marketplace is smaller than Drupal's or WordPress's. Hosting requirements (PHP 8.1+, Composer, decent memory) put SilverStripe firmly in the cloud-server tier, which is the right answer technically but means the platform isn't a fit for budget shared hosting projects. Major version upgrades, like Drupal, need careful planning.

Hosting profile: SilverStripe wants PHP 8.1+ with OPcache, MySQL 8, ideally Redis or Memcached for cache and sessions, plenty of memory, and Composer-based deployment from a Git repository. Our managed cloud servers from £9.99/mo are the right tier. We've hosted SilverStripe sites for a UK government-adjacent client where compliance, accessibility, and security were the headline requirements, and the platform handled all three well.

For typical SilverStripe deployments we set up Composer in deploy hooks, configure OPcache and Redis, separate database backups from filesystem backups, and tune MySQL for the DataObject query patterns. CDN with pre-caching helps with anonymous-user page load. Logged-in editorial admin response is mostly bound by PHP execution time, so memory and OPcache configuration matter.

If you're choosing between SilverStripe and Drupal for an editorial project in the UK, the deciding factors are usually your developer team's familiarity, the specific content modelling needs, and the strength of any required modules in either ecosystem. Drupal has the larger community and bigger module marketplace, SilverStripe has a more polished out-of-the-box admin and a friendlier framework feel. Both are solid choices for serious editorial work.