We've launched a changelog

We’ve launched a public changelog, a running log of what’s changing in the Embed product and why it matters.

Changelogs are simple, but powerful. They offer a way to keep track of progress in real time through the steady rhythm of frequent improvements. For our customers and prospective ones, it’s a window into how we’re thinking, what we’re prioritizing and our commitment to being nimble.

But just as importantly, it’s for us.

Quoting from one of Paul Graham's famous essays that coincidentally our CEO Alex posted earlier this week

As with exercise, improvements beget improvements. If you run every day, you'll probably feel like running tomorrow. But if you skip running for a couple weeks, it will be an effort to drag yourself out. So it is with hacking: the more ideas you implement, the more ideas you'll have. You should make your system better at least in some small way every day or two.

First, it’s about transparency. We want our customers to have a clear view of what’s changing, what’s improving, and what we're fixing.

Second, it’s about discipline. Publishing changes forces us to ask: Are we shipping fast enough? Are those changes meaningful? It’s a simple way to keep ourselves accountable to a high-velocity, high-impact culture.

Finally, it’s a helpful record. Over time, it becomes a lightweight history of how the product is evolving, useful to customers who want to track progress, and to us as we reflect on how we’re growing.

We’ll be publishing updates every two weeks.

Each post will focus on 1–3 key highlights, followed by a concise list of new features, improvements, bug fixes, and any deprecations.

Most importantly, we're keeping it written by humans, for humans to enjoy reading. Simple, concise and only relevant updates.

Check it out at changelog.embed.co.