design partners onboarding now·human approval before anything runs·credentials collected once, stored encrypted·every data source documented·v0.7 · forge mcp · tap mcp
The context layer for your company's data

Stop rebuilding
context every time
someone asks.

Your data is scattered across tools, and its meaning gets re-explained on every question. Celync captures it once — what each data source is, where it came from, when it refreshed, and what it's for — so your team and your agents read from one understood context layer.

Agents are only as good as the data and context they have.
forge · pipeline:salesforce-bigquery
/01 The problem

Data infrastructure is broken
for everyone except enterprises.

We talked to 80 data teams in three months. The same six sentences came back, almost word for word. Here they are.

/01

My system doesn't have a connector.

Fivetran has ~400 connectors. There are tens of thousands of APIs. The moment you use a niche CRM or internal system, you're on your own.

connector gap
/02

Current tools cost too much and still break.

Per-connector pricing, enterprise sales motion, and schema drift that still breaks your syncs. You're paying a premium for a fragile system.

cost · fragility
/03

My AI tools grab data inconsistently.

Claude, Cursor, and Copilot MCP into source systems ad hoc. That's a band-aid. They need a reliable, curated layer to read from — not your prod database.

ai · context
/04

The data exists, but I can't trust it.

The same metric calculated three different ways across three dashboards. No ownership. No certification. No way to know which dataset is canonical.

trust · ownership
/05

Data engineering takes too long.

You have the business context to build a great dataset. You're blocked waiting on an engineer who has a queue of ten other priorities.

velocity
/06

I just want to move data from A to B.

Simple data movement shouldn't require a data engineering hire, a $2k/mo SaaS contract, and two days of setup. It should take an afternoon.

simplicity
/02 The flow

Sources in. Forge in the middle.
Tap out — clean, certified, current.

Forge is where pipelines are built and watched. Tap is where everything reads from. Source systems on the left only ever talk to Forge.

Sources
Forge MCP — build & heal
Tap MCP — read
Consumers
salesforce
stripe
postgres.app
shopify
jira
Forge
build · monitor · heal
Tap
certified · current · queryable
claude · cursor · copilot
bigquery · snowflake
looker · metabase
next.js app
analyst notebook
/03 Connector universe

If it has an API,
we can move it.

Most ETL tools give you a fixed catalog of connectors and a roadmap promise for everything else. We generate connectors on demand — paste an API spec, a docs URL, or describe the system in plain English.

The answer is never "we don't support that."

SalesforceStripePostgresBigQuerySnowflakeRedshiftHubSpotShopifyIntercomMixpanelSegmentAmplitudeNotionLinearGitHubJiraZendeskPipedriveWorkdayGreenhouseLatticePlaidMercuryBrexNetSuiteCalendlyGongRampVantaPagerDutyDatadogCloudflareOktaAuth0SentryStatsigMailchimpKlaviyoRecurlyChargebeeModeHexCensusHightouchAirtableSmartsheetServiceTitanToast POSyour internal adminthat legacy ERPa Postgres on a VM nobody ownsan HTTP endpoint behind Cloudflarethe API your CFO swears by+ paste a docs URL →+ describe the system+ upload an OpenAPI spec
Today: REST APIs, Google Sheets, and databases in; Postgres, Sheets, or BigQuery out.Forge generates the long-tail connectors on demand.
/04 Tap from anywhere

Your AI tools read from Tap.
Not your prod database.

Tap is an MCP server. Point Claude, Cursor, Copilot, or your own agent at it — they get current, queryable data with the context to use it correctly: what it is, who owns it, how fresh it is, and what it's for.

claude · connected to tap.acme
RK
Rohan · 11:42
What's our weekly active customers trend over the last 8 weeks, broken out by plan?
C
Claude · 11:42
I'll check Tap for a certified WAU-by-plan dataset.
tap.query
analytics_prod.active_customers
certified · owner growth.k_tan · fresh 4m ago

✓ 8 rows · returned in 240ms
Pro is up +18.4% WoW, Team flat at ±0.5%, Free declining −6.2%. The Pro lift starts the week of Apr 21 — that aligns with the onboarding revamp shipping.
~/.config/claude/mcp.json
{ "mcpServers": { "tap.acme": { "command": "npx", "args": ["@celync/tap", "--workspace", "acme"], "env": { "CELYNC_TOKEN": "$CELYNC_TOKEN" } } } } # That's it. Tap is an MCP server out of the box. # Claude / Cursor / Copilot / your agent → reads from Tap. # Tap → reads from certified datasets. # Forge → keeps those datasets clean. $ celync tap query "active_customers last 8w by plan" ◆ analytics_prod.active_customers owner growth.k_tan certified yes · fresh 4m ago pipeline forge://app_db→bq.analytics_prod ✓ 8 rows · 240ms
/05 Two surfaces

One platform.
Two ways to use it.

Forge is for engineers and agents managing pipelines. Tap is for anyone — humans or AI — that needs to read from clean data.

Forge
forge mcp

Build pipelines from a sentence. Watch them in plain English. Approve fixes from the same place.

salesforce.productionbigquery.analytics_prod
synced
4m
stripe.livesnowflake.finance
reconciling
12s
shopify.ordersbigquery.commerce
drift
1h
jira.issuessnowflake.eng_metrics
learning
7m
hubspot.contactspostgres.app_db
synced
2m
shopify.orders → bigquery.commerce · drift detected
New field customer_locale. Adding to BigQuery as STRING, back-fill 30d.
Tap
tap mcp

Browse certified datasets with ownership and freshness. Query them. Or expose them to your AI tools as MCP.

analytics_prod.daily_revenue
certified
Daily revenue by product, currency-normalized.
owner finance · m_langfresh 12m
analytics_prod.active_customers
certified
WAU/MAU rolled up from session events, by plan.
owner growth · k_tanfresh 4m
commerce.orders_canonical
certified
Single canonical order table — Shopify + manual.
owner cs · j_diazfresh 2h
eng_metrics.deploy_throughput
certified
Deploys per service per day, with rollback rate.
owner eng · r_kofresh 6h

If a pipeline breaks at 2am, the agent fixes it. You wake up to a one-line summary.

Forge watches every pipeline, detects schema drift, proposes a fix, and ships it after your approval — or auto-ships under rules you set. The on-call rotation moves from "data engineer" to "nobody, usually."

100%
of changes to your systems require your approval before they run
/06 Get on it

Become a design partner.

We're onboarding a small group of design partners. Join the waitlist and we'll reach out as we open more capacity.

Waitlist

Get early access.

Join the waitlist and we'll reach out as we open more capacity. No sales call. No drip. One short email when we're ready for you.

No spam. We'll reach out when we're ready for you.