Jitsu Just Got Acquired. Its MIT License and Self-Hosting Survived the Deal.

Helium Ventures announced on October 13, 2026 that it has acquired Jitsu, the open-source customer data platform that positions itself as a Segment alternative. Jitsu collects event data from websites, apps, and servers, then delivers it to data warehouses and business tools in real time. For the self-hosting crowd, the news that matters is not the change of ownership. It is what the announcement explicitly promises will not change: Jitsu remains MIT-licensed, free to self-host with no usage limits, and existing Jitsu Cloud plans and pricing stay exactly as they are.

Open-source acquisitions have a familiar script. A buyer arrives with a smile, and within a year the license gets clarified into something that charges for the features everyone actually runs. Self-hosters watched that script play out when MinIO changed its licensing so the free and open-source edition was effectively neutered, leaving homelabs scrambling for alternatives. Against that backdrop, a buyer that opens its announcement by recommitting to MIT licensing and unlimited self-hosting is doing something unusual. The question, as always, is whether the promise survives contact with the quarterly plan.

A software holding company, not a venture fund

Helium Ventures describes itself as a firm that acquires and operates software businesses. It was founded by Rohit Mittal and Priyank Singh, who previously co-founded the lending company Stilt, and its portfolio already includes InsurGrid, Maroo, and That's The One. Jitsu is the latest addition to that collection. The model matters because it implies a different set of incentives than venture capital: hold and operate rather than grow at all costs and exit. Helium's announcement says the pace of Jitsu feature releases has already increased since the acquisition, with the investment aimed at the unglamorous daily work of pipelines: keeping events flowing, connecting more tools, and resolving problems quickly.

Jitsu co-founder and CEO Vladimir Klimontovich stays with the business in an advisory role, and the founders' own statement frames the deal as a way to give partners a stronger platform to build on while preserving the open-source foundation. Founder continuity is the least reliable metric in acquisitions, but it is the only public signal available about culture, and it points, at least for now, in the friendly direction.

What Jitsu actually does, and why it matters to self-hosters

A customer data platform sits between your product and your analytics. When a user clicks a button, signs up, or pays an invoice, Jitsu captures that event and routes it to wherever it needs to go: a data warehouse, an email tool, an analytics dashboard. The point of doing this yourself is control. With a SaaS CDP like Twilio's Segment, every event your users generate passes through a vendor's servers, and the pricing is metered on the vendor's terms. With a self-hosted Jitsu, the pipeline runs on your infrastructure, the data lands in your warehouse first, and the bill is the cost of the machine you already own.

Jitsu has been expanding beyond the classic one-way pipeline. The company recently launched reverse ETL, which sends data from the warehouse back into business tools, so a marketing team can act on warehouse-computed segments without a manual export. New destinations added in recent releases include Resend, SendGrid, Statsig, DuckDB and MotherDuck, and Xero, alongside expanded authentication options for Snowflake and Postgres. The project also offers a managed ClickHouse service for teams that want a hosted analytics warehouse next to their pipeline.

The self-hosting story got better, not smaller

If the acquisition were a prelude to neglect, the release cadence would be the tell. Instead, the July release of Jitsu 2.14 reads like it was built for production self-hosters. It ships a Kubernetes operator, dedicated function servers, and Kubernetes-native sync scheduling, so teams can scale ingestion, transforms, and syncing independently. Audit logs, expiring API tokens, maintenance mode, and event reprocessing give operators more control over access and a clearer path to recovering failed deliveries. Those are the features that matter when a pipeline stops being a hobby project and becomes something the business depends on.

Developer tooling got attention too: a Management API and CLI plus an MCP server let both humans and AI agents configure and debug pipelines. The MCP angle is a sign of the times. When agents can reach your pipeline configuration, they can also break it, so the expiring tokens and audit logs in 2.14 arrive at exactly the right moment.

Trust, but verify the license

None of this removes the obligation to verify. Licenses are promises until someone edits the repository, and the only license that counts is the one in the code you deploy. Jitsu's MIT license is the most permissive common choice: you can run it, modify it, and distribute it with almost no strings attached. If you self-host, it is worth checking the LICENSE file in each release you pull, pinning to known-good versions, and watching the project's release notes for any licensing language. That is not paranoia. It is the maintenance cost of the freedom that made you self-host in the first place.

Open-source acquisitions usually end with a license change. This one began with a promise: MIT stays, self-hosting stays, and usage stays unlimited.

What to do if you run Jitsu

According to the announcement, customers and partners do not need to take any action as a result of the acquisition. Cloud plans are unchanged: a free tier covers 200,000 active events per month, Business costs $99 per month with 2 million active events included, and additional events cost $40 per million, with custom Enterprise plans on top. If you self-host, the practical homework is small. Test the 2.14 upgrade path in a staging environment, try the maintenance mode and event reprocessing features before you need them, and make sure your backup and restore story covers the pipeline configuration, not just the warehouse data. And keep an eye on the one thing no announcement can guarantee: the license in the next release.