First successful run in about ten minutes.
The path below is the real onboarding sequence. If you have no external system to connect yet, step 3 offers a sample source — fifty synthetic customer records — so you can complete the whole loop before asking anyone for a credential.
Six steps
What the first session looks like.
Environments created
- production
- sandbox
If you prefer the API
The same six steps, as calls.
Everything the interface does is available over the API, against a sandbox key.
export ZX_KEY="zx_sk_sandbox_…" # 1 · workspace and environment are created in the interface# 2 · declare a connection (must pass a test before it saves)curl -X POST https://api.zentrixquark.com/v1/connections \ -H "Authorization: Bearer $ZX_KEY" \ -d '{"name":"postgres-sandbox","type":"postgres","environment":"sandbox"}' # 3 · create the flow from a definition you can commitcurl -X POST https://api.zentrixquark.com/v1/flows \ -H "Authorization: Bearer $ZX_KEY" -d @customer-sync.json # 4 · dry run — every stage executes, nothing is writtencurl -X POST https://api.zentrixquark.com/v1/flows/flw_2a19/run \ -H "Authorization: Bearer $ZX_KEY" -d '{"mode":"dry_run","limit":50}' # 5 · deploy version 1 and arm the schedulecurl -X POST https://api.zentrixquark.com/v1/flows/flw_2a19/deploy \ -H "Authorization: Bearer $ZX_KEY" -d '{"message":"initial sync"}' # 6 · watch itcurl "https://api.zentrixquark.com/v1/runs?flow=flw_2a19" \ -H "Authorization: Bearer $ZX_KEY"Illustrative. No production API is live yet.
Current status
Workspace sign-up is not open yet.
DataBridge is in development. This site is the public specification of the product: the architecture, the API contract, the security design and the plan structure are published ahead of implementation so they can be reviewed and argued with. The interactive demo on the homepage runs the real eight-step sequence against sample data.
If you want to be part of the first group to use it, tell us what you are trying to connect — naming the systems and the rough record volume is enough.