Omlet is going open source

I have some important news to share about Omlet:

We've decided to wind down Omlet as a business. Going forward, we’re open sourcing it — the full thing.

Here's what that means for you, and why we made this call.

Why?

When we built Omlet, we believed (and still believe) that design system teams deserve a clear, objective picture of how their components are used in production. Gut feelings, surveys, and discussions on Slack are all valuable, but they can only tell you so much when making the hard decisions.

Our belief hasn’t changed. What changed is our understanding of the market.

Teams like GoFundMe, Mercury and many others, have been with us and pushed us to build a better product. But after a while, we started noticing a pattern: every team's approach to component adoption analytics is a little different. Some care about adoption rates across repos. Some are laser-focused on prop usage. Some want to track legacy component cleanup. Some want all of the above, but wired up in their own specific way.

That variety is what makes Omlet interesting — but supporting it properly would require a level of customization that just wasn't sustainable for us as a business.

So we asked ourselves: what's the most useful thing we can do for the design system community here?

The answer was pretty clear.

We're open sourcing Omlet. All of it, under an MIT license.

If you're a current paid customer, nothing changes for your workspace today. We will continue to host and support the cloud version of Omlet through the end of your current subscription period.

As you approach your next renewal, we’re encouraging all teams to migrate to the self-hosted version. That said, if you need to stay on the hosted version for a longer period, we’re committed to supporting you — just reach out, and we’ll work with you to ensure your team has what it needs.

If you're new to Omlet, you can now self-host it for free. The features are the same as the paid version: component analytics, adoption tracking, the dependency tree, custom charts, all of it. And the VS Code extension works locally as it always has, so nothing changes there either.

Because it’s open source, you can also actually make it your own. If your team has a specific way you want to look at adoption data or a custom integration you've been wishing for, now you can build it. And if you want to contribute it back, we'd love that.

I genuinely think this is a better outcome than just winding Omlet down. The problem it solves is real, and design system teams still need it. Now you just have more control over how you use it.

Get started

• Self-host Omlet: github.com/zeplin/omlet
• Questions? Ping us: support@omlet.dev

If you want to contribute, report a bug, or just poke around — we’d love your contributions.

Thanks for all the support you’ve shown Omlet. I personally enjoyed working on it as a designer, and we all learned a ton from the teams who used it. Maybe now that it's out in the open, it’ll end up helping even more teams than it would have otherwise.

Pelin