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 Get started

Help and guides

Get started

Sign in, choose your organization, and find your services.

Before you start

You need a Thora Cloud account with access to an organization.

Steps

  1. Open the dashboard and sign in.
  2. Use the organization switcher to choose your workspace.
  3. Open Sites, Domains, Storage, or Compute to see the services available in that workspace.
  4. Open an existing resource and check its status before making a change.

What to expect

You can see the selected organization and its resources. Viewing them does not publish a site or start a purchase.

If something goes wrong

If an organization or resource is missing, confirm the selected workspace. Ask an organization administrator to check your membership if it is still missing.

Technical reference

Before connecting

  • Use a direct organization membership. Delegated professional access cannot issue or use developer credentials.
  • Choose the smallest scope set and shortest practical expiry. Write scopes require a current organization administrator.
  • Keep the credential in an operating-system secret store or protected environment input. Never commit it or paste it into a prompt.
  • During beta, verify the endpoint and capability availability shown by the dashboard before planning mutations.

Make the first read

The inventory response is the safest starting point because it binds profile, organization, authorization, and a bounded resource summary in one read.

PowerShellpowershell
$env:THORA_CLOUD_TOKEN = (Get-Content -Raw -LiteralPath $env:THORA_TOKEN_FILE).Trim()
npm run cloud -- inventory
HTTPSbash
curl --fail-with-body --silent --show-error \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $THORA_CLOUD_TOKEN" \
  https://beta.thora.cloud/api/management/inventory

Plan the first change

  1. Read the target resource immediately before changing it.
  2. Check the returned role, scopes, availability, limits, and current version or revision.
  3. Generate one stable idempotency key for the intended operation.
  4. Submit the smallest exact request. Do not include tenant, host, provider, approval, or credential fields.
  5. If a proposal is returned, stop and direct the organization administrator to the dashboard.
  6. After approval, poll recorded state with bounded backoff and verify the intended external outcome separately.