Data & Storage · Integration
Relational Junction
Add Relational Junction to your product for your customers, and give your AI agents governed access to it.
Relational Junction is Sesame Software's data replication suite: it copies data out of cloud and on-premise applications into a customer's own warehouse or lake, keeps it current with incremental change capture, and preserves relational structure rather than flattening everything into one wide table. Sesame now markets the same capability under its own product suite name, so the Relational Junction branding and the current Sesame products are one lineage. What an embedded integration works with is the replication job, the source and target connections behind it, and the tables a run lands, which is why freshness is the useful question: your product wants to know when a source last replicated before it presents a number as current. Each customer replicates a different set of sources into a different target, so both sides are configuration.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Relational Junction environment so your product reads from the warehouse they already replicate into.
Start a replication job or read its last run, so your product knows whether the data it is about to use is actually current.
Read source and target configuration per tenant, so your setup screens show the systems that customer really replicates.
Support whichever warehouse a customer targets, from Snowflake or BigQuery to Redshift or an Oracle warehouse, as configuration.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports when a source last replicated and which tables came with that run.
An agent triggers a replication run within scoped permissions, with the job it started logged.
An agent explains why a figure looks stale by reading the last run rather than guessing.
Example prompt
When did this source last replicate, and which tables changed in that run?
Set up Relational Junction in 4 steps
- 01Enable the Relational Junction connector in your fastn dashboard.
- 02Have each customer connect their own environment so jobs run under their credentials rather than a shared account.
- 03Map the replication jobs, source connections and target tables your product reads, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Relational Junction integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Relational Junction integration without building it. Your customers connect their own Relational Junction account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Relational Junction update is not your on-call problem.
- One integration serves your product and your agents. The same governed Relational Junction connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Snowflake
AWS Redshift
BigQueryOften used alongside
Tools the same teams tend to run next to Relational Junction, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceRelational Junction integration FAQ
How do I add a Relational Junction integration to my product?
Enable the Relational Junction connector in your fastn dashboard, then let each customer authenticate their own Relational Junction account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Relational Junction client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Relational Junction account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Relational Junction account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Relational Junction integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports when a source last replicated and which tables came with that run.
Who maintains the Relational Junction integration?
fastn does. When Relational Junction changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Relational Junction integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Relational Junction reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Relational Junction integration?
A common starting point: let each customer connect their own Relational Junction environment so your product reads from the warehouse they already replicate into. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Relational Junction integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Relational Junction does not change your per-connector cost. You can start free with 3 connected accounts.
Add Relational Junction to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.