Flume

About Flume

The whole idea
is in the name.

Most HR software is six systems that agree to disagree — a biometric export, a roster spreadsheet, a payroll file, a folder of contracts — each with its own version of what happened. Flume is one continuous system instead, and it is named for the reason it works: a fact recorded at the gate travels a single, walled channel all the way to a number you can defend, without ever being rerouted, topped up or quietly lost along the way.

The channel a punch travelsgate → ledger
PunchTerminal
ReconcileClose-out
ApproveMulti-tier
CalculateComponents
DisbursePayslip
DefendFull lineage

What Flume actually is

Not a dashboard bolted onto your spreadsheets. One record, read from six angles.

Attendance, payroll, performance, training, lifecycle and culture are usually six purchases that a nightly sync tries to reconcile. In Flume they are six views over one employee record, so there is nothing to keep in sync in the first place.

Record

A fact is written once, by whatever witnessed it.

A punch, a leave request, a payroll adjustment — each is captured once, by the terminal, the person or the approval that actually saw it happen, and never silently rewritten after the fact.

Reconcile

Corrections add to the record. They don’t erase it.

When something needs fixing, Flume appends a new entry with an author, a timestamp and a reason. The entry it replaces stays exactly where it was — superseded, not deleted.

Trace

Every number on a payslip walks backward.

Open any figure and it leads to the run, the approval, the reconciled day and the original punch behind it — the same path a fact travelled, open to walk in reverse at any time.

Where the name comes from

A flume is a channel, not a pipe.

The word predates software by centuries — it is the term for an engineered channel that carries something along a controlled course. That is the whole thesis of the product, so it earned the name rather than being picked for how it sounds.

flumerhymes with “room”noun

An artificial channel — built, walled and graded — that carries water or material along a controlled course from a source to a destination. Historically used by loggers and millers to move timber and ore downhill for miles without losing a load along the way: the same route every time, visible and walled the entire distance down.

Not a river

A river finds its own course. A flume is built.

Left alone, water finds the easiest path and floods whatever is in the way. A flume is the opposite of that by design — the same walled route every time, so what goes in at the top is what arrives at the bottom.

Not a pipe

A pipe is opaque. A flume is open the whole way down.

What happens inside a pipe is a guess. A flume is open along its length — you can watch anything travel it, stop at any point, and see exactly what is passing through. That is the audit trail, built into the shape of the word.

It is also why the product’s primary accent — the colour on every call to action, every active state, every line in the chain diagrams across this site — is named “flow” in the code that renders it. One idea, carried through the interface the same way it is carried through the product.

Book a demo

Bring us your messiest month.

The fastest way to judge Flume is to run it against a period you already argued about. Send a month of punches and the payroll you produced from it, and we will show you the same month reconciled — including what the anomaly detectors flag.