Reverse Proxy for Gateway Agents

Hello @Lars

Just to clarify the use case: is the goal to install an Agent at a customer or remote site, have it establish an outbound connection to Gateway, and then let Gateway route sessions through that Agent to private resources behind it?

In other words, are you referring to something like a remote-site outbound connector or tunnel? Something that would allow you to use a central Devolutions Gateway to manage access to many internal networks behind Devolutions Agents?

Best regards,

Hello @Benoit Cortier

As we understood the Gateway is a way to connect to servers and services on edge networks without VPN.

But we do requiere those connections to be on-demand and the protection a reverse proxy offers.

I see you support 3- party Reverse Proxy Solutions, but this another layer of complexity to the solution.

the addition of a native Reverse Proxy in the Gateway solution would make it a viable option for us to make use of.

A typical example of a use case for us would be to connect to a server (RDP) or a service (SSH/HTTPS) at a customer location. Today we use VPN for this.

But we're looking into a way to do this simpler and more secure.

What we want would be the option to deploying one Reverse Proxy Agent that would handle incoming network connections to the different servers in that given network. (RDP, SSH, HTTPS etc).

Allowing only connections coming from our Public IP.

Thanks, that helps.

I want to make sure I’m really understanding your request correctly.

You are asking for a native site connector / outbound tunnel capability in Devolutions Gateway, where a component deployed inside the customer network would:

• establish an outbound connection to Gateway, simplifying network configuration at the customer site,

• allow Gateway to securely relay RDP / SSH / HTTPS connections to internal systems behind it,

• and do this without requiring a separate third-party reverse proxy or VPN solution such as Cloudflare tunnel or Ngrok.

If that is what you mean, then I believe I understand the use case correctly.

I’m also glad to let you know that we are currently experimenting with such a feature and have already made good progress. It is currently planned for v2026.2 on our roadmap.

I’ll attach the ticket to this thread.

Best regards,

Correct, that is what we are looking for in functionallity.

Of course with central mangement of these Gateway agents, so we can bulk update them from the Gateway server.

Glad to hear that, do you have a timeframe for when v2026.2 will be available?

Thanks, we'll keep our eyes peeled!