PHNTMOne
The dead-company test

If we vanish tomorrow, your unit won't notice.

NO SERVERS · NO ACCOUNTS · NO KILL SWITCH · DESIGNED TO OUTLIVE ITS MAKER

You've seen this movie: Revolv. Insteon. Every cloud speaker that became a paperweight the day a server was switched off. The industry calls it "sunsetting." We designed PHNTM One so that movie cannot be made about it — not as a promise, as an architecture.

There is nothing to shut down

WHAT RUNS WHERE
the model
on the device — Ollama bound to 127.0.0.1, run offline
your memories
on the device — SQLite + a local vector store
your documents
on the device — the Vault embeds them locally
voice in / out
on the device — whisper.cpp + Piper, no cloud speech
the phone app
served BY the device, over your LAN — no relay
phntm servers
do not exist — this website is a brochure; the product never talks to it

The day we disappear

Every function above keeps working, forever, because nothing it needs is ours. What stops: software updates (owner-initiated pulls — your unit simply keeps running the version it has) and our email support. What breaks on the device itself: nothing.

And because SSH is documented and the code on the device is readable Python, a community that outlives us can maintain, patch, and improve every unit in the field. We're not promising to open-source anything today — we're pointing out that you already own a readable copy.

Verify it, don't trust it

Unplug your router. Have a conversation. Save a memory, delete a memory, drop a PDF in the Vault. Everything works, because everything is local. The proof page has the exact commands if you want the wire's own testimony.

This page closes the question we get most from people burned by dead gadgets. The honest answer to "what if you shut down?" should always be: you'd never notice.