I'm trying to move away from WordPress and dive into building websites using Next.js and React. I'm excited about creating a more code-centric approach, but I don't want to stick to fully static sites. I'm exploring headless CMS options and have some specific needs: I need a solution that can integrate with GitHub for deployment triggers, support multi-tenancy with customer logins, allow for storage integration with S3, be lightweight in resource usage, and have a modern, user-friendly interface. I've tried out Strapi but found it a bit clunky, and while Payload is fully code-based, it didn't click with me right away. What are your go-to options for a self-hosted headless CMS?
8 Answers
Be careful! Many sites built on WordPress require ongoing management, and any issues with JavaScript packages can cause major headaches. One older theme could break all at once—it's not as resilient as WordPress where many themes still work with minor tweaks.
For a straightforward experience, I’d recommend checking out Sanity.io—I've been using it since 2019 and I absolutely love it! Definitely worth considering for your project.
If you're working with Next.js, Payload could be the way to go. It's specifically designed for that stack. Just a heads up, some major LLMs were still using older versions of Payload a few months back, so that might influence your decision, depending on your needs.
Directus supports S3 storage, so that's one option to look into. But can you clarify what you need in terms of multi-tenancy?
For a lightweight solution, I’d look at Directus and Payload first, then maybe Strapi if your team is already familiar with it. For such requirements, using Payload with PostgreSQL fits perfectly with Next.js. Directus is also user-friendly for non-dev clients, and for multi-tenancy, plan how you model tenant IDs early on—it's super important!
Strapi is a solid choice, but keep in mind it has its own way of managing content, which can feel restrictive. Our team found Directus to be better because it allows for more flexibility with database setups, making it easier to disconnect from it later if needed. Drupal can work too but it's heavier than Strapi and offers greater modularity. Not sure about Payload, though.
Totally agree! Strapi can be a pain; check the GitHub issues. Directus is decent but can feel a bit slow. Pocketbase might be a better alternative to consider.
You’re looking for a self-hosted setup with S3 storage? If you want a more managed experience, check out Brill Software or Enonic XP. They might have the multi-user features you need while managing things fairly well.
For multi-tenancy, it's more about how you structure your data than the CMS itself. Most of these options can do it—just plan ahead!
Payload seems great from what I've seen, but just be mindful of those older versions!