We’re building a frontend-first framework for composable customer portals – Open Self Service. To support dynamic content, reusable UI blocks, and flexible layouts, we needed a CMS that gives developers control over structure while staying accessible to business users.

That’s where Strapi comes in. In O2S, we use it not just for managing page content, but also for defining layout templates, page structures, and component configurations. This approach helps us find the right balance between flexibility for editors and consistency in the frontend.

Open Self Service (O2S) was launched a few weeks ago and we’ve already started working on the next set of improvements, new features, and fixes to make it better.

In this post, we’re sharing what we’ve shipped so far, what’s currently in progress, and what’s next on the roadmap. Whether you’re exploring O2S or already building with it, this is a quick look at where we’re heading.

We're excited to announce the first release of Open Self Service (O2S) – an open-source framework for building composable, API-agnostic customer service & support frontends.

Open Self Service (O2S) is continuously evolving. Below is an outline of upcoming enhancements and planned features.