Thora Cloud
A direct line to Thora

Start a conversation

What can we help make simpler?

Tell us what you need. A real person will point you to the right place.

Email Thorahello@thora.cloudExplore SupportSee the available support paths
Browse docs Use your dashboard

Help and guides

Use your dashboard

Find a resource, check its status, and follow changes through to completion.

Before you start

Sign in and select the organization that owns the resource.

Steps

  1. Choose the product you want to manage.
  2. Open the resource to view its details and current status.
  3. Read the proposed change and any approval message before submitting it.
  4. Return to the resource to check the result. A pending request has not finished yet.

What to expect

The dashboard shows the current resource status and any action that still needs your attention.

If something goes wrong

If a change is waiting, failed, or needs recovery, read its message before trying again. A page refresh does not approve or restart the change.

Technical reference

Read the canvas

The canvas is a visualization of persisted organization resources, not a separate control plane. Resources created through the API, CLI, or MCP should appear in the same dashboard context.

Connections describe purpose: a domain routes visitors, a repository feeds a build, a build produces an immutable release, a release runs on a target, and an application depends on data services. A connection is not automatically a health assertion.

  • Proposed: waiting for a decision.
  • Provisioning or deploying: work is in progress and may still fail.
  • Ready or live: the control plane recorded success for the named resource or release.
  • Degraded, uncertain, or recovery required: stop creating follow-on work and inspect the recorded evidence.

Use product-owned approval dialogs

High-impact decisions show the exact target, operation, digest or version, and expiry. Review those values rather than approving from an agent summary. Closing a dialog changes nothing.

Organization-specific layout

A useful canvas reflects the customer's actual topology instead of forcing every organization into the same cards. An agent may suggest labels, grouping, and placement, but the server-owned resource graph remains authoritative and layout metadata cannot create authority or hide unhealthy resources.

  • Keep resource identity and status visible regardless of layout.
  • Preserve keyboard order and readable mobile stacking.
  • Do not let presentation changes alter dependency, ownership, or approval records.
  • Keep draft and live releases visually distinct.