You can now register servers and VMs as SSH Resources in Twingate. Users can connect to these Resources using their existing tools and authenticate with their identity provider. Admins no longer have to manage SSH keys or distribute them to users. The Twingate Gateway handles certificate-based authentication to the target server and records every session to stdout in asciicast format, ready to forward to your SIEM or to replay for audit purposes. With Privileged Access via the Twingate Identity Firewall, you can eliminate credential sprawl and the need for bastion hosts, all without changing your developers' workflows.For more information, see our documentation.

Gain more visibility into your network with our new Authentication Audit Logs. You can now troubleshoot connection issues by exporting and syncing success and failure event data for each Client login, Resource access attempt, MFA setup, and more. These granular insights eliminate blind spots, allowing your team to resolve user hurdles faster while maintaining a robust audit trail for security compliance.For more information, see our documentation.

You can now edit API keys after they are created to rename them, modify their associated permissions, and disable/enable them. These new capabilities provide developers with crucial flexibility, allowing for quick post-creation modifications and the ability to temporarily pause keys without needing to generate new ones. This streamlines workflows and improves security management.For more information, see our documentation.

The Admin Console now supports more complex search options across key elements like users, Resources, and devices. Users can now perform searches using multiple terms, or by wrapping specific phrases in double quotation marks (e.g., "Grafana Dashboard"). This feature allows admins to quickly and accurately find what they need, whether through a broad, general search or a highly specific, exact-match search.

We now make available summaries of network health as a downloadable reports. These summaries provide metrics like data transferred and errors over specified timeframes, giving admins better insight into network performance. Additionally, existing active user reports have been extended to provide similar data points on a per-user level, making it easier for admins to proactively monitor the health of their networks and efficiently troubleshoot issues.For more information, see our documentation.

The Twingate Linux Client now features a userspace networking mode that eliminates the need for the Client to run with root access or elevated privileges. By using the new HTTP Proxy Mode, users can securely connect to Twingate-protected resources using standard HTTP/HTTPS connections, even in restricted or headless environments. This enables DevOps to seamlessly integrate Twingate into CI/CD pipelines, Docker containers, and developer workstations where admin access is typically unavailable, drastically simplifying deployment.For more information, see our documentation.

With the introduction of Connector metrics, Admins now have more visibility into network performance when using Twingate. These metrics allow monitoring of traffic patterns and connection efficiency using real-time data exported in the industry-standard Prometheus format. This lets admins proactively manage network health and troubleshoot connectivity issues by easily integrating Twingate data into existing monitoring tools.For more information, see our documentation.

JIT Access Requests may now be reviewed and approved by users in designated Groups on a per-Resource basis. Admins may configure one or more Groups as Resource Approvers for any Resource, allowing delegation of Access Requests to non-Admin users. This provides more flexibility by allowing teams to manage access for the Resources they own, while not having full Admin privileges.For more information, see our documentation.

Admins may now configure just-in-time workflows for providing Twingate users with on-demand access to Resources. These users may be granted time-limited access to Resources for between 1 hour and 7 days. Approval can either be required from an Admin or auto-approved for auditing purposes. This JIT workflow is ideal for controlling and auditing access to sensitive Resources, such as in a "break glass" protocol for incident response.For more information, see our documentation.

Twingate Clients now support signing into multiple accounts at once, even if those accounts are on different networks. This makes it simpler to manage use cases such as switching between your home and work accounts, or admin accounts for different networks. You can even pause the connection on an existing account without having to log out or quit.This feature is currently supported on macOS, iOS, and Windows Clients. Android and Linux support will be rolled out shortly.For more information, see our documentation.

The Twingate Admin Console now supports dark mode. The console will automatically match your device's system settings, or you can manually choose to enable light mode or dark mode. This update offers a more comfortable viewing experience, especially in low-light environments.

Event feeds in the Admin Console now support filtering by date, Resource, user, and activity type. This allows you to quickly find specific events when troubleshooting issues or analyzing activity patterns across your network.For more information, see our documentation.

Twingate notifications are now more flexible, giving you granular control over how and where alerts are delivered. You can choose which admins receive specific emails and set up webhooks to support custom workflows - perfect for staying on top of events like Connector updates, integration errors, and service account key expirations.For more information, see our documentation.

You can now configure multiple identity providers and sign-in options for your Twingate Network. This allows you to mix and match social logins and supported IdPs to create the setup that works best for your team - ideal for handling complex environments and situations like migrations, acquisitions, subsidiaries, and third-party contractors.For more information, see our documentation.

Twingate Privileged Access for Kubernetes enables secure, auditable access to your most sensitive infrastructure with greater ease, visibility, and control. By extending Zero Trust principles beyond the initial network connection to include specific Kubernetes operations, this product allows organizations to enforce least-privilege access at the application layer.For more information, see our documentation.

Our Kubernetes Operator is now generally available. The operator allows you to define and manage Twingate Resources and access authorizations directly from your Kubernetes deployment, ensuring that configuration and access to your cluster are maintained in the same place. For more information, see the Github project page.

Resources now support tags, which are key-value pairs used to add metadata for better organization and management. With tags, you can label Resources with important details like their owner, location, or purpose, making it easy to categorize and manage them. You can also filter Resources by their tags in the Admin Console or API, allowing for quick and efficient searching.For more information, including suggestions on how to use tags, read our documentation.

The Twingate Client can now proactively notify end users when their sessions are about to expire, giving them the opportunity to reauthenticate without their session being interrupted. This is ideal for long-running workflows, like SSH, using remote desktop, or downloading large files. This feature is in early access, reach out to have it enabled.To learn more and learn how to opt in, read our documentation.

Automatically locking Resource access due to inactivity is a great way to automate least-privilege access through Twingate. We've now extended this capability to allow user access requests for auto-locked Resources to be automatically approved. Admins still get notified of when and why users are accessing sensitive Resources, which provides the visibility and auditing that admins need around access while not adding a waiting period for their end users.For more information, check out our documentation.

The Admin Console now provides quick access to key resources that help you to set up and manage Twingate even more effortlessly. You can easily search documentation, access the latest changelog entries, sign up for an onboarding workshop, and more.

You can now restrict access to Resources based on a device’s location. Block or allow access from a list of countries that you specify in a Resource policy. Devices that do not meet these location requirements (based on their geolocated IP address) will be prevented from accessing the relevant Resource, strengthening your security posture.For more information, see our documentation.

Twingate is excited to announce that Browser Security is now in beta! Browser Security allows admins to limit which browsers can access sensitive Resources and to apply enterprise application controls. These controls restrict what actions end users are allowed to take on sensitive Resources.Browser Security is available for Chrome browsers on macOS and Windows. To learn more, read our documentation.

You can now select which Groups are able to use Exit Networks. This is useful if you only want a subset of your users to be able to route traffic through Exit Networks, for reasons such as business need or bandwidth use management.To learn more, read our documentation.

You can now specify the minimum OS versions that can access your Resources to enforce stricter device security postures. A minimum OS version can be set as a minimum authorization and/or Trusted profile requirement for macOS, Windows, and iOS devices. For more information, see our documentation.

Signed out devices using DNS filtering will now send their hostname and device information to Twingate. Our logs will now match signed out devices with a previously signed in device or, if one cannot be found, will surface the device's hostname. This makes it easier for admins to keep track of which devices are using DNS filtering, especially when the devices are signed out.To learn more, read our documentation.