Choose your path with QQQ

Use QQQ 4.0 and self-host the framework. qBits, managed hosting, and qStudio have separate availability and terms.

Java framework; review the selected release licenses

Self-Hosted
Framework source
Self-hosted
Review the selected artifact licenses. Infrastructure and operations are your responsibility.
Try QQQ 4.0

Start with the verified development path:

  • Java 21 and Maven
  • Metadata-driven tables and processes
  • Backend modules and Java extension points
  • Dashboard 0.41.0
  • Source and migration documentation
Support discussion
Contact us
Agree scope and response terms for your application.
Discuss support

Topics to discuss:

  • Architecture and migration review
  • Application integration needs
  • Training and operational readiness
  • Availability and response expectations

Review the source and the selected licenses

QQQ applications use Java and Maven and can run on infrastructure you manage. Review the LICENSE, NOTICE, and source-file headers for the exact framework release and each dependency. Framework licensing, infrastructure costs, and optional support are separate decisions.

License materials and component review

Self-Hosted vs Managed

Self-host the framework today. Discuss availability and responsibilities separately for the qRun managed hosting preview.

Self-Hosted

Full control & flexibility

  • Build from source with Java and Maven
  • Select your infrastructure
  • Manage identity, secrets, and databases
  • Maintain deployment and backup procedures
  • Review licenses for all selected components
View on GitHub

Managed (qRun)

Product preview; confirm availability

  • Discuss application requirements
  • Confirm service availability
  • Agree deployment responsibilities
  • Review data handling and recovery
  • Establish support terms
Discuss hosting
Not sure which license works for you?
Explore our licensing guide

Need help choosing? Talk to our team.

Whether you need enterprise pricing, custom deployment options, or have questions about which plan fits your team, we are here to help.

Frequently Asked Questions

  • Is qqq really free?

    Review the LICENSE, NOTICE, and individual source-file headers in the exact framework release and each dependency you select. The repository-level license does not replace component-specific materials. See /licensing for the source links.

  • What's the difference between qqq and qRun?

    QQQ is the Java application framework. qRun is a planned managed hosting offering; it is not required for QQQ 4.0. Confirm availability and service terms before planning a deployment.

  • Do I need qStudio to build qqq apps?

    No. Use Java 21, Maven, and your preferred IDE. qStudio is an optional product preview and is not part of the QQQ 4.0 release gate.

  • What databases does qqq support?

    The 4.0 modules include relational, MongoDB, SQLite, file-system, S3, and REST backends. Operations and query support vary by backend. A shared action interface does not guarantee cross-backend joins or transactions.

  • Can I self-host qqq applications?

    Yes. Build a Java application and run it on infrastructure you control. You configure the database, authentication, TLS, backups, monitoring, and deployment process.

  • What are qBits?

    qBits package reusable application metadata, data integrations, or extensions. The 4.0 train includes templates; production business qBits have separate release and compatibility checks.

  • How do I install a qBit?

    Use a qBit's verified Maven coordinates and version, then register its metadata producer in the host application. Follow that component's README. A catalog preview is not an installable package.

  • How does enterprise support work?

    Contact QRunIO to discuss support requirements and agree scope, availability, and response terms. The framework release itself does not include a support SLA.

Ready to build faster?