Release management for product teams
Ship with
the lights on.
Loomvane turns every release into a controlled rollout: feature flags, staged exposure, live health signals and a changelog that writes itself.
Free for 2 projects. No credit card required.
Rollouts
Production · 12 active · 1 paused
New rollout
Active rollouts
12
+3 this week
Error budget
99.94%
0.02% consumed
Avg. exposure
37%
across 12 flags
Auto-paused
1
needs review
Error rate vs exposure — checkout-v3
00:00
06:00
12:00
18:00
now
Activity
2m
checkout-v3 advanced to 50% — p95 latency within budget
19m
pricing-page-b auto-paused: conversion drop beyond guardrail
1h
Release notes drafted for v4.12 from 8 merged PRs
3h
invoice-pdf-v2 scheduled for Tuesday 09:00 UTC
Flag
Status
checkout-v3
Healthy
search-reranker
Complete
pricing-page-b
Paused
invoice-pdf-v2
Scheduled
onboarding-tour
Healthy
Teams that ship every week use Loomvane
Ashgrove
Kestrelworks
Fennel & Co
Hollowbrook
Pinewire
Marrowline
Oakstead
Tidewell
What you get
Everything between “merged”
and “it is live”.
Most teams stitch this together from four tools and a Slack channel. Loomvane is one workflow with one audit trail.
Flags · prod
3 of 41
checkout-v3
MR
expires in 21d
search-reranker
JT
expires in 6d
invoice-pdf-v2
LK
scheduled
Flags that know their owner
Every flag carries an owner, an expiry and a rollout plan, so nothing is left on at 100% for a year.
error_rate
0.9% · guardrail < 1.2%
Healthy
p95_latency
388 ms · guardrail < 420 ms
Healthy
conversion
-4.1% · guardrail > -2.0%
Paused
Rollouts with guardrails
Set the metric and the threshold. If error rate or conversion crosses the line, exposure pauses on its own.
checkout-v3 · step 3 of 5
last 6 h
Exposed · 25%
0.9%
error rate · 41k sessions
Control · 75%
1.1%
error rate · 123k sessions
−0.2 pts
difference · 95% range −0.4 to 0.0 · not a verdict
Signals next to the switch
Latency, errors and conversion for the exposed cohort, side by side with the control group.
Draft
v4.12 — Guardrails on custom metrics
New — any event can be a guardrail
Improved — flag search matches owner initials
Fixed — DST shift on scheduled steps
drafted from 8 merged PRs
Publish →
A changelog that writes itself
Merged pull requests become a draft release note. Edit the tone, not the facts.
checkout-v3 · prod · 50% exposed
Roll back the flag
no redeploy · no pipeline
≈ 30 s
last rollback
12 days ago · pricing-page-b
One-click rollback
Roll back the flag, not the deploy. Thirty seconds, no pipeline, no pager.
ML
Mara L.
Product
schedule
TA
Teodor A.
Engineering
wire + rollback
CM
Clara M.
Support
read
Built for the whole team
Product managers schedule, engineers wire, support reads. Same page, different permissions.
How it works
Three steps from merge
to one hundred percent.
$ loom flag create checkout-v3 --owner mr
created flag checkout-v3 (off)
expires 2026-11-09 · env prod, staging
01
Wrap the change in a flag
Add a flag with the SDK or the CLI. Default off, owner set, expiry in 30 days.
$ loom rollout start checkout-v3 --steps 1,5,25,50,100
guardrail error_rate < 1.2%
guardrail p95_latency < 420ms
02
Roll out to 1%, then more
Pick a schedule or advance by hand. Guardrails watch the cohort while exposure grows.
step 3/5 · 25% · healthy
error_rate 0.9% · p95 388ms
next step in 02:14:09
03
Watch signals, not Slack
The rollout page shows what changed for the exposed users. Release notes are drafted when you hit 100%.
In practice
Fewer late nights,
shorter incident reports.
~40
min
Typical time from merge to first 1% exposure (demo figure)
30
s
Flag rollback, no redeploy (demo figure)
1
page
Flags, rollouts, signals and notes in one place
“We stopped arguing about whether a release was “done”. The rollout page is the answer, and everyone can read it.”
ML
Mara Lindqvist
Head of Product, Kestrelworks
“The auto-pause caught a conversion drop at 12% exposure. That used to be a Monday-morning discovery.”
“Our changelog used to be written on Friday afternoon from memory. Now it is drafted before we finish the rollout.”
PN
Priya Natarajan
Engineering Manager, Pinewire
Pricing
Start free.
Pay when you ship more.
Three plans, one feature set that grows with the team. Yearly billing saves two months.
Compare all plans
Questions
Things people ask
before they switch.
Does Loomvane replace our CI/CD pipeline?
No. Your pipeline still builds and deploys. Loomvane controls who sees the change after it is deployed, and what happens if it misbehaves.
Which languages have an SDK?
The demo lists JavaScript, TypeScript, Go, Python, Ruby, Java and Swift. Replace this answer with the list for your own product.
What happens when a guardrail trips?
Exposure is paused at the current step, the owner is notified in the channel they chose, and the rollout page shows the metric that crossed the line.
Can we self-host?
The Scale plan includes a self-hosted option with the same feature set. Contact sales for the deployment guide.
How is pricing counted?
By seats and by monthly tracked users. Flags, rollouts and environments are unlimited on every plan.
See a rollout
run end to end.
Twenty minutes with the team. We will use your release process, not a slide deck.