Radaptor LLC

At Radaptor, we're changing the game in framework design. Many current frameworks mix layers they shouldn't, pile on complex middleware, and try to act like CMS solutions. This not only complicates things but also makes scaling a nightmare. We believe the core framework should be as simple as possible. It should handle the essentials like user management, authorization (RBAC/PBAC), and error handling without all the extra fluff. That's why we keep the CMS as a separate module with its own router to handle responses, helping you avoid the big mess that often comes with more traditional frameworks. Our approach? Ditch the router. Instead, we let you address modules directly via URL parameters. This means no unnecessary middlemen and still supports friendly URLs by defaulting to the CMS module. We take an event-based approach, where everything is treated as an event. A page request? Just an event that composes a webpage using the CMS module. And the framework? It doesn’t need to render any views. With this setup, complexity grows linearly, and modules can easily be reused across projects—just tweak the views as needed. Plus, since neither the framework nor the CMS is tied to any specific tech, it works with any stack out there. Whether you need modules for GraphQL, HTMX, or anything else, we’ve got you covered. This is how Radaptor works—and it works great. Follow us for more insights and updates!