A clear path from account to reviewed request.

1. Create an account with email and password.
2. Open the Console and review the available account context.
3. Create a project, then open Service Catalog.
4. Choose a product and configure its name, project, region, and plan.
5. Review the summary and save the request.

Saving a request starts review and, where applicable, quotation. It does not deploy automatically and does not charge a payment method.

Create an account →

Services represent resources available to the workspace. Read their state as a current connection and readiness signal, not as a promise that every provider is enabled. “Not connected” means the workspace needs a provider connection before that capability can be evaluated.

Orders and setup requests capture intent: the selected product, configuration, and review context. They are distinct from an active service. A saved request can require review, clarification, or a quote before any implementation begins.

Observability is the operational layer: signals, logs, metrics, health, and evidence around changes. If it is not connected, treat that as a gap to resolve during planning rather than inventing a runtime status.

Integrations determine which infrastructure, regions, and runtime capabilities are available. Verify the connection and scope in the Console before planning around a product.

Keep ownership, access boundaries, secrets, endpoints, backups, and rollback evidence explicit. The UI can organize the request; your team still owns the approval and operational decisions.