Connect anything to anything
Drop connections on the canvas. Wire them up. One source to many destinations, many to many, with transformation steps in between. No flow type to pick — Composer figures it out.
Composer
Build data pipelines without picking a flow type first.
Drop connections on the canvas. Wire them up. Chat with Simba, drag-and-drop, or write code — same workspace, same flows. Backed by 200+ flow types and 3,979 templates underneath.
- 200+ flow types underneath
- 3,979 pre-built templates
- 270+ connectors
- 0 flow types to pick first
The challenge
Too much commitment, too early.
Most data integration tools make you pick a flow type before you understand what you’re building. Pick wrong and you reconfigure. Pick right and you still spend an hour mapping fields by hand.
What Composer does
Six capabilities that change how you build flows in Etlworks. The first three are about the workspace itself. The last three are about what’s underneath.
Build it four ways
Chat with Simba, drag-and-drop, write code, or run from CLI — all on the same flow. Switch modes mid-build. The flow object is the same regardless of who’s driving.
Live preview as you build
See data flowing as Simba assembles or as you wire connections. Validate transformations against real rows before you ship.
200+ flow types underneath
ETL, ELT, reverse ETL, CDC, replication, files, EDI, webhooks. Composer composes them — but the engine primitives are still there if you need to drop into one directly.
3,979 templates underneath
Pre-built integrations for known source-destination pairs. AI-searchable from inside Composer. Simba reaches for them automatically when building.
Nested workflows
Compose multiple flow types into one larger pipeline. Conditional logic, loops, parallel branches, error handling. Build complex orchestrations in the same canvas.
How Composer fits the platform
Composer is a workspace, not a flow type. It sits on top of the existing platform — flow types, templates, and connectors are the foundation. Same engine, new starting point.
Backwards compatible: Existing flows built directly from flow types or templates keep working. Composer doesn’t replace the gallery — it sits next to it as a faster path for new builds.
From the team
“We watched new users open Etlworks for the first time, see 200+ flow types and 3,979 templates, and freeze. The platform’s depth was working against us. Composer is what happens when you stop asking people to commit before they understand. Drop two connections, wire them up, ask Simba to handle the parts you don’t know yet. That’s it. The rest of the platform is still there underneath — but you don’t need to know it exists to ship something useful.”
Composer launched May 1, 2026. We’re talking to early-adopter customers about how they’re using it. If you’d like to be part of those conversations — or share what you wish Composer did — reach out at product@etlworks.com.
FAQ
How is Composer different from picking a flow type from the gallery?
The flow gallery makes you commit before you build — pick “Database to Database” or “API to File” and the UI configures around that choice. Composer skips that step. Drop the source and destination on the canvas, wire them, and Composer figures out the flow type from your wiring. You can still drop into a specific flow type later if you need to. Existing flows built from the gallery can also be converted to Composer flows directly from the UI — no rebuild required.
Do I need to use Simba to build in Composer?
No. Composer supports drag-and-drop, code, and CLI building without ever invoking the agent. Simba is opt-in — useful when you want to vibe-build or hand off boilerplate, but never required. Most current users build manually in Composer; we expect that ratio to shift over time, but the choice stays yours.
Can I still start from a template?
Yes. All 3,979 templates are still discoverable from inside Composer via AI search. Pick one as a starting point, then customize on the canvas. Simba uses templates automatically when building flows for known source-destination pairs.
Can Composer flows be exported, version-controlled, run from CLI?
Yes. Composer flows are first-class flows — same export/import, same built-in version control, same CLI access as any other flow in Etlworks. The workspace is new; the underlying flow object is the same one you’d get from the gallery.
What scripting languages does Composer support inline?
JavaScript, Python, and SQL. Use them inline for transformation steps, validation, or custom logic. Self-hosted scripts also work via SSH for code that needs to live outside the Etlworks runtime.
Is Composer available in on-premise deployments?
Yes. Composer ships with every Etlworks deployment — cloud, hybrid, and on-premise. Same workspace, same engine. No feature differences across deployment types.
Try Composer.
14-day free trial. No credit card. Build your first flow in Composer — or hand it to Simba and watch.