Why We Built qqq: The Story Behind the Framework
After building hundreds of enterprise applications, we got tired of writing the same boilerplate. Here's how that frustration became the qqq framework.
In 2013, we founded Infoplus - a warehouse management system that would grow to serve thousands of customers and process millions of transactions daily. By the time we exited in 2021, we had learned something important: the secret to building enterprise software fast isn't writing less code. It's writing the right code once and generating everything else.
Every enterprise project we built had the same patterns: CRUD operations, user management, audit logs, reporting. We were copying code between projects and adapting it each time. There had to be a better way.
The Problem Every Developer Knows
If you've built enterprise applications, you know the drill. Every project needs:
- Authentication and role-based authorization
- CRUD operations with validation
- Audit trails for compliance
- Reports and data exports
- Admin dashboards
These aren't optional features - they're table stakes. Yet we kept building them from scratch, project after project. Our initial estimates would be accurate for the core business logic, but we'd blow the timeline implementing the same infrastructure we'd implemented a dozen times before.
From Copy-Paste to Framework
At Infoplus, we started extracting common patterns into reusable components. Authentication became configurable. Audit logging became automatic. The admin UI started generating itself from our data model.
What emerged was something we called internally "the framework" - a metadata-driven approach where you define your data model once, and the system handles CRUD, validation, permissions, audit logging, and UI generation automatically.
Why Open Source It?
After our exit, we looked at what we'd built and realized the warehouse-specific code was maybe 20% of the system. The other 80%? Generic enterprise patterns that any team could use.
We stripped out the WMS-specific code, cleaned up the architecture, and made a decision: we're releasing it under the Apache 2.0 license. Why? Because we want qqq to be enterprise-friendly and truly open. Apache 2.0 is the same license used by Kubernetes, TensorFlow, and React - pre-approved at most enterprises with no legal friction.
What Makes qqq Different
Most "low-code" platforms lock you into their ecosystem. qqq takes a different approach:
-
It's just Java. No proprietary runtime, no special deployment requirements. If you can run Java, you can run qqq.
-
Full code ownership. When you build with qqq, you own the code. Fork it, modify it, deploy it anywhere.
-
Enterprise features included. Auth, audit logging, RBAC, multi-tenancy - they're not add-ons you integrate later. They're built into the core.
-
Escape hatches everywhere. The generated code and UI are starting points. When you need custom behavior, drop down to Java and write exactly what you need.
The Road Ahead
We're building more than a framework. qBits bring pre-built business applications you can customize. qRun offers managed hosting so you can focus on building. qStudio adds AI assistance for faster development.
But the core of qqq will always be free and open source. We believe the best enterprise tooling should be accessible to every developer, not just those who can afford expensive platforms.
That's why we built qqq. We hope you'll build something great with it.
