Kinetiq — Motion, calibrated.

Waylight · how we decide

Four rules, and what each one costs us.

These settle arguments internally. We publish them so you can hold us to them, and so you can tell when we have broken one.

The gate before the office
Every feature is designed for the person standing outside in the weather first, and adapted for the desk afterwards. Never the other way round.
What it costs us
Office reporting is plainer than our competitors', and that is a choice, not a backlog item.
A plan that cannot explain itself is not published
The scheduler withholds any board whose reasoning it cannot state, and flags it for a person instead.
What it costs us
About one morning a fortnight arrives with a flag rather than a plan.
Leaving is a workflow
Export everything, any time, without asking. Cancellation is a settings page, not a phone call.
What it costs us
We lose accounts we could have kept by making them hard to leave.
Small enough to name
You should always be able to find out who made a decision about the product you rely on.
What it costs us
It caps how fast we can grow, which we have decided we can live with.

Waylight · plain definitions

We are precise about these because the precision is the product. Where our word differs from the usual one, the usual one is printed beside it.

BoardElsewhereSchedule, plan, run sheet: One yard's plan for one shift, cut at a moment in time and never edited afterwards. A change produces a new board, not a revision of the old one.
CutElsewhereGenerate, publish, build: The act of producing a board from the constraints as they stand. Boards are cut, not generated — the word is deliberate, because a cut has a moment and an author.
ConstraintElsewhereRule, restriction, business logic: Anything that limits what a board may contain: crane windows, crew rest, tide, or a hold a supervisor entered by hand. Constraints are visible on every board they shaped.
ReshuffleElsewhereRe-plan, update, revision: A re-cut caused by something changing mid-shift. It names its cause, and it propagates to every board sharing the constraint that moved.
The recordElsewhereAudit log, history, event store: The append-only history of every board cut and every override entered. It is the thing audits are answered from, and nobody — including us — can quietly edit it.

Waylight · where we are

We hire where the yards are. That gives us most of the working day covered without asking anyone to answer at three in the morning.

06:00 – 24:00 UTC covered by someone on shift

1212in total

00:00 to 06:00 UTC, nobody is working. Urgent pages wake an on-call engineer; everything else waits for Rotterdam.

Waylight · who does what

Your side of this is about an afternoon in total. We have marked which steps are ours so you can hold us to them.

YouWaylightOur team

01 · You
Name one yard and its crews
Three questions on a form. No integration, no data export, no meeting.
About ten minutes
02 · Waylight
A first board is cut
From what you named plus public tide and weather. It will be roughly right and visibly incomplete, which is the point.
Under a minute
03 · You
Correct it once, in front of us
You tell us what the board got wrong. Every correction is a constraint the scheduler did not know about.
One afternoon
04 · Our team
We wire the constraints in
Crane windows, crew rest, and the local rules nobody writes down. This is the part we do, not you.
Two or three days
05 · Waylight
Mornings cut themselves
The board arrives before the gate opens, with its reasoning attached, every day.
Ongoing
06 · You
Take the whiteboard down
Whenever you are ready, and not before. Most yards leave it up for about a month.
Your call

Waylight · where it sits

One row per thing we hold. If a row says nobody, it means nobody — including us, without a ticket you opened.

DataWhere it restsKept forSeen by

Boards and plans
Rests in · Frankfurt (eu-central)
Kept · Indefinitely, yours to delete
Seen by · Nobody
Crew names and shifts
Rests in · Frankfurt (eu-central)
Kept · 24 months after a yard closes
Seen by · Nobody
Support attachments
Rests in · Frankfurt (eu-central)
Kept · 90 days
Seen by · Support, on your ticket
Billing records
Rests in · Ireland (eu-west)
Kept · 7 years, by law
Seen by · Payment processor
Error traces
Rests in · Frankfurt (eu-central)
Kept · 30 days
Seen by · On-call engineer

Thirty days' notice before anything joins this list, by email, whether or not it affects you.