Tasmanian Cloud documentation

Management

Resource state, events, integrations, and operational workflows

Manage resource state and the systems that respond to it. The REST and GraphQL APIs are the control plane. The portal, CLI, SDKs, and x402-aware machine callers are clients of that API surface.

Tools

[Projects](./projects) - Resource organization
[Uptime](./uptime) - Service status and availability tracking
[Events](./events) - Signed state changes and webhooks
[Integrations](./integrations) - Notifications and email relay
[Patch reporting](/docs/infrastructure/patch-reporting) - Package findings and remediation state

Quick Start

API Authentication

export TASMANIAN_CLOUD_API_KEY="your-api-key"

First API call

curl -H "Authorization: Bearer $TASMANIAN_CLOUD_API_KEY" \
  https://api.tasmanian.cloud/v1/compute/vps

Architecture

flowchart LR
    subgraph "Management Tools"
        CLI[CLI Tool]
        API[REST + GraphQL API]
        SDK[SDKs]
    end

    subgraph "Tasmanian Cloud"
        COMPUTE[Compute]
        STORAGE[Storage]
        NETWORK[Networking]
        EVENTS[Events and integrations]
    end

    CLI --> API
    SDK --> API
    API --> COMPUTE
    API --> STORAGE
    API --> NETWORK
    API --> EVENTS

SDKs

Official SDKs available for:

Python - pip install tasmanian-cloud
JavaScript/TypeScript - npm install @tasmanian-cloud/sdk
Go - go get github.com/tasmanian-cloud/sdk-go

Monitoring

Metrics

Resource utilization (CPU, memory, disk)
Network traffic and latency
API request rates and errors
Uptime and availability

Alerts

Configure alerts via:

Webhook notifications
Email alerts
PagerDuty integration
Slack notifications

Project Organization

Organize resources into projects for:

Environment separation (dev/staging/prod)
Team access control
Cost tracking and billing
Resource quotas

# Create a project
tc projects create --name production --description "Production workloads"

# Move resources to project
tc vps move my-server --project production