Jan Jagoda

Over the past few years, we’ve worked on many large-scale solutions. E-commerce applications, customer support portals, B2B service hubs - all combining content, integrations (PIM, search, e-commerce, ERP, IAM, custom APIs) and user-facing functionality, where delivering strong user and customer experience has always been a key priority.

Many of those platforms were built on top of enterprise products. These provided headless backend APIs and, in some cases, their own frontend layer as well.

Usually in practice, the frontend quality was rarely good enough.

We’re excited to share the initial release of our integration between Open Self Service and Medusa.

This integration allows developers to easily display commerce-related data such as Orders, Assets, and Services within customer-facing portals built with O2S.

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.

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

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.