Metadata-driven applications
Define tables, fields, relationships, apps, and processes in Java. Manage the database schema explicitly.
Our Story
We got tired of rebuilding the same application plumbing
Every enterprise project starts the same way: authentication, CRUD operations, admin UI, audit logging, API endpoints. None of it is your competitive advantage. All of it is slow, hard, and a liability waiting to happen.
The Problem We Kept Hitting
Project after project, we found ourselves writing the same boilerplate. Build the data layer. Wire up the API. Create the admin screens. Add authentication. Implement audit trails. Handle permissions. It was months of work before we could even start on the features that actually mattered.
And every time, that undifferentiated code became technical debt. Security patches. Framework upgrades. Bug fixes in CRUD logic that should have been trivial. Repeated application plumbing still needs maintenance.
We wanted a different approach: define what your application does, not how to build the plumbing. An opinionated framework that makes the right choices so you can focus on the behavior your users need.
What We Believe
Opinionated by Design
Flexibility is overrated. The best frameworks make decisions for you so you can ship instead of debating architecture. When you need to break the rules, you can—it's just Java.
Source You Can Review
Review the framework source and the license materials for the exact components you select. Keep your build and deployment process under your control.
Enterprise Without the Pain
Consider security, data access, recovery, and scale while designing your application. Validate those requirements with configuration, tests, and operational checks.
The road to QQQ 4.0
QQQ 4.0 brings the framework, sample, starter, and reusable templates through a coordinated release process.
The foundation
Core
Java metadata and extension points
Describe tables, fields, apps, and processes. Implement application behavior in Java.
Candidate validation
4.0 RC
Validate the release train
The core artifacts, sample, starter, BOM, and templates went through release validation. RC.2 was an earlier published candidate.
General availability
4.0
QQQ 4.0.0 is available
Use the v4.0.0 source tag, core 4.0.0 artifacts, and Material Dashboard 0.41.0. Production qBits and the Next frontend have separate release scopes.
Capabilities to configure and extend
Reuse framework facilities while keeping application behavior explicit. Validate the exact release with your data, identity provider, and workflows.
Authentication integration
Select and configure an authentication provider. Test login, logout, session handling, and denied access.
Backend modules
Use relational, MongoDB, SQLite, file-system, S3, or REST modules. Supported operations vary by backend.
Java process steps
Compose process metadata with Java backend steps. Implement business rules and recovery behavior explicitly.
Application permissions
Configure the permission rules for your application and test them across queries, processes, and custom entry points.
Metadata-driven dashboard
Use dashboard 0.41.0 with compatible table, app, process, and widget metadata. Review the sample UI.
Audit requirements
Configure audit-related facilities and verify the events, actor context, retention, and access rules your application needs.
Application APIs
Use the selected middleware/API module and its actual contract. Automatic GraphQL generation is outside this release scope.
Reporting and export
Configure reports and supported export formats for your backend, then test representative data and access restrictions.