> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rwsintegration.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Network Connectivity

> RWS reaches any system, anywhere: public, firewalled or on a private network

## Any system, anywhere

RWS integrations and [RWS Connect](/en/core-concepts/rws-connect) pipelines reach the systems they extract from and load to regardless of where those systems run, and regardless of whose they are: your own, your customer's, or any third party's. Where a system lives never decides whether it can be integrated. It only decides how the connection is set up.

## Three ways to reach a system

| Where the system is      | How RWS connects                                          |
| ------------------------ | --------------------------------------------------------- |
| **Public internet**      | Directly. Nothing to configure.                           |
| **Behind a firewall**    | The firewall allowlists RWS's three fixed IP addresses.   |
| **On a private network** | A VPN between RWS and the network where the system lives. |

### Fixed IP addresses

All RWS traffic originates from three fixed IP addresses:

```
80.254.212.213
52.44.32.53
52.86.32.5
```

When a source is protected by a firewall but does not require a VPN, allowlisting these three IPs is enough to grant access.

### VPN

RWS supports **IPSec (site-to-site)** and **OpenVPN**. Tunnels are outbound only: only RWS gains access to the network, never the reverse. Setup is requested by email to [connect@rwsintegration.com](mailto:connect@rwsintegration.com) and takes two business days after the required information is provided by whoever manages the network, whether that is your team or your customer's. See [VPN Connectivity](/en/features/connections/vpn) for the step by step and what to send.

## Everything works the same

Once connectivity is set up, the platform behaves identically for every system: the **Extract Preview** panel, integration runs, schedules and monitoring all work exactly as they do with publicly reachable sources.

## Next steps

<CardGroup cols={2}>
  <Card title="VPN Connectivity" icon="shield-halved" href="/en/features/connections/vpn">
    Supported VPN types, what to provide and setup time
  </Card>

  <Card title="RWS Connect" icon="plug-circle-bolt" href="/en/core-concepts/rws-connect">
    Extract from SOAP APIs, databases and files
  </Card>
</CardGroup>