Skip to content

Built to not lose anything

Kacky is a record book. If it loses your times, it is broken. So a lot of the work that never shows up on screen went into making sure that it does not. This is what protects your data.

Only trustworthy times count

Ranks and world records are built only from trusted online records. Times that came in offline, or that were imported from Kacky's older systems, are kept out of the rankings on purpose. Nothing unverifiable can ever claim a record it did not earn. This is the single most important rule on the platform, and it has its own page.

No finish is ever lost

Your finish is not a fragile message. A fragile message is gone the moment nobody is listening. Your finish is a durable one that waits in a queue until the backend reads it.

A backend that is down or mid-deploy works through the backlog after it comes back. A finish that still slips through can be added back by hand, because the controllers keep a log of every finish.

The full mechanism is on How the game talks to the platform.

The whole database, backed up three ways, every night

The database holds all of Kacky's history. Every night it is copied to three separate places: the dev environment, off-site storage at Hetzner, and a physical disk on an admin's own machine. All three must fail at once for Kacky to lose its history for good. The backend and the data lists what each copy is for.

Servers that look after themselves

The backend watches for each server's regular check-in. More than five minutes of silence and the backend marks that server offline automatically, so the site never shows a dead one as live. If a machine ever dies for real, it is not a crisis. The whole fleet is described in code, so a replacement is a seven-minute rebuild, not a lost weekend.

You never think about any of this

That is the point. The record of every run you ever did is meant to outlive any single crash, deploy, or dead server. The reliability is the part you are not supposed to notice.