01 / YOU SHIPPED IT.
Control who's
running your app.
See every update
that didn't land.
Built for Electron apps today.
DEV BUILD SIGN RELEASE
FLEET
CONFIRMED ON v1.8.0
2,181 / 2,481
300 not yet confirmed
Example release · v1.8.0. Each mark represents a group of installations.
Inspect an unconfirmed installation02 / RELEASED ≠ RUNNING02 / RELEASED ≠ RUNNING
Released isn't
running.
A release tells you the artifact exists. Barrel shows where it actually went.
Example release · v1.8.0
03 / INTERROGATE THE GAP03 / EXPLAIN
Follow the
missing signal.
Select the gap. Inspect the evidence. Keep the unknowns visible.
Example release · v1.8.0
19 / NO RECENT SIGNAL
installation_9C02
Observed v1.7.4
Desired v1.8.0
NO RECENT SIGNAL
Signal absence is not a diagnosed cause.
Reported history: the download timed out.
14:02:00
Update offered
Desired v1.8.0
14:02:01
Download started
Binary requested
14:02:31
Download failed
Download timed out · ETIMEDOUT
No target-version confirmation reported.
Held back · Ineligible · Went dark
Eligibility decisions and missing signals are distinct.
Held back · Ineligible · Went dark
Eligibility decisions and missing signals are distinct.
04 / CONTROL THE NEXT OFFER04 / CONTROL
Change the
release's reach.
Change future offers. Releases already offered are not recalled.
NEEDS ATTENTION
19 WENT DARK / RELEASE v1.8.0
RAMP
60%
No releases are recalled.
GATE
OPEN
NEXT UPDATE CHECK
10,000 installations considered for future update offers.
6,000 / 10,000 eligible
Eligible at 60%
Outside ramp
RECORDED RELEASE RESULTS
2,181 confirmed / 2,481 attempted · 19 Went dark
v1.8.0 / NEEDS ATTENTION
19 went dark
RAMP
60%
GATE OPEN / FUTURE OFFERS
6,000 / 10,000 eligible
Changes apply to future update offers.
RECORDED RELEASE RESULTS
2,181 / 2,481 confirmed
300 unconfirmed · 19 went dark
05 / RELEASE HEALTH05 / RELEASE HEALTH
Signals become
a decision.
A computed release read, with the evidence still in view.
Example release · v1.8.0
- CONFIRMED
- 2,181 / 2,481 confirmed
- UNCONFIRMED
- 300 not yet confirmed
- WENT DARK
- 19 Went dark
Ramp 60% · Gate open
COMPUTED RELEASE HEALTHRELEASE v1.8.0
Needs
attention.Needs attention
19 installations went dark.
06 / INSIDE BARREL06 / REAL PRODUCT
The same model.
When you need details.
From the release, to the fleet, to an installation's reported history.
Example release · v1.8.2 · Channel: Stable
Snapshot: Oct 6, 2026, 12:09 PM
Release v1.8.2
Failed installation
a1f3b9c2
Installation ID
Update failed
Not enough disk space
Needs attention
900 installations have not reached v1.8.2.
92.4% of attempted installations reached the target version.
14 went dark · 23 failed · 798 pending · 65 other
Selected installation · a1f3b9c2
a1f3b9c2
Installation ID
Update failed
- Current version
- v1.7.9
- Desired version
- v1.8.2
- Platform
- macOS · arm64
v1.8.2
Oct 6, 2026
Update failed
Not enough disk space
Eligible for update
macOS on Apple silicon
Oct 6, 2026, 9:02 AM
Included in rollout
Included in the 25% rollout
Oct 6, 2026, 9:02 AM
Update available
v1.8.2 became available
Oct 6, 2026, 10:04 AM
Download started
Updating from v1.7.9 to v1.8.2
Oct 6, 2026, 10:07 AM
Update failed
Not enough disk space
Oct 6, 2026, 10:09 AM
Inspect the events reported by this installation.
07 / YOUR RELEASES STAY YOURS07 / TRUST
Your releases
are still yours.
Barrel gates releases and observes the fleet. Your binaries stay on your infrastructure.
YOUR RELEASE INFRASTRUCTURE
Binaries / artifacts
EXISTING RELEASE FEED
Existing updater
DIRECT BINARY PATH
Installation
BARREL
CONNECTED
Observe · evaluate
Gate · control
Metadata / policy / reported signals
Barrel attaches control and observation to the updater path.
Binary delivery never passes through Barrel.
SOLID / BINARY PATH · DASHED / POLICY + SIGNALS
08 / THE WHOLE SYSTEM08 / THE WHOLE SYSTEM
From release
to running.
Your release path, with the control and observation loop attached.
DEV BUILD SIGN RELEASE
YOUR BINARY / RELEASE FEED
EXISTING UPDATER
FLEET
BARREL
CONTROL PLANE
Observe Explain
Control Release health
The binary path stays independent.
The binary path stays independent.
09 / REQUEST ACCESS
INVITE-ONLY PRIVATE BETA
QUESTIONS / BEFORE YOU CONNECT
Before you connect.
Questions worth asking before your first release.
Something else on your mind?
Ask us directly
01What is Barrel?
Barrel is release and update-management infrastructure for desktop apps; it shows you who's running your app, what version, and why an installation isn't updating when it should be.
02Does this only work with Electron apps?
Yes, for now. Barrel supports Electron apps packaged with Electron Builder or Electron Forge. Other desktop frameworks aren't supported yet.
03Do I have to give Barrel my binaries, or move my update feed to you?
No. Barrel never hosts or touches your binaries; you keep your own update feed and distribution infrastructure exactly as it is today. Barrel only records metadata about releases and installations, never custody of the files themselves.
04Can Barrel actually control who gets an update, or does it just observe?
Both. Beyond observing rollout health, you can hold a release instantly if something's wrong, or ramp it out to a fixed percentage of your fleet. The SDK itself enforces that in your app, so the control actually takes effect.
05Is the SDK open source?
Yes. The SDK that runs inside your app is open source, so you can see exactly what it does and doesn't send. The dashboard and backend are not.
06How do I get access, and what does it cost?
Barrel is currently a private, invite-only beta. We're building out the full beta now; pricing will be published once it's ready.
07What data do you actually collect, and can I delete my account?
Barrel collects installation-level update data (OS, version, whether an update succeeded). It never collects your end users' personal data, and no IP addresses are stored. You can delete your account and its data at any time.
08What happens if I want to stop using Barrel?
You can leave cleanly at any time. Since you always keep your own update feed, removing Barrel is just deleting one init() call; your installations and update mechanism are completely unaffected.
09Is Barrel ever a single point of failure for my releases?
No. Barrel is designed so your installations never depend on it staying up. If it's ever unreachable, your app keeps running on its last known update state, and your own update feed and distribution infrastructure stay fully in your control the whole time.
