Open numbers
Everything we do after the deploy, counted.
The server work, in public: advisories tracked, fixes applied, upgrades and backups, alongside deploys and revenue. Updated daily from the platform itself; small numbers included, because that is where we are.
Updated 19 Nov 2026, 00:32 UTC Public beta since 9 Sep 2026 Raw JSON ↗
Security
The promise, measured in public.
We match every advisory against what our servers actually run, approve the fix, test it on one server, then roll it out to the rest. This is how long that takes, counting only fixes applied a week or more ago.
Fixes applied a week or more ago · from fix available to patched
median of 3 fleet-wide fixes, last 90 days · early read
p90 12.9h promise 24h every fix within 24h for 42 days running
- 18
- advisory fixes across our fleet
- 3
- fleet-wide fixes rolled out
- 0
- actively exploited, fixed
0.6% actively exploited
- caddy 2.11.7 → 2.11.8 patched in 12h 52m 1 server 5 advisories
- php 8.4.26 → 8.4.27 patched in 1h 56m 1 server 2 advisories
- php 8.4.25 → 8.4.26 patched in 9h 30m 4 servers 11 advisories
Fleet
Servers we look after, and how current they are.
Customer servers, plus the ones running strackt itself, listed separately. Upgrades nobody had to book an afternoon for.
as of 11 Nov 2026
-
18 Jul 2026
Kernel 6.12 → 6.18 LTS
-
4 Jul 2026
NixOS 25.11 → 26.05
-
every day
package and security updates, 125 rebuilds since July, 12 fleet-wide rollouts in 30 days
Deploys
Push a commit; this is what happens next.
Money
The business, in euros.
Small, and published anyway. If you are deciding whether to trust a one-person company with your servers, this is part of the answer.
Building in public
How the platform itself is made.
- 138
- releases shipped
- 26,659
- tests on every change
- 286
- changelog entries
- 82
- docs pages
- 69
- months of The Log
What we do not publish
Transparent, not careless.
Nothing an attacker could use
No live counts of unpatched servers, no "N servers on version X". Security figures show what is fixed, with a 7-day delay.
No single customer
Nothing per team, ever. Signup sources with fewer than three signups are grouped as "other".
How the numbers are made
Computed once a day from the platform's own records; internal teams excluded unless labelled. The raw JSON is public too.
GET https://app.strackt.io/api/public/stats
The machines that run strackt.
At least 15 servers work together to power strackt. The dashboard, background work, builds, caches, secrets and monitoring have separate roles, joined by a private network.
That separation gives the platform room to grow. As demand increases, we can add workers and service capacity independently. The work behind your app can grow without putting every job on the dashboard’s machine.
The secrets vault and the private network’s meeting points already run on more than one machine. The dashboard, workers and database each run on a single machine today. Your app serves traffic directly from your own servers; it keeps serving if the strackt dashboard is unavailable.