Fieldline
Nineteen a seat. That is the whole page.
One plan, every feature, no call required. The rest of this page is us showing our working — you already know what it costs.
- Every instrument, no tiers
- Unlimited yards and crews
- Full history and exports
- Support from people who ran yards
$1919
per seat / month
Billed monthly, cancel from the settings page, exports work after you leave.
Fieldline · the arithmetic
Where your nineteen dollars goes.
We would rather show the split than defend the number. These are rounded, and they move by a point or two each quarter.
$1919per seat / month
People who answer
41%
Support and field staff who have run a yard, on shift from five in the morning.
Building it
29%
Six engineers and a designer. No growth team, because there is nothing to grow yet.
Running it
18%
Servers, backups, and the second region that exists purely so an outage is boring.
Keeping the lights on
12%
Accounting, insurance, and the audits our customers make us pass.
Rounded to whole points, so the column may read a point off the price. Updated each quarter from the same ledger our accountants use.
Fieldline · fit
Who this is for, and who it is not.
Both lists are real. The second one cost us three deals last year and saved us six refunds, which we consider a good trade.
Built for
Teams who want the price before the call
It is on the first screen, and the second screen shows where it goes. Nothing below contradicts either.
Anyone who has been burned by a quote
One number, no seats-versus-usage arithmetic, and no discount that expires if you think about it.
Buyers who read the incident log first
Ours is published in full, including the fortnight we would rather forget.
Not for
Anyone needing a bespoke contract
We have one agreement and we do not redline it. That is what keeps the price the price.
→ You want a vendor with a legal team, and that is fine.
Procurement that requires three quotes
We will not pad a number so yours looks competitive against it.
→ Put us in as the fixed-price option.
Teams who want the roadmap in writing
We publish what shipped, not what might. A roadmap we could promise is one we would break.
→ Read the changelog and judge the pace.
If you are on the right and think we are wrong about you, say so — we have been wrong before, and we would rather hear it now than after you have paid.
Fieldline · what it does
Six things, stated plainly.
No demos in this section. If any of these matter to you, the rest of the page shows them working.
One record
Every yard writes to the same lineage, so there is never a second version of the morning.
Plans that explain themselves
Each board carries the constraints it was cut under, in language a crew reads at a gate.
Changes that propagate once
A reshuffle updates every board that shares the constraint. Nobody re-keys anything.
Built for gloves
Large targets, high contrast, and nothing that needs a second tap to confirm.
Exports that hold up
Audits are answered from files, not screenshots, and the files carry their own provenance.
Leaving is a workflow
Your history is yours. Export it whole, on your own schedule, without asking us.
Fieldline · 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.
Fieldline · what went wrong
Every incident of the last year.
Written by the person who fixed it, published whether or not anyone noticed. If this list were empty we would not expect you to believe it.
- 33
- incidents, last 12 months
- 433433
- minutes affected, total
- 14 Jan
Boards slow to cut for 41 minutes
degraded- What happened
- A migration held a lock on the planning tables longer than we had tested. Boards still cut, but some took over a minute.
- What changed
- Migrations now run against a copy first, and the planner reports its own latency to the status page rather than to us.
- 2 Nov
Gate view unavailable, 12 minutes
outage- What happened
- A bad config reached production because the deploy gate only checked the primary region. Two yards saw an error page at shift change, which is the worst possible minute.
- What changed
- Config changes now roll region by region with a five minute soak, and the gate view falls back to the last cut board offline.
- 8 Aug
Exports delayed overnight
degraded- What happened
- A queue backed up behind one very large export and nothing shed load. Nightly exports landed at 06:40 instead of 23:00.
- What changed
- Large exports run on their own lane, and anything late now tells the customer before we notice.
Fieldline · said elsewhere
Things people said when we were not in the room.
None of these were requested, edited, or paid for. We have kept the unflattering one because removing it would make the other three worthless.
Port operations mailing list· 12 Jan
“We are two months in. The thing I did not expect is that the arguments moved from the radio to the constraint list, where they are at least written down.”
a terminal supervisor
Marine engineering forum· 3 Feb
“Setup was longer than they say if your TOS is old. Worth it, but budget a week not an afternoon.”
a shift planner
Crew WhatsApp, forwarded to us· 20 Feb
“board's up already lads, crane 2 is ours till two”
a crane operator
Logistics subreddit· 28 Feb
“Their incident write-ups are the most honest I have read from a vendor this size. That is most of why we signed.”
an operations manager
Collected from public posts and, in one case, a screenshot a customer forwarded to us. Handles and names are withheld deliberately — we did not ask permission to quote, only to reproduce.
P.S. — Everything above gives something away: the price, where it goes, who we are wrong for, and every outage of the last year. We do it because the alternative is asking you to take all of it on trust, and we would not.
M. AldanaFounder, Fieldline