Infrastructure Access

Twingate enables engineers and DevOps to manage and automate secure access to technical infrastructure, both on-premises and in the cloud.

Benefits of using Twingate for securing access to infrastructure

  • Enhanced security. Twingate enables secure access to infrastructure without requiring anything to be publicly exposed on the internet via a jump server, Bastion host, or other endpoint. Twingate allows networks to remain hidden from the internet while allowing access to authorized users and services.
  • Fast deployment. Twingate can be deployed in under 15 minutes with a lightweight connector component, deployed on a single host within a network. No network reconfiguration or VPN server setup is required.
  • Programmatic configuration. Twingate supports Terraform and Pulumi and offers an Admin API to automate management of Twingate and access controls.
  • Granular permissions. Define access to individual resources with custom policies and groups, enabling a least privilege approach to access permissions.
  • Enable CI/CD workflows. Define narrow access permissions to internal infrastructure for automated services (e.g. Jenkins, CircleCI) hosted in the cloud.
  • Unified access. Easily access multiple clouds or multiple environments (e.g. development and staging) at the same time.
  • Works with Kubernetes. Twingate can be deployed in Google Kubernetes Engine (GKE), Amazon EKS, and similar Kubernetes and microK8s deployments to address various use cases. The Twingate Kubernetes Operator provides seamless integration between your Kubernetes clusters and the Twingate Zero Trust Network.

Guides for using TWingate to secure infrastructure

Automating configuration with Twingate

Securing CI/CD workflows

Using Twingate with Kubernetes

Securing development environments

Last updated 3 days ago