Guide · Connection
There are two routes. The local agent route opens no ports: the connection always leaves your network outbound, never the other way round.
If the database lives in your network, on your own server or behind a firewall you would rather not touch.
If the database is already reachable from outside: a managed cloud database or hosting with a public IP.
Four steps. The longest one is deciding which machine to install it on.
Inside Sapioverse, under Connections → Gateway. The token identifies that agent and belongs to your organization: nobody outside it can use it.
There are builds for Windows, macOS and Linux. If your policy is not to run third-party binaries, you can download the Python script and review it first.
Install it on a machine in your network that can already see the database. You give it the engine, host, port and a read-only user. Those credentials stay on that machine.
The agent shows up as connected. From there you create the connection by choosing that gateway and the schema syncs just like any other.
None of what usually stalls these projects in the meeting with IT.
Opening ports in the firewall
Publishing the database on the internet
Paying for a static IP or setting up a VPN
Copying or moving the data somewhere else
The same by both routes, because the connector is per database engine, not per ERP.
One detail worth knowing before you start: SQL Server through the agent needs Microsoft's ODBC driver (msodbcsql18) on the machine running the agent. It is Microsoft's and is installed separately. The other engines need nothing external.
If your IT team would rather not do the first connection alone, we do it together on a call. And if what you need is the security questions, they are answered separately.