Infrastructure

Infrastructure is easier to trust when the boundary is visible. Tasmanian Cloud is 100% Tasmanian owned and operated, with private access, local operation, and explicit resource state as design constraints.

Platform layers

flowchart TB
    API[REST + GraphQL APIs]
    CLIENTS[Portal, CLI, SDK, x402 clients]
    RUNTIME[Saga runtime]
    COMPUTE[VMs and containers]
    STORAGE[RustFS S3 storage]
    NETWORK[Private networking]
    SECRETS[Kleis references]
    ACCESS[Bastion and zero trust]
    PATCH[Patch findings]
    EVENTS[Webhooks and delivery providers]

    CLIENTS --> API --> RUNTIME
    RUNTIME --> COMPUTE
    RUNTIME --> STORAGE
    RUNTIME --> NETWORK
    RUNTIME --> SECRETS
    RUNTIME --> ACCESS
    RUNTIME --> PATCH
    RUNTIME --> EVENTS

Read the boundary before you deploy

• Architecture explains the public edge, private plane, and operator mesh.
• Security services explains current controls and data handling.
• Kleis expressions explains encrypted secret references and scoped use.
• Object storage explains the S3-compatible storage plane.
• Monitoring explains the operational signals we are building.
• Patch reporting explains package findings and remediation signals.
• Bastion access explains scoped private forwarding.

Know what remains yours

Tasmanian Cloud provides the hosting boundary, network primitives, platform runtime, and service interfaces. Customers remain responsible for the guest operating system, application configuration, data, and access decisions inside their workloads.

The exact boundary depends on the service. Read the service guide before treating a platform feature as a managed application control.