Sovereignty / Tasmanian Cloud
Private cloud is an operating boundary
What to ask when you need Australian cloud infrastructure, private access, and a clear answer about who operates the boundary.
Private does not mean invisible
A private cloud is not defined by a marketing label or by whether a server sits behind a firewall. It is an operating boundary: who can access the control plane, where workloads and data are handled, how networks are exposed, and which external providers are dependencies.
Those questions matter for Australian organisations comparing public cloud, hosted private infrastructure, and self-managed systems.
Ask where the management path runs
The management path often decides more than the workload path. It includes identity, provisioning, logs, backups, patch findings, support access, and the services that can change a running system.
A customer should be able to identify that path, understand which access is private, and see how a temporary operator grant is issued and revoked.
Keep application exposure deliberate
Private access by default means a VM, container, database, or operator interface does not receive a public address only because it was provisioned. A recipe can declare an application route public when needed, while management traffic remains behind the mesh or a scoped bastion.
This is an architectural choice, not a claim that private networking removes every security obligation.
Local ownership is useful when it is real
Tasmanian Cloud is 100% Tasmanian owned and operated. That gives customers a direct local operating relationship and a clear place to ask where the platform boundary starts and stops.
It does not mean every workload is automatically compliant, every risk disappears, or every service has the same support or availability terms. Those details must be stated for the actual service and agreement.
Need the implementation details?
Read the Tasmanian Cloud documentation ↗