ODBC, DSN and local agent

Automate ODBC reporting with a local agent and without exposing the database

When the source depends on a DSN, a local driver or an internal network, the local agent makes it possible to run queries from the customer environment and send the result to the platform without publishing the database.

Start free trial See pricing

What this approach adds

Access to hard-to-expose sources

It fits when the database or DSN is only reachable from the customer's private network.

Less security friction

The cloud does not need a public IP for the database to start validating the flow.

Continuity with existing processes

Your team keeps drivers, DSN and access logic where they already work today.

When it fits best

Especially useful when the limitation is not the query but connectivity.

Generic ODBC with a DSN already configured in the customer network.
Legacy software that requires specific local drivers.
Firewall or compliance restrictions that prevent direct cloud access.
Teams that need to validate manually first and scale afterwards.

Frequently asked questions

Does the local agent completely replace opening the firewall?

It avoids exposing the database with a public IP, but your team still needs to allow the agent's outbound traffic to the required endpoints.

Can I schedule reports if the source depends on the agent?

It depends on the connection type and the current product support for that source. Initial validation is precisely how you confirm that point.

More key pages

Link the main areas Google should discover about the product.

Check whether your ODBC source fits with a local agent

Start free trial