← The Work

The Nimos OS

the operations view

THE NIMOS OS — CONCEPT

ALL WATCHED

Site

healthy

Funnel

healthy

Changes

healthy

Domain

our stack

Data

healthy

RECENT ACTIVITY

The Nimos OS — the dashboard that watches for you

What it is

The Nimos OS is the client dashboard concept for Nimos Websites: one hub where the whole system reports its work. A website that ships fast is half the product. The other half is knowing, every day, what your site did about it — leads captured, orders waiting, stock running low — without opening six tools or reading a single spreadsheet.

What we built

A single dashboard with the sections a business owner actually checks:

  • Nodes — every agent in your fleet, what it is doing right now, and when it last reported.
  • Traffic — visits and behaviour on your site, in plain numbers, not a marketing login.
  • Leads — every enquiry the site captured, with status, so nothing sits unanswered.
  • Deposits — money committed, tracked in one place against the work it belongs to.
  • Settings — your agents, your permissions, your controls. You decide what agents may and may not do, and you can see the configuration rather than trust it.

The design brief was the operations view: dense, legible, and fast. An owner should be able to look at it for thirty seconds and know the state of the business.

The engineering

Built on the same stack as every Nimos site — a modern component framework with server-side rendering, so the dashboard loads fast and works on a phone. The agent fleet reports into a shared backend, and the dashboard reads that state directly, which means what you see is what the agents see. Agents write their actions to a log the owner can inspect. Nothing happens in your account that you cannot trace in the dashboard. The same pattern library that ships your website ships this interface, so it stays consistent as both evolve.

What the business gets

The honest answer to the question most AI products dodge: after the launch, who is running it? With the Nimos OS, the answer is visible. Agents watch inventory and flag shortfalls, triage incoming orders, draft supplier correspondence for your approval, and report to one hub. You are not subscribing to a black box — you are looking at the actual system, with settings in your hands.

A website brings customers in. The dashboard makes sure the business behind it responds. That combination — presence and follow-through — is what turns a site into an operation.

Start yours

The same four steps built the Nimos OS; a human checked it. Clients own their stack outright, dashboard included.

Start your build at nimoswebsites.com/start

THE BRIEF

One screen where the owner sees what the site did — no logins to chase, no spreadsheet.

HOW IT IS DRAWN — THE SIX STEPS

  1. BRIEF

    The question after launch: who is running it? The concept answers with one view.

  2. SCOPE

    An operations view — nodes, traffic, leads, deposits, settings — dense, legible, fast.

  3. POLICIES

    None to sign yet — a concept commits to nothing.

  4. ACCOUNT

    No login yet — the view is drawn, not built.

  5. BUILD

    Drawn from the studio's own components — the same system, seen from the owner's chair.

  6. RUNNING

    Not running — a concept, labelled as one here and in the work list.

WHAT IT IS

  • One screen for the owner: nodes, traffic, leads, deposits and settings — the state of the business, at a glance.
  • Agents write their actions to a log the owner can inspect — nothing in the account happens off the record.

OPERATIONS · CONCEPTNo public site to open — a concept, labelled as one here and in the work list.

The stack it runs on

The OS sits on the same rails we build on — the same five stations, the same four stages, the same account handover.

GitHub

where every build lives, branches, and ships from

Vercel

deploys the sites the agents build

Neon Postgres

client data, isolated per business — never shared tables

Telegram

where agents reach a human when judgment is needed

Postgres

every brief, lead and deposit, in one place

Resend

the email rail, behind owner-approved sends only

The four stages

provision, build, audit, ship — and the log they write

Scheduled agents

the fleet on a heartbeat — every cycle logged and inspectable

Deploy history

what shipped, when, and what it changed — readable after the fact

Every tile is a tool this build really runs on. Tools, not partnerships.

The loop a client’s site lives on

Deploy is not the end of the work — it is one pass of the cycle. The loop is the product.

THE AGENTIC LOOP

ONE PASS, THEN AGAIN

  1. Intake

    the brief arrives

  2. Scope

    the plan is set

  3. Build

    the site is made

  4. Audit

    a human checks it

  5. Deploy

    it goes live

  6. Watch

    traffic · leads · uptime

  7. Repeat

    the loop closes, it runs again

Never-down, stated honestly

We will not invent an SLA. What we can show is the operations view — and what happens when something breaks.

THE OPERATIONS VIEW — THE HONEST PART

WATCHED

Watched

the site, the funnel, the enquiry inbox — checked on business days

When something breaks

flagged at once, worked by agents, and a human checks the fix

What you hear

the truth first, from the operations view, before you would find it yourself

EVERY CHECK LOGGED, INSPECTABLE

No uptime percentage we do not measure, no guarantee written by marketing — a watching system, agents on a heartbeat, and a human in the loop.

Your build starts the same way.

File the brief