Tasmanian Cloud documentation

Security boundary

Zero-trust access, scoped capabilities, and patch evidence

The security model is based on boundaries that can be checked in a workflow. Management traffic is private. Access is identity-scoped. Sensitive values remain references until an authorised machine needs to use them.

Private management

The platform MUST NOT publish normal SSH, database administration, or operator interfaces on a public management address. Use the zero-trust mesh and a scoped bastion grant.

Scoped actions

The API and workflow carry the identity, tenant, resource, and action that a caller is requesting. The resulting decision can be attached to the deployment run and its audit event.

Secret references

Kleis can hold encrypted references for provider credentials, webhook keys, mail configuration, and application inputs. Dialkeys provide service identity and discovery without turning every relationship into a copied .env value.

Patch evidence

Patch reports show observed package state, scan age, severity, and remediation state. A customer can read findings through the API and send them to a webhook, email relay, or ntfy-compatible notification provider.

What this page does not claim