Open metrics
The numbers, live.
Every figure below comes out of our production database, through a public API that anyone can call without a key. The page reads it again every minute; the API refreshes it every ten. We publish these because trust should be checkable, and a number you cannot verify is just a claim.
Headline platform numbers
1,788
Deployments
2,658 min
Build minutes
46.2 GB
Bandwidth served
242
Teams
Instruments
Builds run
1,788
Deployments that actually started a build. Queued rows waiting for a runner are not counted.
Projects
114
Sites connected to a repository or set up for direct uploads.
Verified domains
45
Customer domains that passed verification and are serving traffic today.
Build success rate
81.2%
Over 1,783 builds that reached an outcome. Builds a customer cancelled are left out, which flatters this number a little.
Median build
40s
Mean is 1:22 min, over 1,442 builds that finished and recorded both timestamps. Failures are excluded: a failure measures how long we took to give up.
Form submissions
23
Messages delivered through deploybase forms. Spam is quarantined and never counted here.
Branch previews
80
Branch previews built and given a URL of their own.
Building right now
0
Nothing is building at the moment this snapshot was taken. Quiet is a real reading.
The shape of it
Weeks start Monday, UTC, and run from our first deployment to this week. A flat week is a quiet week, not a missing one. Cancelled builds are in the tooltip and the table below, not in the columns.
Usage is metered per billing period, which is the finest grain we have. Each period is counted whole, in the month it starts, so these two charts are monthly where everything else is weekly. Nothing is split across buckets to make a smoother line.
Raw numbers
The same values the charts are drawn from. If a bar looks wrong, this is where you check it, and the endpoint below is where you check us.
| Week of | Deployed | Failed | Cancelled | Forms | Previews |
|---|---|---|---|---|---|
| 2026-02-09 | 13 | 1 | 0 | 0 | 0 |
| 2026-02-16 | 2 | 0 | 0 | 0 | 0 |
| 2026-02-23 | 0 | 0 | 0 | 0 | 0 |
| 2026-03-02 | 0 | 0 | 0 | 0 | 0 |
| 2026-03-09 | 4 | 1 | 0 | 0 | 0 |
| 2026-03-16 | 3 | 4 | 0 | 0 | 0 |
| 2026-03-23 | 3 | 0 | 0 | 0 | 0 |
| 2026-03-30 | 3 | 0 | 0 | 0 | 1 |
| 2026-04-06 | 7 | 5 | 2 | 0 | 0 |
| 2026-04-13 | 1 | 0 | 0 | 0 | 0 |
| 2026-04-20 | 1 | 0 | 0 | 0 | 0 |
| 2026-04-27 | 1 | 4 | 0 | 0 | 0 |
| 2026-05-04 | 4 | 2 | 0 | 0 | 0 |
| 2026-05-11 | 1 | 0 | 0 | 0 | 0 |
| 2026-05-18 | 3 | 0 | 0 | 0 | 1 |
| 2026-05-25 | 4 | 0 | 0 | 0 | 0 |
| 2026-06-01 | 15 | 9 | 0 | 0 | 1 |
| 2026-06-08 | 6 | 0 | 0 | 0 | 0 |
| 2026-06-15 | 7 | 6 | 0 | 0 | 0 |
| 2026-06-22 | 1 | 0 | 0 | 0 | 0 |
| 2026-06-29 | 48 | 5 | 1 | 0 | 6 |
| 2026-07-06 | 15 | 6 | 1 | 0 | 0 |
| 2026-07-13 | 15 | 1 | 0 | 0 | 0 |
| 2026-07-20 | 14 | 2 | 0 | 0 | 1 |
| 2026-07-27 | 6 | 2 | 0 | 4 | 0 |
| 2026-08-03 | 22 | 8 | 0 | 1 | 0 |
| 2026-08-10 | 18 | 15 | 0 | 0 | 0 |
| 2026-08-17 | 269 | 24 | 1 | 3 | 5 |
| 2026-08-24 | 153 | 19 | 0 | 3 | 4 |
| 2026-08-31 | 251 | 35 | 0 | 2 | 9 |
| 2026-09-07 | 381 | 76 | 0 | 4 | 41 |
| 2026-09-14 | 175 | 111 | 0 | 6 | 11 |
| 2026-09-21 | 1 | 0 | 0 | 0 | 0 |
| Month | Bandwidth (GB) | Build minutes |
|---|---|---|
| 2025-09-01 | 0.00 | 0 |
| 2025-10-01 | 0.00 | 0 |
| 2025-11-01 | 0.00 | 0 |
| 2025-12-01 | 0.00 | 0 |
| 2026-01-01 | 0.00 | 0 |
| 2026-02-01 | 0.00 | 21 |
| 2026-03-01 | 0.82 | 48 |
| 2026-04-01 | 0.00 | 6 |
| 2026-05-01 | 0.01 | 124 |
| 2026-06-01 | 0.77 | 109 |
| 2026-07-01 | 11.70 | 93 |
| 2026-08-01 | 20.73 | 919 |
| 2026-09-01 | 12.16 | 1338 |
Check our math
curl https://api.deploybase.eu/api/v1/public/stats
{
"deployments_total": 1788,
"builds_total": 1788,
"build_success_rate": 0.8116,
"generated_at": "2026-09-21T06:28:43.121066582Z"
}Four fields of the real reply, taken from the same snapshot this page is built on. The endpoint returns every number above, including the weekly and monthly series.
On the runway
- Queued Build times per framework, once enough builds have recorded a framework for the figure to mean anything.
- Queued Uptime and response times for the API itself, so our own reliability sits on the same page as everything else.
No dates on any of these. They are what we are working towards, not a commitment, and this list is here so you can hold us to the direction.
Why this page exists
I put this page up because I think the internet gets better when companies show their work. Transparency builds trust and helps customers understand the product better. Most companies do not share anything, and when they do share, it is for their stakeholders, not the actual people who use the product.
The numbers here come from the same place I look every day: the database that serves the product. You will see exactly what I see, and hopefully, together, we can build a more transparent internet.
Antoine, founder