Skip to content

Open numbers

Everything we do after the deploy, counted.

Every advisory we track, every patch we roll out, every deploy, backup and euro. Updated daily from the platform itself; small numbers included, because that is where we are.

Updated 5 Oct 2026, 11:00 UTC Public beta since 9 Sep 2026 Raw JSON ↗

119,855
security advisories tracked
+30,781 in 30 days
16
deploys in the last 30 days
81.2% succeeded
€5
monthly recurring revenue
1 paying customer

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

Too early for a median. Every security figure here counts completed fleet-wide work that is at least seven days old, and the first fixes have not aged past that yet. The number appears on its own once they have.

Advisories tracked per week OSVCISA KEV
20 Jul5 Oct

1.7% actively exploited

Recent fleet-wide fixes7-day delay

Nothing to list yet. The log shows fixes applied a week or more ago, so the first rows appear once a fix has aged past that.

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.

  1. 18 Jul 2026

    Kernel 6.12 → 6.18 LTS

  2. 4 Jul 2026

    NixOS 25.11 → 26.05

  3. every day

    package and security updates, 47 rebuilds since July, 0 fleet-wide rollouts in 30 days

4
servers managed
2 customer · 2 internal
95.7%
rebuilds succeeded, 30d
47 rebuilds · 0 rolled back on their own since 3 Oct 2026
100%
reachable by our monitoring, 30d
2 servers

Deploys

Push a commit; this is what happens next.

Deploys per week81.2% success
20 Jul5 Oct
0
rollbacks, 30d
0
preview environments
0 closed on merge · 0 idle, 30 days
1
team reached a first deploy
since 1 Oct 2026

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.

€5
monthly recurring revenue
list price × applications · excl. VAT
1
paying customer
€5
revenue to date
0
churned, 30d
Signup → payingall time
Signed up 2
Added an app 2
Went live 2
Paying 1
Where signups came from30d
Other (<3 each) 1

Building in public

How the platform itself is made.

66
releases shipped
12,052
tests on every change
190
changelog entries
76
docs pages
68
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