Why we publish a public changelog
Most event platforms ship updates and hope you don't notice. The UI shifts. A button moves. A workflow changes. You find out when something you relied on stops working the way it did yesterday. Maybe there's a release note buried in a help centre somewhere. Maybe not.
We publish a public changelog with every release. Every feature, every fix, every change — documented and visible. It's a small thing, but it says a lot about how a company operates.
Accountability you can read
A public changelog is a record. It shows what we're actually working on, not what a roadmap slide says we might get to someday. You can see whether we're shipping fixes, adding features, or going quiet for months.
That's uncomfortable for a lot of software companies. Silence is easier. If you don't document what changed, nobody can point out that you spent three months on internal refactoring while a bug sat open. Nobody can ask why a promised feature hasn't appeared.
We'd rather have that accountability. If we go a week without shipping, you can see it. If we fix something that was broken, you can see that too. The record is honest because it has to be.
No silent changes
When a platform changes something without telling you, it creates a specific kind of frustration. You're not angry about the change itself — you're angry that nobody told you. You question what else changed that you haven't noticed yet. Trust erodes in small, quiet increments.
A changelog fixes that. When we change how a feature works, it's documented before you encounter it. You can read what's different and why. No surprises, no guessing, no "did this always work this way?" conversations with your team.
A feedback loop that works
Publishing changes publicly creates a natural feedback loop. When you can see exactly what shipped, you can tell us exactly what's wrong with it. "The new filter on the exhibitor list doesn't account for multi-day booths" is a more useful conversation than "something feels off."
It also means you can tell us when something's right. Knowing which changes land well helps us make better decisions about what to build next.
Proof the product is alive
Event teams evaluating software have a reasonable concern: is this platform actively developed, or am I buying into something that shipped its last meaningful update two years ago?
A public changelog answers that question instantly. You don't need to take our word for it. You don't need to ask a sales rep. You can look at the record and see for yourself — what's shipping, how often, and whether the product is moving forward.
It's a small thing
A changelog isn't a feature. It doesn't close deals or show up on comparison charts. But it signals something about how a company thinks about its relationship with the people who use its product.
We think you should know what's changing in the tools you depend on. That's it. No deeper philosophy required.