Access to hard-to-expose sources
It fits when the database or DSN is only reachable from the customer's private network.
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.
You can sign up without a card and validate with a test source when it fits your schedule.
ODBC and the agent are the bridge—link ERP, IBM i and SQL Server as your architecture requires.
It fits when the database or DSN is only reachable from the customer's private network.
The cloud does not need a public IP for the database to start validating the flow.
Your team keeps drivers, DSN and access logic where they already work today.
Especially useful when the limitation is not the query but connectivity.
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.
It depends on the connection type and the current product support for that source. Initial validation is precisely how you confirm that point.
All public pages by use case: they help visitors and search engines see how topics connect—without mixing unrelated products.
Sign up, review connectivity requirements and validate a real case before broadening scope.
If you want to compare quotas and plans before creating an account, use the pricing section on the home page.