[Roadmap]
Know what is being built before you depend on it.
Tasmanian Cloud is being built for teams that need to deploy and operate real systems without hiding the difficult parts. This roadmap shows the boundaries we are making explicit and the workflows we are putting behind them.
Access is limited while we develop the platform with early users. Bring us a real workload and we will be clear about what is ready, what is being built, and what remains your responsibility.
API control plane
REST and GraphQL own resource state. The portal, CLI, SDK, and x402-aware machine callers use the same boundary.
VMs and containers
Private virtual machines and container workloads with the access boundary documented for each service.
Saga templates
A stateful template system for VM and container state, Docker Compose, Ansible, and Terraform or OpenTofu work.
Kleis and Dialkeys
Encrypted secret references, service identities, and scoped machine actions without .env sprawl or secret context in AI workflows.
Bastion and zero trust
Mesh-only management traffic, scoped port grants, and an audited path for private services.
Patch reporting
Host and image findings with scan age, severity, remediation state, and customer-selected delivery paths.
Events and delivery
Signed webhooks, an ntfy-compatible notification provider, and an email relay for the systems around the platform.
S3-compatible objects
RustFS-backed object storage with familiar clients, lifecycle controls, versioning, and a Tasmanian data boundary.
Current status: The platform is Tasmanian owned and operated and built on open-source foundations. Availability, support, and service scope depend on the specific private beta workflow.