About
A small team
with a strong opinion.
We think releasing software should feel routine. Loomvane is the tool we wanted when it did not. Demo copy — replace with your own story.
Why we exist
Releases should be
a non-event.
Every team we have worked on had a release ritual: a channel, a checklist, a person watching dashboards at an odd hour. The ritual exists because the tools separate the switch from the signal. We put them on the same page.
$ loom status
12 rollouts healthy · 1 paused · 0 incidents
last release note drafted 19 minutes ago
How we work
Four rules
we will not trade away.
Team
People behind
the product.
Six people, three time zones, one rule: every change goes out behind a flag. Fictional team for the demo.
IV
Ida Vestergaard
Co-founder, Product
SH
Samir Haddad
Co-founder, Engineering
NA
Noor Abbasi
Design
FB
Felix Brandt
SDKs and platform
YT
Yuki Tanaka
Signals and data
CM
Clara Moreau
Customer engineering
Timeline
From internal tool
to public changelog.
Started as an internal tool for a team that shipped daily and paged weekly.
First external teams. Guardrails and the auto-pause shipped after a rollout went wrong at 40%.
Signals with control groups, drafted release notes and the public changelog.
Come and see
a rollout run.
Twenty minutes with an engineer. Your release process, not a slide deck.