<software />
I started building my own platform back in 2003–2004, when decent CMS options barely existed and e-commerce was almost unheard of. At that time, there were only a few experimental systems around, and none of them truly combined content and commerce.
From the very beginning I worked with SEO in mind, listened closely to client requests, and kept refining the common elements every project seemed to need. Unlike many “pure” shop systems, my approach was to build a hybrid: a CMS and a Shop under the same roof. That’s because every online shop also needs content — sometimes a lot of it. For example, a grocery store that also wants to publish recipes is far better served by a CMS-driven shop than by a shop-only platform.
Having my own platform also gave me the freedom to create highly customized features — the kind of things that are very hard, if not impossible, to achieve when stitching together separate systems.
My first prototypes were rough, but they already carried some of the ideas that are still core today. For instance, one of my client websites from 2007 used “masked pages” to generate permalink-style URLs — before .htaccess rewriting became mainstream. That early focus on usability and search-friendly structure has stayed with me ever since.
From these beginnings, EZMedia emerged as the current generation of my CMS+Shop system. It merges:
Unlike many CMS platforms that struggle with commerce, or e-commerce platforms that lack content management, EZMedia was designed from day one as a hybrid solution.
EZMedia has everything a CMS and Shop system needs — and, more importantly, the flexibility to add what your business actually requires. I know the platform inside out, because I’ve built and rebuilt it across multiple generations. That gives me the confidence to implement almost anything that is logically possible, not just what comes in a predefined feature list.
The experience accumulated with EZMedia is now being transformed into my next-generation platforms:
With EZMedia I provide proven stability. With evoCORE and evoSHOP I prepare the future.
I learned early that using overly complicated tools when a simpler approach works is a mistake. That principle has guided me ever since: clarity and efficiency matter more than trend-driven complexity.
Therefore, none of my platforms follow the single-page app (SPA) model. From an SEO perspective, SPA is problematic — and that’s not what you want for your online shop.
At the same time, the backend is flexible enough: since it already works with page-based scripts, exposing endpoints for a custom frontend is straightforward if a project really requires it. The foundation is always the data, and that part is solid
I do keep a detailed technical sheet, but I share it only on request. For most clients, what matters is that EZMedia already covers all essentials, has been proven in production for years, and remains open to deep customization whenever it makes business sense.