Direct connection — IP allowlist

Not available yet. Elglide does not publish a fixed set of egress IPs today. Our connectors run on shared cloud infrastructure whose outbound addresses change when we deploy, so an allowlist built on them would stop working without warning — we would rather not hand your security team a rule that silently expires. Use the hybrid agent (it dials out from inside your network, so your firewall needs no inbound rule at all and your data never transits our cloud) or an SSH bastion. If direct allowlisting is a requirement for you, tell us — that is what triggers the work.

What this page describes is how a direct connection works once we publish a stable list. We always initiate the connection outbound from us to your database host, SFTP server or API, so there are no inbound rules on our side for your team to manage.

Where the IPs will live. When we publish a fixed list, it will be shown to signed-in tenants at Help → IP allowlist in the portal — filtered to your tenant's home region, with one-click copy and a containing CIDR. The list will live there rather than on this public page, so it reflects your account's region. Until then that page says the same thing this note does.

When to use it

Your firewall can allow inbound connections to your database, SFTP server or API from a small set of Elglide IPs — once we publish one.
You'd rather not stand up an SSH bastion or run an in-network agent.
You're evaluating Elglide and want the quickest path to a first successful sync.

What you'll need to allow

A single firewall rule for your source host:

Source: our egress IPs — not published yet, see the notice above.
Destination port: your source's listening port — e.g. 1433 for SQL Server, 5432 for PostgreSQL, 3306 for MySQL / MariaDB, 1521 for Oracle, 22 for an SFTP server, 443 for a REST API.

A network file share (SMB) or a folder on a server is never reached directly — those are read only by an in-network agent.

Because we always initiate the TCP connection, you do not need to open any inbound ports toward Elglide. The same egress IPs apply whether you connect directly or through an SSH bastion.

Change notice

There is no published list to give notice about yet. When we publish one, it will be backed by dedicated static addresses and we will commit to 30 days' notice before any change, with the portal page showing the date it last changed.

Set up the connection

Once your firewall allows our IPs, create the source from Connections (sign-in required) → Edit / Create, leave Connectivity set to Direct, and click Test Connection (for a database: network → database → permissions).

Can't allowlist our IPs? Connect through an SSH bastion, or keep source data entirely on your LAN with the in-network hybrid agent.