[Articles]
Notes for teams that have to live with the decision.
Clear explanations of the control plane, private access, deployment state, secrets, patch findings, and the systems around Tasmanian Cloud.
[ALL ARTICLES]
The API is the control plane
REST, GraphQL, the portal, CLI, SDKs, and x402-aware callers meet the same API-owned resource state.
Read noteSagaTemplates 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.
Read noteKleisSecrets 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.
Read noteEventsEvents are part of the product
Resource changes become signed events so your systems can react without polling every endpoint forever.
Read noteIntegrationsOne event, the delivery path you choose
Route infrastructure events to an ntfy-compatible provider, an email relay, a webhook, or your own application.
Read noteIdentityDialkeys replace configuration sprawl
Give services a stable identity for discovery and derived configuration without making every deployment a hand-written .env file.
Read noteAccessThe bastion is the boundary
Reach private services through an authenticated, scoped forwarding path instead of publishing management ports to the internet.
Read noteNetworkingPrivate by default
VPN-only access, transparent layer 4 routing, and why workloads do not need a public address.
Read noteOperationsPatch reports belong in the control plane
Turn package state into a customer-readable report with age, severity, remediation status, and delivery paths.
Read noteArchitectureSovereignty is an architecture constraint
What local ownership changes about the public edge, private workloads, and operator access.
Read noteStorageS3 compatibility without moving the boundary
Use familiar object APIs while the storage plane remains hosted in Tasmania.
Read noteArchitectureA cloud exit plan starts before the exit
Reduce hyperscaler lock-in by keeping data, identity, networking, and deployment state portable before you need to move.
Read noteSecurityDark web monitoring is a signal, not a breach decision
What leaked credentials and dark web findings can tell you, and why they do not by themselves decide whether an Australian data breach is notifiable.
Read noteMigrationCloud migration without a big-bang cutover
A practical migration sequence for teams moving a workload while keeping its state, access paths, and rollback visible.
Read noteSovereigntyPrivate 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.
Read note