Tasmanian Cloud documentation
Bastion access
Scoped access to private services over the zero-trust mesh
The bastion is the access boundary for private management and service ports. It accepts an authenticated connection, checks a scoped grant, and forwards only the permitted port to a private service.
No public management ports
Managed deployments MUST NOT expose SSH, database administration, cluster control, or runner configuration on a public IP. Public application traffic is a separate recipe decision.
Scoped forwarding
A customer or operator can receive a grant for a specific deployment and port. The client can use a local forwarded port while the target keeps its private address. A grant does not provide access to every service on the host.
Mesh plus service authentication
The zero-trust mesh authenticates the peer. The access policy checks the identity and target. The service still performs its own authentication. Joining the mesh is not permission to reach every deployment.
Transport
The overlay uses the shared Bedrock transport and its peer discovery path. Iroh informed the earlier transport design, but the customer-facing promise is the private, authenticated path and the scoped grant, not a public iroh endpoint.