September 2026 in numbers: what we measured and what went wrong
Once a month we write down what the platform did, in numbers we measured ourselves, and what broke along the way. This is the first one, covering the build-up from 13 to 22 September 2026. Nothing here is a projection.
What we measured
| What | Number | How |
|---|---|---|
| Cold start of an app that scaled to zero | about 22 seconds for a fresh Next app | timed on the App plan; the promise on the pricing page says 10 to 30 |
| Uptime check of every hosted site | every 5 minutes | the monitor that feeds the status page |
| Question pages published | 23 questions, 138 pages in six languages | the new Questions and answers category |
| Addresses reported to IndexNow | 516 in one submission, answer 200 | after the release of the question pages |
| Vulnerabilities in the platform's dependencies | 5, of which 1 set critical, then 0 | npm audit before and after the upgrade to Next 16.3.5 |
| Commits scanned for leaked secrets | 429, none found | the security round in CI |
| Exams of the agent roles | support 10/10, trust 10/10, customer success 10/10, security 10/10 | each role sits ten exam tasks before it goes live |
| Backups | every night, kept 90 days, checked the same night | the platform copy and, since 22 September, every customer database |
What it costs
The prices did not move: a site is € 10 a month, an app with a database € 15, Platform € 10 plus usage with a spending cap of € 50 by default. No VAT is added. An extra standard domain is € 1 a month and free for the first six months; "Always on" for an app is € 9.
What went wrong
- A pull request was merged before its CI check had registered, so it went in untested. The rule since then: wait until the check exists, then wait for green, and never chain the merge behind it blindly.
- The own error page at the edge did not catch the cloud provider's "unavailable" response at first, because that response carries no server header. It now detects our own headers instead: no headers from us means the platform did not answer.
- The contact form module worked on trial addresses but refused submissions on a customer's own domain. Found while writing the question page about email, fixed the same day.
- The article about cold starts said keep-warm was only available on Platform, while the "Always on" add-on for the App plan had existed for two weeks. Corrected in six languages.
- The first live question to the new chat assistant got the wrong article, because the search ranked the longest text instead of the best match. Stop words and prefix matching fixed that a day later.
The first share-of-voice numbers
On 22 September we asked the 23 questions, in Dutch and in English, to Perplexity and to Copilot Search, anonymously, and wrote down who gets named. Dorelli Cloud: named in 4 of 92 answers, all four on the one question that has our name in it, and three of those four got our facts wrong because no page of ours had been indexed yet. On the other 44 questions we do not appear at all. Vercel was named 28 times, Hostinger 19, Render 15, Netlify 14. Twenty-four answers named no host whatsoever. That is the baseline; next month's article will show whether the question pages moved it.