Every system DataForge connects to
Sources and destinations, on-premises and in the cloud. Each entry shows how DataForge reaches it: a connection you configure in DataForge, the database the application runs on, or its API with the DataForge SDK. A destination is a system DataForge writes results back to, which other tools sell as reverse ETL. Select a system to see the details.
That system is not on this page yet.
If you can reach its database with a JDBC driver, DataForge reads it with a Generic JDBC connection. If it has a documented API, DataForge reads it with the DataForge SDK. Book a demo and bring the system name.
Three ways to connect
How DataForge reaches each system
You configure each connection in DataForge, with its own credentials. Every source feeds governed tables in your account, and every output reads from them. Each card is labeled with its path.
-
01 Configured
A connection type in the DataForge UI. Pick it from the list, enter the credentials, and schedule the pull. It runs through the Outcrop agent inside your network, or directly from the DataForge platform without the agent.
-
02 Database
DataForge connects to the database this application runs on, with a Table connection and the bundled driver or a Generic JDBC connection and the vendor’s driver. It reads the tables, keys and relationships and creates the sources for you.
-
03 API
A short notebook in your Databricks or Snowflake account, built with the DataForge SDK, calls the API and hands DataForge the rows. The SDK handles the process lifecycle, logging, credentials and the incremental watermark.
Bring the systems you run
Tell us the systems your business runs on and where they are, and we will show you how DataForge connects to each one.