In Q1 2026, a five-person DevOps team opened a renewal email from Terraform Cloud. The annual bill had jumped from $180,000 to $270,000. A 50% increase with zero new features to show for it. The team lead forwarded the email to their Slack channel with one line: “We need to talk.”
Three months later, that team had migrated 600 Terraform modules to OpenTofu, replaced Fivetran with self-hosted Airbyte for their data pipelines, and swapped Datadog for Grafana plus SigNoz. Annual infrastructure tooling spend dropped 58%.
This is not an outlier. In 2026, open source infrastructure is systematically eroding the territory of commercial SaaS vendors. And if you run a B2B SaaS company, you should be paying attention, whether as a buyer of these tools or a seller competing against open alternatives.
The Trust Crisis That Started It All
The timeline matters.
In August 2023, HashiCorp changed Terraform’s license from Mozilla Public License (MPL 2.0) to Business Source License (BSL 1.1). BSL is not an OSI-approved open source license. It prohibits anyone from using Terraform to build a “competing product,” and the definition of “competing” was vague enough to make legal departments nervous.
The community response was fast and final. By September 2023, the Linux Foundation announced OpenTofu, a fork based on Terraform’s last MPL-licensed version. IBM, Alibaba, Gruntwork, and Spacelift backed it on day one.
Then in late 2024, IBM acquired HashiCorp for $6.4 billion. Terraform, Vault, Consul, Nomad: all became IBM assets. IBM needs to recoup that investment. Tighter enterprise licensing, feature gating, and ecosystem lock-in are the predictable commercial playbook.
This was not a one-off event. Elastic switched Elasticsearch from Apache 2.0 to SSPL in 2021, and AWS immediately forked OpenSearch. MongoDB made the same move even earlier, in 2018. In 2024, Elastic added AGPL back as an option under community pressure, but trust, once broken, costs far more to repair than to maintain.
According to an industry survey from April 2026, 38% of Terraform users are evaluating or have already started migrating to alternatives. OpenTofu’s annual download growth exceeded 300%, with cumulative downloads approaching 10 million. GitHub stars reached 29,300 as of June 2026.
The logic behind these numbers is simple: when your infrastructure tooling vendor can change the rules at any time, you either accept the risk or take back control.
The Money: How Much Open Source Actually Saves
Cost is the primary migration driver. It is more practical than any philosophical commitment to openness.
Take the data integration space. Fivetran charges by Monthly Active Rows (MAR). A mid-size SaaS company processing 50 million rows per month typically faces a Fivetran bill of $120,000 to $180,000 annually. Switching to self-hosted Airbyte brings infrastructure costs (Kubernetes cluster plus storage) to roughly $20,000 to $40,000 per year, plus about half an engineer’s time for maintenance. Net savings: 50 to 70%.
A more extreme case: one e-commerce platform had a single high-churn table updating 8 million rows daily. Their Fivetran monthly bill tripled in a single quarter because of per-row pricing. After moving to Airbyte, the same data volume generated only infrastructure costs. No surprise bills tied to row counts.
The gap in observability is even wider. Datadog’s pricing model stacks per-host fees with per-module SKUs. Infrastructure monitoring runs $15 to $23 per host per month, plus APM at $31 per host per month, log management starting at $0.10 per GB, and Synthetics billed per test run. A team with 50 hosts running Infrastructure plus APM plus Logs easily crosses $5,000 per month. Over $60,000 annually.
Self-hosted SigNoz? The ClickHouse plus OpenTelemetry stack costs roughly $800 to $1,500 per month in cloud compute and storage at 50-host scale, covering logs, traces, and metrics. Even factoring in engineering maintenance time, total cost lands at 20 to 30% of what Datadog charges. SigNoz’s own published figures claim customers save up to 80% after migration.
Infrastructure-as-code shows the same pattern. Terraform Cloud’s Team and Governance tier starts at $70 per user per month. Enterprise pricing is custom but commonly exceeds $100 per user per month. OpenTofu paired with open source CI/CD pipelines (GitHub Actions, GitLab CI) brings the tooling layer cost to near zero, given that features meet your requirements.
Technical Maturity: From “It Works” to Production-Ready
Two years ago, choosing open source alternatives required courage. Not enough connectors, incomplete documentation, thin community support. These were legitimate concerns.
In 2026, the picture has shifted.
OpenTofu has reached version 1.12.x, with its codebase diverging significantly from Terraform through 2025. Features unique to OpenTofu include native state file encryption (supporting AWS KMS, PBKDF2, and other key providers), dynamic provider configuration, loopable import operations, and provider iteration. In Terraform, these either do not exist or sit behind the paid Enterprise tier.
One critical detail: the migration path remains smooth today. Both projects share a compatible core language and state file format. Existing Terraform modules run on OpenTofu with near-zero modification. But this window is narrowing. As each project introduces exclusive features, future migration complexity will increase. Waiting has a compounding cost.
Airbyte now offers over 350 connectors in its open source version, covering major SaaS platforms, databases, and API sources. The Connector Development Kit (CDK) lets Python developers build custom connectors in a day or two. Airbyte Cloud provides a managed option, typically priced 30 to 50% below Fivetran.
For comparison: Fivetran completed its merger with dbt Labs in June 2026 and maintains over 500 connectors with higher consistency (all maintained by paid engineers). But Airbyte’s advantage lies in flexibility. Self-hosting means data never leaves your network, which is a hard requirement for regulated industries.
Grafana plus SigNoz covers the three pillars of observability: metrics, logs, and traces. SigNoz natively supports OpenTelemetry, using ClickHouse (the columnar database behind Uber and ByteDance) for storage. Query performance at high data volumes is strong. Grafana’s dashboard ecosystem and alerting capabilities are already industry standard. Together, they match Datadog’s core use cases.
PostgreSQL deserves a mention at the database layer. It is the de facto open source relational database standard, with performance and features that have caught up to (and in some cases surpassed) many commercial options. Choosing AWS RDS PostgreSQL or Google Cloud SQL for PostgreSQL over Aurora or Cloud Spanner is itself an act of preserving migration flexibility. Your data format and query syntax work in any PostgreSQL-compatible environment.
Composable Over All-in-One
Fivetran plus dbt Labs completed their merger in June 2026, serving over 100,000 data teams. The merger thesis: end-to-end data infrastructure (movement plus transformation plus governance) in one platform.
This is exactly the model the open source camp rejects.
The composable architecture philosophy says: pick the best tool for each layer, and connect them with open standards (SQL, OpenTelemetry, Apache Iceberg). Data integration via Airbyte. Transformation via dbt Core (still open source under Apache 2.0). Orchestration via Dagster or Prefect. Storage in Iceberg format. Analytics through DuckDB or ClickHouse.
The benefits of this approach:
No single point of failure. If Fivetran goes down, your entire pipeline stops. With self-hosted Airbyte, availability depends on your own Kubernetes cluster, which you control.
Transparent pricing. You pay for compute and storage, not for a “platform.” No MAR multiplication leading to billing surprises.
Freedom of choice. When a better tool appears, replacing a single component costs far less than replacing an entire platform. OpenTelemetry’s OTLP protocol means your instrumentation code stays the same whether you switch from SigNoz to Grafana Tempo or the reverse.
The trade-off is real: you own the integration glue, version compatibility testing, and operations. This is not a free lunch. It is a trade where you spend engineering time to gain control.
Why Open Source Moves Faster
OpenTofu delivered multiple features within two years of forking that Terraform had failed to ship for nearly a decade. Client-side state encryption was an RFC submitted to Terraform by community members back in 2016. OpenTofu shipped it in under a year.
The difference is governance. OpenTofu operates under the Linux Foundation with a Technical Steering Committee (TSC) meeting biweekly. Community members participate directly in RFC discussions and code contributions. Terraform under IBM follows commercial priorities. New features are more likely to land in paid Terraform Cloud or Enterprise, not the open source edition.
Airbyte’s connector development model follows a similar dynamic. The CDK lowers contribution barriers. When Notion updates its API version, community patches often arrive faster than a commercial vendor’s planned release cycle.
Grafana’s ecosystem is the textbook case. Grafana Labs keeps core products (Grafana, Loki, Tempo, Mimir) open source while monetizing through Grafana Cloud and enterprise support. This model proves open source and commercial viability coexist. The condition: you do not treat the open source community as your unpaid beta testing group.
The Honest Counterarguments
The open source narrative frequently glosses over several realities. These deserve direct acknowledgment.
Operations cost real money. Self-hosted Airbyte requires ongoing Kubernetes maintenance: upgrades, scaling, troubleshooting. OpenTofu state management needs you to build and maintain your own remote backend. SigNoz’s ClickHouse cluster demands tuning as data volumes grow. Someone has to own this work. A 20-person startup without a platform engineering team may find that self-hosted Airbyte’s hidden costs exceed Fivetran’s invoice.
SLAs and commercial support carry genuine value. Datadog commits to 99.9% availability, with a dedicated technical account manager when things break. Self-hosted SigNoz availability is your responsibility. When ClickHouse runs out of memory at 3 AM, no one is coming to help. For financial services, healthcare, and other regulated industries, a vendor’s SOC 2 Type II certification, HIPAA compliance, or FedRAMP authorization is not optional.
User experience gaps exist. Fivetran’s automatic schema drift handling, anomaly detection, and retry mechanisms work out of the box. Airbyte remains less polished on these details. Datadog’s Session Replay, Synthetic Monitoring, and Real User Monitoring form a digital experience suite that has no equivalent in the open source world.
Not every organization can self-host. A data team with three analysts and zero infrastructure engineers cannot realistically operate Airbyte on Kubernetes. Fivetran’s “zero maintenance” value proposition is genuine for these teams. They are paying for the privilege of not worrying.
Migration Strategy: Pragmatic, Not Dogmatic
The smart play is not “go all-in on open source” or “stay locked to commercial vendors.” It is understanding where your needs fall.
Ask three questions:
How much engineering bandwidth can you dedicate to infrastructure maintenance? If the answer is “almost none,” full self-hosting may not fit. Airbyte Cloud or SigNoz Cloud offer a middle path: open source core with managed operations.
How strict are your data compliance requirements? If data cannot leave a specific geographic region or network boundary, self-hosting becomes nearly the only option regardless of cost.
What does your growth curve look like? If data volumes triple annually, usage-based commercial SaaS pricing gets progressively more expensive. Open source self-hosting scales at near-linear cost (primarily storage and compute).
Phased migration beats a single cutover. Start in non-critical environments. Manage dev infrastructure with OpenTofu. Sync a few non-core data sources through Airbyte. Monitor a handful of microservices with SigNoz. Build confidence and operational muscle, then expand to production.
For Terraform-to-OpenTofu migration specifically, the window remains friendly today. Core language and state file compatibility means low risk and modest engineering effort. But as each project diverges further, the cost of waiting only increases.
Looking Ahead to 2027
Industry consensus points toward continued acceleration of open source infrastructure adoption over the next two years. The drivers are converging:
AI workloads are exploding cost pressure (GPUs are expensive enough without observability and data pipelines consuming another chunk of the budget). Multi-cloud architecture is becoming standard practice (amplifying the risk of vendor lock-in). Platform engineering culture is spreading (more organizations are building internal infrastructure teams with the skills to run these tools).
The Fivetran plus dbt Labs merger is a defensive move from the commercial camp, using bundling to reduce customer switching motivation. IBM will likely introduce more paid feature gates in Terraform, which will push further OpenTofu adoption. Datadog’s 15-plus product SKU model is being systematically unbundled by the OpenTelemetry ecosystem.
Open source infrastructure will not fully replace commercial SaaS. Linux did not kill Windows. But it is resetting the baseline for what counts as a “reasonable price” and “acceptable level of control.” When open source reaches 80% feature coverage at 20 to 30% of the cost, vendors need an extremely compelling story to justify the remaining 20% gap.
The Bottom Line
This is not a technology decision. It is an organizational capability question.
Do you have the ability to operate your own chosen tool stack? If yes, open source gives you freedom and economics. If no, commercial SaaS sells you the service of not having to worry. Both are valid choices.
The key is being honest about where you stand. The worst outcome is choosing self-hosted open source for cost savings but lacking the engineering depth to run it reliably. The second worst outcome is paying 3x for commercial tools because “we’ve always done it this way” while your competitors pocket the savings and invest them elsewhere.
The infrastructure layer is too important to leave on autopilot. Whether you choose open source or commercial, make it a deliberate decision based on your team’s real capabilities, your compliance requirements, and your growth trajectory. The tools are ready. The question is whether your organization is.
Stay updated with our latest AI insights
