Frequently Asked Questions

Everything you need to know about qqq, qBits, qRun, and our licensing. Can't find what you're looking for? Ask on Discord.

General

Common questions about qqq and QRunIO

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.
How long does it take to learn qqq?: Start with the source-based sample, then build one table and one backend process. Learning time depends on your Java experience and application requirements; the documentation does not promise a fixed setup time.
Are there production apps running on qqq?: The project grew out of application development experience. QQQ 4.0.0 is available; assess production readiness for the exact release and your application.
How is qqq different from no-code platforms?: QQQ applications are Java source and metadata that you can inspect and extend. You remain responsible for application logic, deployment, and the license terms of selected components.

qqq Framework

Technical questions about the qqq framework

What programming language does qqq use?: QQQ 4.0 targets Java 21. Application metadata and custom backend steps are Java classes; Maven manages framework dependencies.
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.
Does qqq support authentication and authorization?: QQQ has authentication and permission extension points and provider modules. Configure and test the selected provider and application permission rules; no provider is enabled securely just by adding the core dependency.
Can I customize the generated UI?: The metadata-driven dashboard supports table layouts, apps, processes, and widgets. Custom frontend work is possible through the application middleware/API contract. This release train uses Material Dashboard 0.41.0.
How does qqq handle security?: Configure authentication, permissions, validation, and operational controls explicitly. Test allowed and denied access across every entry point. Framework facilities do not guarantee that an application cannot bypass its intended controls.
Does qqq support multi-tenancy?: Tenant isolation is an application design responsibility. Select an isolation model, apply tenant constraints consistently, and test cross-tenant access through queries, processes, exports, and integrations.
How is qqq different from Spring Boot?: QQQ focuses on metadata-driven data applications and Java extension points. Compare a representative workflow against your requirements rather than relying on generic development-speed claims.
Can I migrate an existing app to qqq?: Yes. Introduce one bounded workflow alongside an existing application. Map the database explicitly, decide which system owns writes, and verify authentication, data behavior, and rollback before expanding.
Does qqq support GraphQL?: Automatic GraphQL generation is not part of the verified QQQ 4.0 release scope. Any GraphQL adapter requires a separately implemented and tested integration.
Can I use qqq with microservices?: You can deploy separately built QQQ applications as services. Define service boundaries, data ownership, authentication, and integration failure handling explicitly.
How does qqq handle background jobs and workflows?: QQQ provides processes with Java backend steps and scheduling facilities. Queue delivery, retry policy, idempotency, and recovery depend on the selected implementation and application design.
How often is qqq updated?: Consult repository tags and release notes for actual releases. QQQ 4.0.0 is available. See the tagged release notes and migration guidance for its scope and limitations.

qStudio

Questions about the qStudio AI development assistant

What is qStudio?: qStudio is a preview of development tooling for QQQ. It is independent of the core 4.0 release; confirmed installation and service details will be documented with the released product.
Is qStudio required to use qqq?: No. QQQ application development uses Java and Maven. qStudio is optional and remains a separate preview.
How much does qStudio cost?: qStudio availability and pricing must be confirmed with QRunIO. No generally available subscription tier is established by this release.
What IDEs does qStudio support?: Editor and MCP integrations are product preview concepts until supported clients and setup instructions are published with a release.
Does qStudio require an internet connection?: Connectivity, processing location, and data retention must be confirmed for the actual released service before providing source code or other data.
Can qStudio work with existing qqq projects?: Existing-project support is a planned use case. Verify supported versions and integration steps with an available qStudio release.
How is qStudio different from GitHub Copilot?: qStudio focuses on QQQ development workflows. The preview does not establish comparative accuracy, training claims, or performance guarantees against another assistant.
Can I use qStudio with my team?: Team access, billing, and shared-context features require separately confirmed product availability and terms.

qBits

Questions about qBits components and marketplace

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.
Are qBits free?: Availability, pricing, and licensing depend on the selected qBit. The public catalog currently shows previews, not a verified set of 4.0-compatible packages for purchase.
Can I create my own qBits?: Yes. Start with the application, data, or extension template, choose your own Maven coordinates, implement the metadata producer, and test it in a host application. See /docs/tutorials/first-qbit.
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.

qRun Hosting

Questions about managed hosting and deployment

What is qRun?: qRun is a planned managed hosting product. The 4.0 framework release does not establish cloud service availability, pricing, backups, or support commitments.
Do I have to use qRun?: No. The framework can run on infrastructure you manage. Managed hosting is a separate product decision.
What's included in qRun hosting?: Service plans and commitments must be confirmed with QRunIO. This site does not currently offer a generally available qRun hosting plan.
Can I migrate to/from qRun?: Keep code, configuration, data migrations, and backups portable. Moving a deployment requires validating networking, identity, secrets, database compatibility, and operational procedures in the destination.

Licensing

Questions about licenses and pricing

Which license applies to my application dependencies?: 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.
Can I use qqq for commercial projects?: 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.
How should an enterprise review licensing?: Use your organization's normal dependency and license review for the selected artifacts. The website does not determine whether a component is approved for your use.
Is qStudio free?: qStudio is in preview. Public availability and subscription terms have not been established by the QQQ 4.0 release.
Do I need a commercial license?: 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 happens if QRunIO shuts down?: Keep source, dependency versions, build instructions, and operational runbooks under your control. Continued use and redistribution follow the licenses supplied with your selected components.

Compliance & Auditing

HIPAA, SOC 2, HITRUST, and regulatory compliance

Is qqq SOC 2 or HIPAA compliant?: The framework is not a compliance certification. Assess the complete deployed system and the contractual requirements for your use case. The 4.0 release makes no SOC 2 or HIPAA certification claim.
Does qqq have audit logging?: QQQ includes audit-related facilities. Configure the required records, actor context, retention, and access controls, then verify the events your application needs. Do not assume every action is logged automatically.
Can qqq help with HITRUST certification?: A framework release does not confer HITRUST certification. Evaluate the actual application, infrastructure, organizational controls, and assessment requirements independently.
How does qqq handle data encryption?: Configure TLS, database/storage encryption, secret management, and any field-specific protection in your application and infrastructure. Encryption and key rotation are not enabled universally by QQQ metadata.
Does qqq support data retention policies?: Implement and test retention jobs appropriate to your data and obligations, including backups and audit records. Scheduling a process does not by itself define a retention policy.
Can I get a BAA for HIPAA compliance?: Contact the relevant service provider about any required agreement before using a service for regulated data. This site does not promise a BAA or a HIPAA-ready hosting plan.
How does qqq handle access controls for compliance?: Define application permission rules and test their enforcement through each relevant entry point. Include denied-access tests; do not assume custom Java actions inherit all intended restrictions.
Is there a compliance-focused deployment guide?: The knowledge base includes security and operational guidance. It is a starting point for reviewing a deployment, not a certification checklist or a guarantee of compliance.

Support

Getting help and community resources

How do I get help with qqq?: Use the framework documentation at /docs and report reproducible issues in github.com/QRun-IO/qqq. Include the exact version, failing command, and a minimal example with secrets removed.
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.
Do you offer training or consulting?: Contact QRunIO about training or consulting needs. Scope and scheduling are agreed separately from the framework release.
Where can I report bugs or request features?: Use github.com/QRun-IO/qqq/issues. Include the exact release, environment, reproduction steps, and expected result.

Still have questions?

Our community is here to help. Join Discord for real-time support or browse the documentation.

Join Discord->

View Documentation