Tasmanian Cloud documentation

Compute

VMs, containers, and stateful application deployments

Run the workload in the shape that makes sense for it. Use a VPS when you need a complete machine. Use containers when the application is already split into services. Use Saga when the system needs a repeatable definition across compute, Compose, and infrastructure tooling.

Compute paths

PathUse it forControl surface
VPSFull VM, root access, custom operating systemREST API via portal, CLI, or SDK
ContainersServices that already have a container shapeREST API via portal or client
Saga templatesVM, container, Compose, Ansible, and IaC stateREST API via template, CLI, or SDK

One API, several clients

flowchart LR
    PORTAL[Portal]
    CLI[CLI]
    API[REST API]
    SDK[SDK]
    INTENT[Intent]
    RUNTIME[Runtime]
    STATE[Verified state]

    PORTAL --> INTENT
    CLI --> INTENT
    API --> INTENT
    SDK --> INTENT
    INTENT --> RUNTIME --> STATE

Keep access private

Compute resources use the private networking model by default. Read the VPN guide before you publish a service or expose an administrative port.

Next steps