WayseerAbout
Way, plus seer: seeing where things are, and which way to go.
Wayseer is a small software company that makes tools for the people who keep IT systems running. This page says who, how and why.
The name
A wayfinder's word.
A wayseer is someone who can see the way: where everything is, and which way to go from here. That is the whole job of an operations tool at three in the morning. Not a report about last week, not a wall of panels, but a clear sight of the live state and a sense of direction through it.
The company is Wayseer. Each product is Wayseer something, with a site of its own: the first is Wayseer Desktop, which day to day people simply call Wayseer. This site, wayseer.net, is the company's.
The company
One desk, in 2026.
Wayseer is made by one person: a working IT professional who has spent years on the receiving end of pagers and set out to build the tool they wanted on their own second monitor. The work began in 2026 under the working name Mind's Eye and became Wayseer on 1 October 2026, when the company took shape around it.
It is deliberately small. There is no sales team, no funding round and no roadmap written for investors. The business is plain: what is free stays free, what costs money is listed with its price, and the terms are written to be read. We would rather earn a place on a thousand second monitors than be installed on a million machines that never open it.
How we work
Engineered with AI, kept honest by process.
We say this plainly because it is how the software is made, and because the method matters more than who, or what, typed the code.
The software is written with AI assistance. The domain expert decides what done means, in writing, before a line is written; the AI does much of the writing of code, tests and documentation, fast. What keeps that honest is neither party but the process around them.
Every phase of work is broken into small tasks with runnable acceptance checks before it starts. Tests come first. Every change is vetted, tested and linted on every platform a product ships on before it lands. Anything that changes what a user sees updates the documentation in the same task, and wherever documentation can be generated from the program itself, it is, so the two cannot drift.
Every architecture decision is recorded with its context, the choice and its consequences, and is not revisited without a new record. Those records are what a new contributor, human or model, reads first.
- Define done first
- Acceptance criteria are written and agreed before a task starts, and they are the only measure of whether it finished.
- Tests before code
- Pure code gets its tests first; what is drawn gets scripted sessions and snapshots; what must be fast gets a budget and a benchmark.
- Decisions on record
- Each architecture decision is written down with its reasons and accepted by the owner before the work that depends on it begins.
- Say what is not done
- What is not yet built is labeled planned; what is not yet released is pre-release. On every site, in every product.
Why these principles
Each one has a reason, and the reason is usually a night shift.
A lens, not a store
Every store eventually becomes the thing you have to run, back up and pay for. You already have the stores. What was missing was a way to see them.
Reads what you have
A tool that needs its own agent on every host never gets installed on all of them. One that reads what is already there gets used on day one.
Truthful
A number with no source, no age and no error state is a guess dressed as a fact. At three in the morning, a guess is worse than nothing.
An instrument, not an arcade
Motion and light are there to show that something changed, where, and how badly. Anything else is in the way, so there is nothing else.
Paid plainly
Prices are listed. Terms are written to be read. Nothing depends on a subscription that lapses while you are on call.