[100% Tasmanian owned and operated]
Run your infrastructure somewhere you can account for.
Public management ports, copied credentials, and provider consoles make infrastructure hard to explain when something goes wrong. Tasmanian Cloud gives you a private, locally operated path to run VMs, containers, storage, and the systems around them.
[A calmer operating model]
Infrastructure should not become a second job. Keep the boundary clear.
When a deployment is spread across scripts, dashboards, shell history, and undocumented access paths, every change creates more uncertainty. Tasmanian Cloud puts intent, execution, access, secrets, and evidence into a system your team can inspect and reuse.
[Core product]
When something changes, you should be able to explain it.
Deploy a resource, compose an application, or reconcile a larger system. The control plane keeps the request, the work, the access decision, the events, patch findings, and verified state connected.
Explore the platform ↗[What we are building]
Stop stitching together five consoles
Use one API-owned view of resources, runs, events, and findings. Start in the portal, then move the same workflow into a CLI, SDK, REST, or GraphQL client.
Read the note ↗[Saga]Know what a failed change left behind
Describe the VM, container, Compose, Ansible, and OpenTofu work together, then keep the plan, steps, outputs, and recovery path attached to the run.
Read the note ↗[Kleis + Dialkeys]Stop passing secrets around
Give services a stable identity and keep sensitive values behind scoped expressions instead of copying them through templates, shell history, or AI context.
Read the note ↗[Private access]Keep management off the public internet
Reach private services through a zero-trust mesh and scoped bastion grants. Make application exposure deliberate instead of accidental.
Read the note ↗[Operations]Know which packages need attention
Turn host and image findings into useful state, then send the right signal through webhooks, email, or an ntfy-compatible notification provider.
Read the note ↗[Frequently asked questions]
What risk does Tasmanian Cloud remove?+
The platform is designed to keep management traffic private, keep sensitive configuration out of copied files, and show what happened during a deployment. It does not make risk disappear, but it gives you a clearer boundary and a more useful record when something changes.
Will this fit the way we already work?+
You can start with the portal, automate through the CLI, integrate with an SDK, or call the REST and GraphQL APIs directly. Those clients use the same control plane, so moving from a person to a pipeline does not create a second source of truth. x402-aware callers can use the payment path where a service enables it.
What can I run?+
Tasmanian Cloud is for virtual machines, containers, Docker Compose applications, S3-compatible storage, and the systems around them. Saga templates can combine those pieces with Ansible and Terraform or OpenTofu work.
What happens when a deployment fails?+
Saga records the plan, the work that ran, the result of each step, and the compensation or retry decision. You can see what changed and where the run stopped instead of receiving one opaque failure message.
How are secrets and service connections handled?+
Dialkeys give services a stable identity for discovery and derived configuration. Kleis keeps sensitive values behind encrypted references and scoped expressions, so credentials do not need to travel through templates, logs, shared `.env` files, or AI context windows.
How do private services work?+
Management traffic stays on a zero-trust mesh. A bastion can forward a specifically granted private port without publishing SSH or database administration to the internet. Application exposure is an explicit recipe choice.
Do you provide patch reporting?+
The platform is designed to report host and image package findings with scan age, severity, remediation state, and delivery through the API, webhooks, email, or an ntfy-compatible notification provider.
Where is my data hosted?+
Tasmanian Cloud is 100% Tasmanian owned and operated. The platform is designed around local hosting in Tasmania and Australian jurisdiction. Current service boundaries and provider dependencies are documented for each service.
[Articles]
The API is the control plane
REST, GraphQL, the portal, CLI, SDKs, and x402-aware callers meet the same API-owned resource state.
SagaTemplates that describe a running system
Define VM and container state, Docker Compose state, and the Ansible or Terraform/OpenTofu work that makes the state real.
KleisSecrets without handing them to the model
Keep secret material encrypted and use scoped expressions so machines can act without leaking credentials into templates, logs, or AI context.
EventsEvents are part of the product
Resource changes become signed events so your systems can react without polling every endpoint forever.
[Private beta]
Bring us the workload you are tired of explaining.
Tell us what you want to run, what must stay private, and where the current workflow creates risk. We will show you how the pieces fit together.
Start the conversation →