Tasmanian Cloud documentation

Getting Started

Build and operate private infrastructure from Tasmania

If you need to run infrastructure without losing track of who can reach it, what changed, or where a secret went, start here. Tasmanian Cloud is a local control plane for compute, containers, storage, private access, and the workflows that connect them.

Choose how you work

The REST and GraphQL APIs are the control plane. The portal, the tc CLI, SDKs, and x402-aware machine callers use the same state. Pick the client that matches the person, pipeline, or application that owns the change.

  • Use the portal when you want to inspect resources and runs visually.
  • Use the CLI for scripts, release jobs, and local operations.
  • Use the API when another service owns the workflow.
  • Use an SDK when infrastructure is part of your application.
  • Use GraphQL when a client needs related resource state in one query.
  • Use x402 when an enabled machine-facing operation needs payment admission.

Start with the part that is making you uneasy

The operating boundary

Tasmanian Cloud is 100% Tasmanian owned and operated. Services are designed around local hosting, private access, open-source foundations, and clear boundaries between customer intent, platform execution, and provider state.

There is no blanket claim here of an SLA, ISO certification, or 24/7 support service. Read the service documentation for the current scope of each feature.

The platform in one view

flowchart LR
    HUMAN[Portal client]
    SCRIPT[CLI client]
    SYSTEM[SDK client]
    API[REST + GraphQL APIs]
    PAY[x402 payment admission]
    INTENT[Deployment intent]
    SAGA[Saga runtime]
    KLEIS[Kleis references]
    STATE[Verified resource state]

    HUMAN --> API
    SCRIPT --> API
    SYSTEM --> API
    PAY --> API
    API --> INTENT --> SAGA
    SAGA --> KLEIS
    SAGA --> STATE

Read next