Excelsior Framework LLC · Northern Virginia

Your systems, on your own hardware.

Records, identity, payments, backups and automation — built and run on machines you control, with your data never leaving them.

This stack runs our own medical practice every day. It is not a demo, and the same pattern transfers to any practice that would rather own its systems than rent its data back from a vendor.

Consulting engagements · your data stays on your premises · this page makes zero external requests

What we do

One framework, any practice

Everything below runs in production for our own companies first — including a working medical practice, the hardest test we could set it. The same pattern fits any business that runs on clients, documents and recurring paperwork.

On-premise & TLS

Infrastructure you own

Self-hosted services on your hardware — certificates, private DNS, an encrypted network between sites.

  • Public entry points hold no keys to anything inside
  • Encrypted offsite backup; the keys stay with you
  • Every deploy tracked in version control
Local inference

AI without a meter, or an upload

Open models running on machines you own — new, old, or repurposed — doing the reading, drafting and summarising all day.

  • Volume work costs electricity, not per-token fees
  • Assistants start already briefed on your systems
  • Hard calls escalate through a controlled handoff

The engine room below shows the math from a measured day.

Data containment

Nothing leaves quietly

Outbound traffic is denied by default and allowed by name — containment is enforced at the network, not promised in a policy.

  • Systems cannot phone home; one checkpoint out
  • Every automated action written down before it runs
  • Encrypted before anything travels; keys stay with you
Identity

One login, correct doors

Single sign-on everywhere — with staff, client and public logins kept as genuinely separate systems.

  • Breaking into the public side reaches nothing internal
  • Access by role, revoked in one place
  • Second factor where it earns its friction
Automation & CRM

Assistants that do real work

Software assistants wired into your own systems through an open standard. They look up and draft; a person approves.

  • Contacts, pipeline and billing in one record
  • Routine paperwork drafted, never sent unreviewed
  • Runs on the local models — prompts stay in the building
Beyond one industry

Built for practices of every kind

If your work is clients, documents, deadlines and confidentiality, this pattern already fits it.

  • Law firms, accounting & financial practices
  • Clinics and independent professionals
  • Education, studios & local business

Proven in the hardest arena first: a complete clinic stack — charting, portal, video visits — runs our own practice daily.

What we run

A working stack, not a slide deck

Described by what each piece does — we do not publish how they are wired, on our systems or on yours.

The Chart

A record that keeps its own history

Every client gets their own vault, kept in plain files any program can read. Every change is attributed and reversible.

Your data format is your export format. No lock-in, ever.

The Gate

One door, watched

Public services are reached through an entry point that dials outward only — nothing on the internet can open a connection inward.

The building has no inbound doors to force.

The Board

One live picture

Every system, its health, and what is talking to what — one screen, in plain language.

If it moves on the board, it is really moving.

The Ledger

Nothing happens unrecorded

Assistants propose, a person approves, and the record is written before the action runs — not after.

Proposed → approved → written down → done. In that order.

The Vault

Backups that survive the building

Encrypted on your machines before a byte leaves them, copied off-site nightly, keys held by you alone — and restore-drilled from the off-site copy, because that is the one a fire leaves you.

An untested backup is a rumour. Ours restore on a schedule.

The Perimeter

Outbound traffic is a decision

By default, systems here cannot reach the internet at all. Anything phoning out needs an explicit entry on a short list you control.

The default answer to "may I phone home?" is no.

The engine room

Frontier brains, local muscle

These models were trained on the work of all of us — our writing, our code, the way we do things. Excelsior exists to claw that value back: run the new intelligence on machines you own — new, old, or whatever's in the closet — point it at your business, your ideas, your family's projects, and keep what it learns. Your data. Your systems. Your hardware. Protected first, contained always.

Most of what AI does for a business is volume work — reading, drafting, summarising, watching. We run that on open models on your own hardware, where the marginal token costs electricity, and save the metered frontier models for the few calls that genuinely need them. The bill stays flat while the volume grows — and nothing leaves the building to be processed.

One real day of our AI, three ways to pay for it

7.3 million tokens processed by our own machines in one measured day

on our hardware≈ $1 · the power bill
same day, mid-tier cloud API≈ $2–4
same day, frontier cloud API≈ $24 · $700+/mo

True scale, no visual mercy. The same machines also run the speech engine and the search index — the hardware pays for itself in months, then the tokens are effectively free.

The advisor loop

why the system gets better every week instead of repeating itself

an assistantdoes the work a personapproves · corrects the correctionbecomes a lesson every assistantreads it first next task starts smarter

Corrections — and what frontier models teach on escalated calls — are written down once and read by every assistant before it acts. Your judgment accumulates in your building; the local tier absorbs capability instead of renting it.

No meter
7.3M tokens · one day · ≈$1

Volume work runs on open models on hardware you own. Using AI more stops being a budget question.

No uploads
0 documents sent anywhere

The models live beside your records, so assistants start every task already briefed — no uploading files to someone else's cloud first.

Model routing
~5% of calls leave the local tier

Hard calls escalate through a controlled handoff — minimal scrubbed context out, the result captured back as a lesson the local models reuse. The routing gets more local every month.

Honest math: token volume is a measured day on our own fleet; cloud figures use public list prices for comparable hosted models (mid-2026) against the same volume. Prices change — the shape doesn't.

Field sketches

What the screens feel like

Small recreations of our actual screens — drawn, not photographed, with made-up data. The real ones hold real work, and real work stays private.

The Agents
Assistants on shift 4 up
records-agent reading inbox…
drafting 2 replies
billing-agent 3 invoices ready
awaiting review
research-agent summarising notes
2 sources read
ops-agent backups verified ✓
idle

Four assistants working at once — each drafts, a person approves.

The Board

Every system and what it talks to, live. Moving means moving.

The Ledger
Every action, written down
drafted invoice ✓ approved
looked up schedule ✓ logged
send reminder email waiting on you
nightly backup ✓ verified
nothing runs unrecorded

Assistants propose; the consequential waits for a person.

The Chart
A. Sample — demo record
Prevention 2 due
Vitals · today 118/76 · 62
Medications 3 active
Notes · signed ✓ attributed
every edit kept · nothing overwritten

A record that keeps its own history, readable by anything.

The Portal
Good morning ☀
Your results are in — all clear. A note from your doctor is attached.
Join video visit
self-hosted · no third-party meeting service

The patient side — messages, results and visits, on the same hardware.

The Console
The whole stack live
records vault healthy
sign-on healthy
payments healthy
backups off-site · drill passed
updates 2 pending review
perimeter nothing phoning out

One screen for everything — a problem is visible before a phone rings.

Being straight with you

What this is, and isn't

  • A small consultancy. One physician-engineer, a limited number of engagements. You work with the person who builds it.
  • On-premise is a trade, not a free win. You own the hardware and the responsibility; in exchange nobody can change your terms or mine your records. When renting is the better answer, we will say so.
  • No client list here. Our clients are not advertising copy. Neither will you be.
  • Not a HIPAA certificate. We build systems that make compliance achievable and document how; the obligations stay yours.
How we work

Start with a conversation

A call first — sometimes the honest answer is that what you have is fine. If it fits: a short review of what you run today, then a written plan you own whether or not you continue with us.

Get in touch

Tell us what you're working with

A sentence or two is plenty. We read everything and reply ourselves.

This lands in our own CRM, on our own hardware — no form service, no analytics, no pixels. We use it to reply to you and nothing else.