About kitset.io
Companies buy a system for hiring, a system for money, and a system for tickets. The work that
connects them ends up in a spreadsheet with one owner and no history.
That work is real and it is expensive when it fails. A subscription auto-renews for another year
because the cancellation window closed while the person who knew about it was on leave. Someone
leaves and keeps access to three systems for four months, because the offboarding checklist lived
in a document that nobody owned. A policy goes out and eleven months later nobody can prove who
read it. None of these are hard problems. They are just nobody's problem in particular.
kitset.io is built on the observation that these all have the same shape: a record, an owner, a
date, and evidence that something happened. Once you model that once, vendor renewals and
offboarding checklists and policy acknowledgements stop being eight different tools and become
eight views of the same thing — sharing one directory of people, one set of locations, one
permission model and one audit trail.
So the product is modular on purpose. You install the two or three modules that match the fire
you are currently fighting, and the rest are there when the next one starts. You are not asked to
migrate your whole operation to justify the licence.
How we build it
The failure case is the design case
Every feature is designed for the day someone asks what happened. That is why
acknowledgements are insert-only, why publishing a new version of a policy does not rewrite
the old evidence, and why quizzes are graded on the server.
Tested against the database we actually run
The full suite runs on PostgreSQL as well as SQLite. The first time it did, it found a column
overflow that passed every previous test and would have failed in production.
A fix is not done until the test goes red without it
Every security fix in the project has been reverted afterwards to confirm the test written
for it actually catches the bug. Twice that exercise found tests that quietly passed against
the defect they were written for.
We would rather say what is missing
The security page lists what kitset.io does not have as plainly as
what it does. You will find out eventually; better here than after you have bought it.
Have a look for yourself.
A workspace of your own, free for 30 days.