> This page is for Home.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.emnify.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.emnify.com/_mcp/server.

> Overview and setup

emnify's communication platform hosts an OpenVPN service that allows you to establish a private network between a device and any remote client location.
The remote client can be on the application server or any machine that wants to access the device remotely (such as operational staff).

## IoT device requirements

Your IoT device doesn't need a private APN, OpenVPN software, or dynamic DNS resolution to use the OpenVPN service.
Through the emnify SIM, each device has a [static](https://www.emnify.com/iot-glossary#static-ip) [private IP address](https://www.emnify.com/iot-glossary#private-ip) that you can use to identify and address the device.

At the same time, the IoT device can send data through the private tunnel to the IP address of the remote machine.

> **Note**
>
> End-to-end connectivity only works between devices and OpenVPN clients configured in the same region.
> When downloading the configuration file for your OpenVPN client, select the region that matches the breakout region configured in the device's service policy.

> **Warning**
>
> Don't use automatic breakout region selection for devices reached over OpenVPN.
> A policy set to automatic selection can send a device to a different region at any time, which breaks the tunnel.
> Use a fixed region instead.
> See [Set the breakout region](/portal/how-tos/set-breakout-region).

> **Warning**
>
> Because OpenVPN relies on a single tunnel, service restarts cause short interruptions.
> For critical data traffic, use [Cloud Connect VPN](/services/cloud-connect).

## Available guides

* [Linux](/developers/integrations/openvpn-linux-ubuntu)
* [macOS](/developers/integrations/openvpn-macos)
* [Windows](/developers/integrations/openvpn-windows)