About

We would rather be exact than impressive.

Koldheim is built by Kold Software. A small company that makes software which does one job, does it precisely, and gets out of the way.

Why we exist

Most approval software is sold on how much it can do. We think the useful question is narrower: when the request was approved, what was the budget, who signed, and can you still prove it a year later.

The standard

How we build

The standard Kold Software holds its own software to. Koldheim is held to the same one.

3 rules
01

Direct

Clear claims, clear constraints. We keep a written register of what may be said about Koldheim and what may not, and a sentence that is not in it does not ship. The list of what we will not claim is longer than most vendors’ feature lists.

02

Operational

Software is built around a real workflow: capture it, process it, export it. Every step is visible and its result is something you can use, rather than a status that only the system understands.

03

Precise

Specifics build trust. Crash-safe means fsync. Local means local. Isolated means a row-level security policy in the database that fails the build when it leaks. We hold the software to the word.

In practice

What that costs us, and buys you

Precision is a constraint before it is a feature. These are the four places it decides how Koldheim is built.

Every claim has a test behind it

A sentence on this site that describes what Koldheim does is traced to the code that does it and, where there is one, to the suite that proves it on every build. Copy without that trace does not ship.

A balance is a ledger, never a total

Budgets, leave and stock are movements with dates rather than numbers that get edited. It costs more to build and it is the difference between a figure you can read back and a figure you have to trust.

The record proves itself

The audit trail is append-only and hash-chained, one chain per organisation. Its end is emailed to your own managers weekly, and you can download the whole trail and check it on a page that runs on your machine, asking nothing of us.

A service is configuration, not a release

Records, steps, rules and stages are authored rather than written. That is why a new process is not a development project, and why changing a threshold does not join a queue.

The company

Who you would be contracting with

  1. Kold Software (Pty) Ltd registration 2026/236232/07
  2. Hilton, KwaZulu-Natal, South Africa where the company is run from
  3. Johannesburg where the application and its database run; backups are copied to Cape Town
  4. 9 services on one platform, one workspace, one sign-in, one audit trail

Small enough to answer the phone. Large enough to have written down what we will not claim.

Keep exploring

Where to next

See it with your own process.

Book a demo