Launching today
Braidplane
Make data pipelines easier to maintain
2 followers
Make data pipelines easier to maintain
2 followers
Braidplane Alpha connects APIs, databases and files with declarative pipelines, SQL transformations and typed contracts. Version specs in Git and inspect runs in the UI or CLI. For evaluation with test data and non-production systems.
I’m Łukasz, founder of Braidplane.
The idea came from working with Python workflows orchestrated by Airflow. After dependency updates, we would run pipelines, inspect logs and check output data manually to confirm everything still behaved as expected.
I’m building Braidplane to make configuring and checking data flows easier. You declare sources, transformations, destinations and typed contracts, version the specifications in Git, and inspect execution through the UI or CLI.
The 73-second video shows Settlement Review: a preconfigured workflow compares a settlement CSV in S3 with a PostgreSQL payment ledger, then saves transaction-level findings and a batch summary. A payment matches, a refund differs by €5, and another transaction has no matching ledger entry. The demo also shows daily scheduling and run lineage so you can trace how the results were produced.
This is a synthetic example for investigating discrepancies, not accounting corrections or a guarantee of complete reconciliation. Contracts help detect structural mismatches; business checks still need to be defined for the workflow.
Braidplane is currently in Alpha, for evaluation with test data and non-production systems. I’m looking for engineers willing to try a concrete workflow and share where the product helps or falls short. I’ll personally help with the setup.
For a workflow like this, what would you need to see before trusting its results?