Data source not in the catalog? Here is how to connect it without waiting for a vendor roadmap
Erathos' Custom Connector connects custom APIs or non-catalog sources to your data warehouse, with automatic builds and syncs via GitHub.
The headache of needing a connector that doesn't exist
Every connector catalog has its limits. At some point, the data team will need a source that isn't there: an in-house tool with no public documented API, or a niche vendor too small for any ingestion platform to prioritize.
Up until now, you had three options, and none of them were great: Wait for the connector to land on a vendor's roadmap, with no guaranteed timeline or priority; build the entire ingestion pipeline from scratch, along with all the maintenance that comes with it (pagination, rate limits, schema evolution, backfills, alerting—all rebuilt and maintained by your team forever); or settle for an all-in-one platform just because it promises to cover that specific edge case, sacrificing the rest of your modern data stack.
The worst-case scenario remains the same: a home-grown pipeline that runs smoothly in month one and becomes a permanent maintenance project by month six.
What is Custom Connector?
Custom Connector lets you point Erathos to a GitHub repository containing your connector's code. Erathos builds the code, keeps it synced with every push, and displays it in your workspace catalog with a Custom badge, right alongside native connectors.
This isn't DIY data ingestion. You write the extraction logic once in your repo, and it runs on the same infrastructure that already handles scheduling, incremental syncs, observability, and alerting for any native Erathos connector.
How it works
Install the Erathos GitHub App on the account or organization that owns the connector's code.
Tell Erathos which repository to watch.
Every push to the watched repository triggers an automatic rebuild of the connector image.
After the first successful build, the connector appears in the data sources catalog with a Custom badge, and the connection is configured just like any native connector.
Prerequisites
Admin access to the GitHub account or organization that owns the repository you want to watch.
A repository containing a valid Erathos connector project, following the development guide.
Why this isn't DIY data ingestion
Writing the extraction logic doesn't mean inheriting all the operational overhead again:
Automated builds and syncs. Every push to the watched repository rebuilds and syncs the connector, with no parallel deployment pipelines to maintain.
Incremental syncs out of the box. The exact same engine that powers native connectors runs your custom connector.
Built-in observability and alerting. Execution time, record volume, and error context are visible for every sync, with automated alerting webhooks for email, Slack, or Discord.
Your team writes the source integration. Erathos remains responsible for everything that happens after it runs in production.
Get started now
Create your Erathos account and connect your own SaaS or an off-catalog source in just a few steps. Once the first build succeeds, Erathos handles the rest: scheduling, incremental syncs, alerts, and observability, just like any native connector.
In-house tools without off-the-shelf connectors shouldn't force you to choose between waiting on a vendor's roadmap or building your entire ingestion infrastructure from scratch.
Check out the complete connector development guide and documentation at docs.erathos.com/connectors/custom-connectors.
The headache of needing a connector that doesn't exist
Every connector catalog has its limits. At some point, the data team will need a source that isn't there: an in-house tool with no public documented API, or a niche vendor too small for any ingestion platform to prioritize.
Up until now, you had three options, and none of them were great: Wait for the connector to land on a vendor's roadmap, with no guaranteed timeline or priority; build the entire ingestion pipeline from scratch, along with all the maintenance that comes with it (pagination, rate limits, schema evolution, backfills, alerting—all rebuilt and maintained by your team forever); or settle for an all-in-one platform just because it promises to cover that specific edge case, sacrificing the rest of your modern data stack.
The worst-case scenario remains the same: a home-grown pipeline that runs smoothly in month one and becomes a permanent maintenance project by month six.
What is Custom Connector?
Custom Connector lets you point Erathos to a GitHub repository containing your connector's code. Erathos builds the code, keeps it synced with every push, and displays it in your workspace catalog with a Custom badge, right alongside native connectors.
This isn't DIY data ingestion. You write the extraction logic once in your repo, and it runs on the same infrastructure that already handles scheduling, incremental syncs, observability, and alerting for any native Erathos connector.
How it works
Install the Erathos GitHub App on the account or organization that owns the connector's code.
Tell Erathos which repository to watch.
Every push to the watched repository triggers an automatic rebuild of the connector image.
After the first successful build, the connector appears in the data sources catalog with a Custom badge, and the connection is configured just like any native connector.
Prerequisites
Admin access to the GitHub account or organization that owns the repository you want to watch.
A repository containing a valid Erathos connector project, following the development guide.
Why this isn't DIY data ingestion
Writing the extraction logic doesn't mean inheriting all the operational overhead again:
Automated builds and syncs. Every push to the watched repository rebuilds and syncs the connector, with no parallel deployment pipelines to maintain.
Incremental syncs out of the box. The exact same engine that powers native connectors runs your custom connector.
Built-in observability and alerting. Execution time, record volume, and error context are visible for every sync, with automated alerting webhooks for email, Slack, or Discord.
Your team writes the source integration. Erathos remains responsible for everything that happens after it runs in production.
Get started now
Create your Erathos account and connect your own SaaS or an off-catalog source in just a few steps. Once the first build succeeds, Erathos handles the rest: scheduling, incremental syncs, alerts, and observability, just like any native connector.
In-house tools without off-the-shelf connectors shouldn't force you to choose between waiting on a vendor's roadmap or building your entire ingestion infrastructure from scratch.
Check out the complete connector development guide and documentation at docs.erathos.com/connectors/custom-connectors.