Meltano

The unit at least is clear even if the price is not. Meltano defines a compute hour as the time its managed infrastructure spends actively running pipelines, and gives a worked shape: a connector taking 30 minutes to sync, running twice a day, uses about 30 hours a month. The tiers are therefore a throughput ladder, not a feature ladder.

What the tiers do buy, beyond compute, is workspaces and engineering time. Starter includes 25 workspaces and unlimited users; Growth 100 workspaces and 8 hours a month of engineering on demand; Scale unlimited workspaces and 15 hours; Enterprise adds custom connectors and a custom SLA. All plans, Open included, carry the full catalogue, stated as 600+ connectors.

Meltano Open remains the priceable option: self-hosted, MIT-licensed, with the same connectors and Git-native pipelines, and the cost is infrastructure plus the platform-engineering time to run it. Meltano is direct that Open is built for experimentation and that production teams are the target for the managed tiers.

On ownership: Meltano describes itself as an open source project by Matatika, and Meltano's own about page says Aaron became founder of Meltano in 2025 and that the two came together under the Meltano name in 2026. Meltano publishes no date more precise than that.↗source - pulled 2026-09-22

Pick Meltano when the team is engineering-led and wants pipelines defined as code, version-controlled, and reproducible. Strong fit for analytics-engineering shops that already run dbt with rigour. Meltano Open is the low-commitment way in, because it costs nothing and needs no sales conversation.

Avoid Meltano when the team is analyst-led and would rather click through a Fivetran UI than write YAML, or when the buying process needs a list price before a call. Nothing on the managed side can be budgeted from the rate card, which is a real constraint in a procurement-heavy organisation.