Status
Build status
Is Waddle live? No. It is an early preview. This page lists what exists, what is built but not live and what is not written, as of .
Working and tested: CLI, Pipeline engine and checks. Built, not live yet: Hosted run image, API, MCP server (local), Web console. Planned, not written: MCP endpoint (hosted), Hosted service, Sign-in and billing.
| Component | State | What is true today |
|---|---|---|
| CLI | working | Local, with no account and nothing uploaded: init, validate, test and run. Hosted: deploy, pipelines, trigger, runs, logs and secret (the value comes from stdin). Format, lint and all tests pass on a Linux build server, including end to end against a real API server. Not published as a download yet. |
| Pipeline engine and checks | working | Files and Postgres sources and sinks, incremental watermark, not_null, unique, row_count and reconcile checks, read-back of the sink. Tested against Cloudflare R2 and a real Postgres 18; the incremental upsert round trip passes on Linux. |
| Hosted run image | built, not live | The renderer that turns a pipeline into DuckDB scripts matches the engine on the parity tests, and the run entrypoint scrubs secret values and connection-string passwords from output (tested). The image itself is not built or booted yet. |
| API | built, not live | Organisations, scoped tokens, versioned pipelines, encrypted secrets, runs, quotas, schedules, webhooks, usage, CORS and a generated OpenAPI document. Its 14 tests pass on a Linux build server. Runs use a mock runtime only: the machine runtime is not written, and the server is not deployed. |
| MCP server (local) | built, not live | Stdio server with eight tools to validate, test, deploy and run pipelines. No tool accepts a secret value. Its tests pass on a Linux build server; it has not been tried from a real MCP client yet. |
| Web console | built, not live | Built. The production build, type check and 42 tests pass on a Linux build server. The in-browser SQL preview has not yet been checked in a real browser. Not deployed. |
| MCP endpoint (hosted) | planned | A hosted /mcp endpoint that uses the same API tokens. Not written. |
| Hosted service | planned | Running customer pipelines in microVMs needs the machine runtime adapter, the network allow-list and a cross-tenant test. Not written. |
| Sign-in and billing | planned | Invite-only sign-in and metered billing. Not written. Until then, operators issue API tokens by hand. |
What do the states mean?
- Working: built, its automated tests pass, and it does what its description says.
- Built, not live: the code is written and tested on its own, but it is not deployed or not usable end to end yet. The detail column says what is missing.
- Planned: not written.
Nothing here is a service level. The hosted service, sign-in and billing do not exist, and nothing is for sale. See security for what is tested about isolation and pricing for how pricing will work.