It does what the page says
Feature lists describe the software that exists today, not the software on the roadmap. If it is not built, it is not listed.
Software, built to specification
We build tools that meet the requirement, pass the review, and then get out of the way. No transformation. No journey. The feature works, the invoice is correct, and the uptime is the number we told you it would be.
One product, in development · No trial yet · No sales call ever
| Item | State |
|---|---|
| kolvi/core | In development |
| kolvi/docs | Not started |
| midapps.app | Online |
| status page | Not needed yet |
This is our actual status. It will get more interesting.
In practice
Feature lists describe the software that exists today, not the software on the roadmap. If it is not built, it is not listed.
Unremarkable architecture, documented decisions, and a security questionnaire that contains no surprises for either of us.
Fewer features, maintained for longer. We would rather support a small product well than a large one eventually.
By the numbers
Uptime is a target we have committed to, not a measurement we are quoting back at you. When there is a year of history, this will say so.
We will write to you once, on the day it ships. That is the whole programme.