Coming soon
Qbit Console keeps some reserved navigation areas to communicate product direction, but a reserved page does not mean a separate product workflow is operational.
Current preview-only areas
The following Phase 1 surfaces remain Coming soon:
- Qbit-hosted cloud compute or purchasing a server hosted by Qbit;
- a standalone managed-database product outside the Workloads lifecycle;
- a standalone reusable Template catalog outside current Workload sources;
- managed Git-provider account integration;
- backup services;
- managed DNS;
- push-notification services;
- a Qbit-hosted container Registry;
- a hosted npm cache;
- wallet;
- hourly hosting metering.
Workloads are no longer a preview. The merged create, validate, deploy, history/logs, stop/delete, and recovery lifecycle operates on customer-owned remote servers. This documentation currently provides the image-source workflow in Deploy an image workload.
Source choices such as Compose, Git, and database templates that appear inside Workloads belong to the same unified Workload model. Do not confuse those source types with separate preview products such as a managed-database product, Template catalog, or managed Git-provider account integration.
Why are some reserved pages visible?
Reserved pages communicate future information architecture. They must not create fake endpoints, billable resources, or simulated mutations.
Currently operational areas
Use the implemented surfaces for:
- Workspace and membership management;
- remote-server inventory;
- typed remote operations and authorized terminal access;
- passive resource monitoring and retained history;
- resource alerts and operational notification destinations;
- Workloads on customer-owned remote servers;
- read-only billing visibility;
- panel preferences and account sessions.
Do not plan production operations around a Coming soon capability until its real workflow is merged and enabled in the Console.