Choose a use case
Common Use Cases
Choose the right connection model: direct private DNS/IP access with the full client, or one fixed TCP destination on localhost with a wzctl access pass.
Each guide identifies its mode explicitly. The full client installs routes and split DNS for direct private access; wzctl access passes relay one fixed TCP target through 127.0.0.1. Full-client host-and-port granularity requires effective restricted rules.
Private service access without a VPN
Give each person or process the private connection it needs, without publishing the service or defaulting to broad VPN access.
Read use case →AI agent access to a private database
Let an agent use one private database endpoint while database credentials and SQL permissions remain under your control.
Read use case →CI/CD access to private resources
Give each build or deployment job the private connectivity its runner can support, without publishing the destination.
Read use case →Developer access to a private database
Let developers keep their normal database tools and connect to the real private endpoint without publishing the database.
Read use case →Process access to a private API
Give an integration a fixed local path to one private API without adding private routes to its runtime.
Read use case →Restrict remote access to one server
Keep direct private DNS and native tools while limiting a user's network access to one approved server service.
Read use case →Monitor private services without publishing them
Check private services without publishing health endpoints or giving every probe broad access to the surrounding network.
Read use case →SSH access without a broad VPN
Keep port 22 private and use normal SSH commands against the server's real private hostname or IP.
Read use case →Private Kubernetes API access
Keep kubeconfig pointed at the real private control-plane endpoint while WireZTNA supplies the required routes and split DNS.
Read use case →Vendor access to one internal application
Let a vendor use the application's real private address without publishing it or granting access to the surrounding network.
Read use case →European digital sovereignty
Data residency says where systems run. Digital sovereignty also asks who operates them, holds the keys, and can be compelled to provide access.
Read use case →