Stacks / Analytics
Meltano / dlt
ELT you run. Meltano is MIT; dlt is Apache-2.0 — Fivetran without the MAR meter.
The problem
Fivetran meters monthly active rows. You wanted extract-and-load on hardware you control. Meltano is MIT (meltano/meltano). dlt is Apache-2.0 (dlt-hub/dlt) if you want a Python loader. Airbyte is Elastic License 2.0 — not OSI, so it is not this path. Transforms stay on /replace/dbt-cloud. Orchestration stays on /replace/astronomer.
Replaces
Fivetran
Estimated SaaS saved
$1,200
per year, small team, before lock-in
Start on Railwaydbt Core if this is transforms in the warehouse, not extract-and-load
Placeholder: Meltano or a dlt job next to Postgres/a warehouse. This is often a worker, not a public website. No one-click template in this repo yet — Start on Railway. Transforms stay on /stacks/dbt-core-transform.
The stack
Cost table
| You stop paying | Typical / year | Self-host instead |
|---|---|---|
| Fivetran (small team) | $1,200 | Meltano or dlt |
Agent setup prompt
Replace Fivetran with Meltano (preferred) or dlt. - One connector you actually use. Land into Postgres or the warehouse you already have. Schedule it. - Do not install Airbyte and call it OSI (ELv2). Do not claim every Fivetran SaaS connector on day one. Write AGENT_PROMPT.md.
Also as markdown: /stacks/meltano-elt.md
FAQ
- Meltano or dlt?
- Meltano if you want a declarative ELT project. dlt if you want a Python library. Pick one.
- Why not Airbyte?
- Airbyte's LICENSE is Elastic License 2.0. This page uses MIT and Apache-2.0 loaders.
- Where is dbt?
- Transforms are /replace/dbt-cloud. This page is extract-and-load.