Tapstate docs
Learn the tapstate product model, prepare connectors, and build reviewable data paths
Tapstate connects operational systems through one governed Capture–Transform–Serve data path. Use these docs to understand the model, prepare external systems, and describe a path as reviewable resources.
Start here
What is tapstate?
Understand the customer problem and the tapstate product model.
Quickstart
Run the disposable Docker playground and inspect one assembled order.
Connections and connectors
Understand connector definitions, connection roles, and scope.
Capture modes
Choose Snapshot, Full load + CDC, Stream, or API by outcome.
Current preview
The public preview demonstrates one concrete operational data path:
- MySQL orders and PostgreSQL shipments, each captured by an initial load plus continuous change data capture (CDC)
- an in-flight
nesttransform that assembles one order document - continuous materialization to MongoDB
The local MongoDB instance is the preview's managed state store for the declared view. Do not infer another store, query API, or push surface from the broader product model. Start with the Quickstart to run the current path locally.
The server-backed preview is supplied through the disposable Docker playground; this release does not publish a standalone server installer.
Complete a task
Prepare a connector
Find roles, modes, permissions, limitations, and exact field names.
Install the CLI
Install and verify the preview CLI on macOS or Linux.
Explore the order-state demo
Change MySQL and PostgreSQL rows and watch the same MongoDB document update.
Create your own workspace
Author and validate declarative source, pipeline, transform, view, and serve resources.
Look up fields
Use the DSL grammar and resource reference for exact syntax.
Troubleshoot
Separate authoring, connector, deployment, and data problems.
Understand the product
Architecture
Review the logical data plane, control plane, and state boundaries.
Use cases
Match customer outcomes to the data path they need.
Compare approaches
Choose between a unified path and a composable streaming stack.
State and storage
Understand working, recovery, and materialized state.
AI-readable documentation
The HTML pages, llms.txt, combined context, and page-level Markdown are generated from the same content. Connector frontmatter supports discovery; the page body remains canonical for people and agents.