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?
- Yes. The qqq framework is open-source under the Apache 2.0 license. You can use it for free, build commercial products, self-host anywhere, and keep your code proprietary. No vendor lock-in, ever.
- What's the difference between qqq and qRun?
- qqq is the open-source framework you use to build applications. qRun is our managed hosting platform that handles deployment, scaling, and operations so you can focus on building.
- Do I need qStudio to build qqq apps?
- No. qStudio is an optional visual development environment that makes building qqq apps faster. You can build qqq apps with any IDE or text editor - it's just Java code.
- How long does it take to learn qqq?
- Most Java developers are productive within a day. If you know Java, you already know how to extend qqq. The metadata-driven approach means less code to learn—define your tables and fields, and qqq handles the rest. Start with our 90-second quickstart to see it in action.
- Are there production apps running on qqq?
- Yes. qqq has powered production applications since 2007, including warehouse management systems serving thousands of customers and processing millions of transactions. The framework is battle-tested at enterprise scale with years of real-world production use.
- How is qqq different from no-code platforms?
- No-code platforms (Salesforce, OutSystems) lock you into their ecosystem and limit customization. qqq gives you real code ownership—it's Java you can read, modify, and deploy anywhere. When you hit platform limits, you drop down to Java instead of hitting a wall.
qqq Framework
Technical questions about the qqq framework
- What programming language does qqq use?
- qqq is written in Java (version 21+). Your application code is also Java, but qqq's metadata-driven approach means you write far less code than traditional frameworks.
- What databases does qqq support?
- qqq supports PostgreSQL, MySQL, MongoDB, and can connect to external REST APIs as data backends. You can even query across multiple backends with a unified API.
- Can I self-host qqq applications?
- Absolutely. qqq applications are standard Java applications that run anywhere Java runs - AWS, GCP, Azure, on-premises, or your own servers. You have complete control.
- Does qqq support authentication and authorization?
- Yes. qqq includes built-in authentication with support for table-based users, OAuth providers, and SSO. Role-based access control (RBAC) allows fine-grained permissions down to the field level.
- Can I customize the generated UI?
- Yes. While qqq auto-generates a complete admin UI, you can customize layouts, add widgets, override components, and even build completely custom frontends using the generated API.
- How does qqq handle security?
- Security is built into the core. qqq includes field-level permissions, role-based access control (RBAC), automatic audit logging, session management, and support for OAuth/SSO. Every data access goes through the permission system—there's no way to accidentally bypass it.
- Does qqq support multi-tenancy?
- Yes. qqq has first-class multi-tenancy support with tenant isolation at the data layer. You can run multiple tenants in a single deployment with automatic data segregation, or deploy separate instances per tenant—your choice.
- How is qqq different from Spring Boot?
- Spring Boot is a general-purpose framework—you build everything yourself. qqq is opinionated for enterprise apps: define your data model and get CRUD, APIs, admin UI, auth, and audit logging automatically. Use Spring Boot when you need maximum flexibility; use qqq when you want to ship faster with less code.
- Can I migrate an existing app to qqq?
- Yes, but it's typically easier to build new modules in qqq alongside your existing app. qqq can connect to your existing database and expose APIs that your legacy code can call. Many teams adopt qqq incrementally—new features in qqq, legacy code stays as-is.
- Does qqq support GraphQL?
- qqq generates REST APIs by default. GraphQL support is on the roadmap. In the meantime, you can add a GraphQL layer on top of qqq's service layer if needed—it's just Java.
- Can I use qqq with microservices?
- Yes. qqq applications are standard Java apps that can be deployed as microservices. Each service can have its own qqq instance with its own data model, or you can build a monolith and split later. qqq doesn't impose an architecture.
- How does qqq handle background jobs and workflows?
- qqq has a built-in process engine for background jobs, scheduled tasks, and multi-step workflows. Define processes in metadata, add custom steps in Java, and let qqq handle queuing, retries, and error handling.
- How often is qqq updated?
- We release updates regularly—typically monthly for minor versions with bug fixes and improvements. Major versions are less frequent and come with migration guides. All releases are tagged on GitHub with changelogs.
qStudio
Questions about the qStudio AI development assistant
- What is qStudio?
- qStudio is an AI-powered development assistant specifically trained to understand qqq patterns and best practices. It helps you build qqq applications faster by generating metadata, suggesting patterns, and catching common mistakes before they become problems.
- Is qStudio required to use qqq?
- No. qStudio is completely optional. You can build qqq applications with any IDE or text editor—it's just Java code. qStudio simply accelerates development by providing AI-assisted code generation and pattern suggestions.
- How much does qStudio cost?
- qStudio has a free tier for individual developers that covers basic AI assistance. Pro features like MCP server integration and team collaboration require a paid subscription. See our pricing page for current plans.
- What IDEs does qStudio support?
- qStudio integrates with popular IDEs through the MCP (Model Context Protocol) server. This includes VS Code, IntelliJ IDEA, and other editors that support MCP. The core AI assistance works with any development environment.
- Does qStudio require an internet connection?
- Yes. qStudio's AI features require connectivity to process requests. However, all code generation happens in your local environment—your source code is never stored on our servers.
- Can qStudio work with existing qqq projects?
- Yes. The free tier understands qqq code and patterns out of the box. qStudio Pro goes further—it indexes your specific codebase and learns your application's data model, processes, and custom logic to provide deeply contextual suggestions.
- How is qStudio different from GitHub Copilot?
- GitHub Copilot is a general-purpose code assistant. qStudio is specifically trained on qqq patterns—it understands MetaDataProducers, RecordEntities, processes, and qqq conventions. It suggests qqq-idiomatic code, not generic Java.
- Can I use qStudio with my team?
- Yes. Team plans allow multiple developers to share qStudio access with unified billing. Team features include shared context, consistent code suggestions across the team, and admin controls for managing access.
qBits
Questions about qBits components and marketplace
- What are qBits?
- qBits are pre-built components and integrations for qqq. Think of them as plugins that add functionality - from authentication providers to complete business modules like OMS or WMS.
- Are qBits free?
- Community qBits are free and open-source. Premium qBits from QRunIO and partners offer advanced enterprise integrations and are available for purchase. You can also create, share, or license your own qBits.
- Can I create my own qBits?
- Absolutely! qBits are Maven packages that follow a simple interface. Check out our tutorial on building your first qBit. You can keep them private, open-source them, or license them on the marketplace.
- How do I install a qBit?
- Use qctl to add a qBit with one command: `qctl qbit add <name>`. Alternatively, add it manually as a dependency in your pom.xml and register it in your MetaDataProvider. Either way, the qBit's tables, processes, and UI components are automatically available.
qRun Hosting
Questions about managed hosting and deployment
- What is qRun?
- qRun is our managed hosting platform for qqq applications. We handle deployment, scaling, backups, monitoring, and updates so you can focus on building your application.
- Do I have to use qRun?
- No. qqq applications are standard Java apps that run anywhere. qRun is optional but saves you the work of managing infrastructure. Many teams self-host successfully.
- What's included in qRun hosting?
- All plans include deployment automation, SSL certificates, daily backups, monitoring, and automatic updates. Higher tiers add more resources, custom domains, and priority support.
- Can I migrate to/from qRun?
- Yes. Your qqq application code is the same whether self-hosted or on qRun. You can start on qRun and migrate to self-hosted (or vice versa) anytime with no code changes.
Licensing
Questions about licenses and pricing
- What does the Apache 2.0 license mean for my app?
- Apache 2.0 is a permissive license with no copyleft requirements. You can build any application—including commercial SaaS products—and keep your source code proprietary. Your code is yours.
- Can I use qqq for commercial projects?
- Yes. Apache 2.0 allows full commercial use with no restrictions. Build a SaaS product, charge customers, and keep your source code proprietary. No license fees, no source sharing required.
- Is Apache 2.0 enterprise-friendly?
- Yes. Apache 2.0 is the same license used by Kubernetes, TensorFlow, and many other major projects. It's pre-approved at most enterprises and requires no legal review.
- Is qStudio free?
- qStudio has a free tier for individual developers. Pro features (MCP server integration, team collaboration) require a paid subscription. See our pricing page for details.
- Do I need a commercial license?
- No. Apache 2.0 already permits commercial use with no restrictions. There is no separate 'commercial license' to purchase. Build your product, charge your customers, and keep your code. If your organization requires a custom legal agreement or SLA, contact us about Enterprise Support plans.
- What happens if QRunIO shuts down?
- Nothing changes for your applications. The qqq framework is Apache 2.0 licensed and hosted on GitHub. You can fork it, continue using it, and even maintain it yourself. Your code runs on standard Java—no proprietary runtime to worry about. This is the open-source guarantee.
Compliance & Auditing
HIPAA, SOC 2, HITRUST, and regulatory compliance
- Is qqq SOC 2 or HIPAA compliant?
- qqq provides the building blocks for compliance—audit logging, access controls, encryption support, and data isolation. Compliance depends on how you deploy and configure your application. For qRun managed hosting, contact us about our compliance posture.
- Does qqq have audit logging?
- Yes. qqq has comprehensive audit logging built into the core. Every data change can be automatically logged with who, what, when, and before/after values. Audit logs are queryable through the same API as your application data.
- Can qqq help with HITRUST certification?
- qqq provides many controls HITRUST requires—access controls, audit trails, session management, and encryption support. You'll still need to implement organizational policies and undergo assessment, but qqq gives you a strong technical foundation.
- How does qqq handle data encryption?
- qqq supports encryption at rest (via your database) and in transit (TLS). Field-level encryption for sensitive data like SSNs or credit cards can be implemented through custom field behaviors. qRun hosting includes encryption by default.
- Does qqq support data retention policies?
- Yes. You can implement data retention through qqq's process engine—scheduled jobs that archive or purge records based on your policies. Audit logs can be retained separately with their own lifecycle rules.
- Can I get a BAA for HIPAA compliance?
- For qRun managed hosting, contact us about Business Associate Agreements. For self-hosted deployments, you control your infrastructure and BAAs are between you and your hosting provider.
- How does qqq handle access controls for compliance?
- qqq has role-based access control (RBAC) with field-level permissions. You can restrict who sees what data, enforce separation of duties, and audit all access. Permissions are defined in metadata and enforced at the framework level—no way to bypass them.
- Is there a compliance-focused deployment guide?
- Yes. Our documentation includes guides for deploying qqq in regulated environments, covering network security, access controls, logging, and monitoring. Contact us for enterprise consulting on compliance architecture.
Support
Getting help and community resources
- How do I get help with qqq?
- Join our Discord community for free support and discussions. Documentation is at docs.qqq.dev. For priority support, consider our enterprise plans with dedicated channels and SLAs.
- How does enterprise support work?
- Enterprise plans include dedicated support channels, SLAs, custom integrations, and direct access to our engineering team. Contact us to discuss your specific requirements.
- Do you offer training or consulting?
- Yes. We offer workshops, training sessions, and consulting engagements to help teams get up to speed with qqq. Contact us for custom training packages.
- Where can I report bugs or request features?
- Use our GitHub repository (github.com/qrun-io/qqq) to report bugs and request features. Our team actively monitors issues and welcomes community contributions.
Still have questions?
Our community is here to help. Join Discord for real-time support or browse the documentation.