WayseerWayseer · software for IT system observability
Tools for seeing the live state of the systems you already run.
Wayseer makes software for the people who keep IT systems running: tools that read hosts, services, databases and queues as they are right now, and show where things are and which way to go.
Products
Each product has a name of its own, and a site of its own.
Every product is called Wayseer something, and everything about it lives on its own site. This site is about the company.
-
Wayseer Desktop
pre-releaseA standalone desktop app for navigating the live state of your systems: metrics, status, logs, inventories and relationships as one world. The flagship, and the first.
wayseer.app → -
For developers
pre-releaseThe developer site: how to extend Wayseer products with your own modules, the SDK, and the documentation that goes with it.
wayseer.dev →
What comes next, and how products are named, on the products page.
What we hold to
Five things every Wayseer product holds to.
They are written down before the code is. A product that breaks one is not a Wayseer product.
A lens, not a store
Our tools show you the systems you already run, as they are right now. They are not another place your data has to live.
Reads what you have
They work with the systems and sources you already have. Nothing has to be re-instrumented to be seen.
Truthful
Where a fact came from, how fresh it is, and whether it can be trusted are always visible. Stale is shown as stale; unknown as unknown.
An instrument, not an arcade
Motion, depth and color communicate state; they never decorate. Keyboard first, mouse fluent, plain language where it helps.
Paid plainly
What is free stays free. What costs money is listed with its price, and the terms are written to be read.
Who
One IT professional, working with AI, with the process in writing.
Wayseer is made by one person who has spent years on the receiving end of pagers and knows which questions a tool has to answer first. The software is engineered with AI assistance, and we say so plainly, because the method is the point: the domain expert defines what done means, in writing, before anything is built; the work is cut into small tasks with runnable acceptance checks; tests come first; and every architecture decision is recorded with its reasons.
The result is a small team's worth of software from one desk, with the judgement of someone who will be using it at three in the morning. The longer account.
Write to us.
One person reads [email protected] and answers. Say what you run, what you would want to see, and what it would take to earn a place on your second monitor.