April was a busy month for us, especially when it comes to new and expanded integrations. And that’s on top of some exciting new native functionality!

Let’s dive in.

Request access to locked resources

Twingate Usage-based auto-lock policies revoke access if a set usage requirement isn’t met, automatically reducing your attack surface and automating least privilege access. But what if a user needs to re-establish access to a locked Resource?

End users can now request and obtain access directly through Twingate. Incoming access requests can be reviewed in Twingate, via email, or in your preferred channel via webhook.

Watch this short demo video to see access requests in action, or check out the docs page.

DNS filtering enrollment groups

You can now enable Twingate Internet Security for specific groups, making it easy to test new functionality and stagger rollout across your users.

Twingate DNS Filtering automatically detects, flags, and blocks malicious web threats like malware, phishing, cryptojacking, and more.

New and expanded integrations

Investing in native integrations is a critical component of Twingate’s approach to Zero Trust security. Here’s the latest from our integration partnerships:

• Our new integration Coder makes it easy to securely access private resources directly from Coder’s open source dev environments.

• The Twingate Pulumi provider has officially moved from beta to GA.

• We continue to make improvements to our Kubernetes Operator, including making it easier to migrate over to K8s from a different tool.

• The Twingate x JumpCloud integration is now available to self-serve directly in the Admin Console.

More from the Product Team

We’ve got plenty of other features we’re excited to share, plus a peek at some upcoming releases:

• Twingate routing now prioritizes connecting to the closest Connectors geographically, with no action needed from admins besides ensuring Connectors are up-to-date.

• Local peer-to-peer connections enable better performance and throughput when clients and Connectors are on the same network

• [Coming soon] We’re further expanding our AWS S3 integration to enable customers to sync DNS filtering logs to an AWS S3 bucket.

Stay in the know

We’ve always got lots of things cooking over here at Twingate, and the easiest way to stay in the know is to subscribe to our changelog. 

We have a few different feeds, so you can subscribe to whichever fits best for your team:

• What’s new RSS: our biggest new feature releases

• Client RSS: information on the latest Client versions and bug fixes

• Connector RSS: updates and improvements to Twingate Connectors

• API changelog: the latest changes and updates to our GraphQL-based Admin API

Not a Twingate customer yet? If you’re interested in taking Twingate for a spin, you can request a personalized demo from our team or try it out yourself for free.