The hospital operating system

Put the resource
where the need is.

Hospitals don't lack data — they lack a way for it to add up. Nightingale OS is the vendor-agnostic router beneath your systems, quietly cross-indexing every stream into one legible fabric. The waste becomes visible. The bedside comes first.

100% firewalled No cloud AI Results-based pricing
flock.nightingale.os / me
The Flock — a nurse's bedside-first shift view in Nightingale OS

Live build · The Flock, the staff surface


The premise

It takes seventeen years for proven medicine to reach the bedside. The bottleneck isn't knowledge — it's the system between knowing and doing.

Every hospital already runs a dozen systems that don't speak: the EHR, scheduling, RTLS, finance, the lab, the bed board. Nightingale OS doesn't replace them. It sits underneath and makes them legible to each other — one cross-indexed fabric the whole institution can reason over.

One router, every stream

Vendor-neutral by design. nOS ingests what you already have and returns a single, queryable picture — no rip-and-replace, no lock-in.

The waste becomes visible

When the streams are cross-indexed, the leaks stop hiding between departments. You see the bottleneck, the cause, and the dollars — in one place.

The bedside comes first

Every decision the system surfaces is built to protect the person at the bedside and the people caring for them. That is a constraint, not a feature.

The fabric

An agnostic router for everything the hospital already knows.

Disconnected systems go in. A cross-indexed, continuously reconciled picture comes out — the substrate every bundle is built on. How it stays consistent, fast, and safe under a live clinical load is the part we keep close.

How the platform works
EHRSchedulingRTLS FinanceLab / PharmacyBed board
nOS agnostic router
One legible fabric

Built and running

A working system you can see today.

Two of the working surfaces, shown as they run. The staff app is firewalled inside the hospital; the patient companion reaches the bedside, the family, and the smart board.

flock.nightingale.os
The Flock staff dashboard

The Flock — the staff surface

A nurse's shift, recovery, and patients in one bedside-first view. Fatigue read as a safety signal, never a productivity score.

Inside The Flock
companion.nightingale.os
Charlie Companion patient welcome screen

Charlie Companion — the patient surface

A calm welcome home for patients and families, on personal devices, in-room iPads, and the smart board.

Meet Charlie

The Aviary

Capability arrives in bundles.

Each bundle is a bird with a job. Adopt the ones you need; they all draw on the same fabric.

See the whole Aviary

What we refuse to do

A constitution, not a style guide.

Nightingale is governed by a set of design laws the software is built to obey. Some of them cost us features. We kept them anyway.

Read the design laws
01
The slack is sacred. A trade that drops a unit below its resilience floor doesn't warn — it refuses, and shows its evidence.

02
Radical honesty. Every number carries where it came from and how sure we are. No stat without provenance.

03
Extract, don't burden. The system does the paperwork. The clinician does the care.

04
Defaults protect. When in doubt, the safe choice is the easy choice. The patient is never "the bed."

For early collaborating partners

You pay from what we find.

Our results-based model ties our fee to verified savings. If the fabric doesn't surface the money, you don't pay for the search.