Feature Availability and Release Status
Use these labels when communicating with users.
| Label | Meaning |
|---|---|
| Core | Expected on a current standard NuQloud installation |
| Provider-enabled | Implemented but depends on provider configuration, credentials, policy, or package |
| Preview | Usable early surface with explicitly limited behavior |
| Foundation | Supporting UI or architecture exists, but the full protocol/workflow is not complete |
| Deprecated | Kept only for compatibility or reference and should not be enabled for normal use |
Current examples
- Dashboard, guides, Files, Talk, PWA, linked accounts, and Decentralized Apps: core, subject to account permissions.
- Billing catalog, Managed Recovery, NuQloud AI, Scrum, foreign coins, Master Calendar, and advanced branding: provider-enabled.
- Q-Chat through a matching Qortal Hub and External Auth installation: provider-enabled. The shared group-chat interface is implemented; live peer interoperability still needs acceptance on the provider's deployment.
- NuQloud Commerce: provider-enabled, with registered application-specific payment contracts. A configured connection does not enable every consumer.
- Standard Appointments scheduling: provider-enabled and subject to staging access. SHEF paid booking is a test workflow; live checkout remains blocked.
- NuQloud World: preview.
- NuQloud Computer: private testing prototype, including its staging-gated cloud companion; not a generally available hosted computer service.
- Federation Registry: provider-enabled / evolving. QDN discovery, publication, opt-in profiles, and authority checks are implemented in source; remaining hardening and live interoperability must not be presented as complete.
- Legacy direct Q-Chat/Talk relay: deprecated. This is distinct from the current optional Q-Chat group interface.
These examples were checked against source on October 29, 2026. Source availability is not confirmation that a particular provider has deployed it. See the October update for the review scope.
Update this page whenever a feature changes status. Avoid promising activation dates unless they have been approved publicly.