LocalGhost - Private Local AI Server | Your AI, Your Data, Your Hardware

ghost@localghost: ~
[ ENTER THE ESCAPE PATH ] > PRIVACY THROUGH CODE, NOT PROMISES.
> SECTION_01

THE MANIFESTO

"Privacy is the power to selectively reveal oneself to the world."
— A Cypherpunk's Manifesto, 1993

The Cypherpunks told us to write code. We didn't write enough. Today, your phone is a tracker, your cloud is an informant, and your AI is a spy. Every click is logged, every query sold, every interaction feeding a model you will never own.

LocalGhost inverts this. We move everything you need, your AI, your data, your digital self, from their servers to yours. A private server on your own hardware, where nobody knows you exist.

We aren't asking you to trust us, we're asking you to verify that trust is unnecessary.

WHAT YOU CAN DO

[✓]
Audit every line of code.
Everything is open source. No black boxes except the one on your desk.
[✓]
Fork, modify, or replace us entirely.
We're blueprint makers rather than gatekeepers, and the mission is bigger than the company.
[✓]
Build it yourself and pay us nothing.
Buy the parts. Flash the OS. We'll still high-five and support you.
[✓]
Walk away whenever you want.
If we go bankrupt, you lose nothing. Your box keeps running. Someone else can pick up where we left off.

WHAT WE CANNOT DO

[✗]
Sell your data.
We do not have it. Your data lives on your hardware. We are architecturally blind.
[✗]
Charge you a subscription.
There is no server to cut you off from. What you buy, you keep.
[✗]
Force an update.
Unplug the ethernet and we cannot reach you. No backdoor. No kill switch.
[✗]
Train AI on your life.
Your journals, photos, biometrics, secrets exist only on your desk.
[✗]
Track you.
No analytics, no telemetry, and the box does not phone home, so we don't know who you are.
[✗]
Comply with surveillance requests.
When the subpoena comes, we have nothing to hand over.

This is code you can read, math you can verify, and architecture that makes betrayal structurally impossible.

Our goodwill isn't the point, the fact that we are technically powerless to stop you is.

No remote dependencies, no server-side computation, and no way for us to betray you even if we wanted to.

[ READ: WHY WE BUILD ]

> SECTION_02

THE FLEET: LOCAL DAEMONS

Eleven daemons ship in the current release, wisp 0.0.5, ten of them doing their whole job every day and ghost.shadowd with its first detector, and one more, ghost.mistd, is planned for poltergeist. Each is a small Go program with one job, so when one of them is wrong, the name of the daemon is the name of the bug. Apart from ghost.secd, they all live on the encrypted volume and exist only while it’s unlocked. Nothing of yours leaves the box. What it asks the internet for is public, from prices on the exchanges to the news when your phone is away and its own maps, models and releases from the signed mirror. Set one up yourself.

FRONT DOOR & KEYS
The only daemon on the unencrypted disk and the only one the phone talks to. It checks the phone’s certificate and answers 503 to everyone else, unseals the volume key from the TPM when the right PIN arrives, and mounts the archive where only the fleet can see it. A wipe PIN erases everything and looks like an ordinary unlock. Why encryption alone isn’t enough.
RUNS EVERY DAY
SUPERVISOR & HEALTH
Started by secd once the volume is open. It starts the rest of the fleet, restarts whatever falls over, keeps the logs, and owns every health number the phone shows, from CPU, memory and GPU to how far each stage of the photo pipeline has got. The only daemon that can read every other daemon’s metrics.
RUNS EVERY DAY
PHOTOS, VIDEOS & PLACES
Takes in photos, videos and location points from the phone. It keeps each original byte for byte, reads its date and place, makes the previews, cleans the location trail and tells each day as stays and moves, drawn along the streets on maps the box cuts itself from public data.
RUNS EVERY DAY
SEARCH & DESCRIPTIONS
Asks the model to describe every photo, files each tag under one of eleven categories, and keeps one index over originals, journal entries and memories. Search runs Postgres full-text and EmbeddingGemma vectors side by side and merges the two with reciprocal rank fusion.
RUNS EVERY DAY
THE MODEL
The box’s inference broker. It queues every request for the model, questions ahead of background work, and runs Gemma 4 12B with its vision projector through llama.cpp, as a private child on a loopback port, on the GPU when there is one. Changing the model is a config change, and no other daemon notices.
RUNS EVERY DAY
MEMORIES & CHAT
Writes a short account of every day, groups photos into outings, learns what you like to photograph, and answers the chat from your own archive with what it used listed under every answer. It also groups the news into stories, writes the day’s brief and two digests, and writes a page for each coin. How a memory gets made.
RUNS EVERY DAY
SITUATIONAL RETRIEVAL
Decides when a memory is worth surfacing before you ask for it, and stays silent the rest of the time. A morning reflection from a year ago, or a place nearby that matches what you photograph, sent to the phone as a notification you can answer. Why retrieval isn’t enough.
RUNS EVERY DAY
TEXT
Takes in notes and emails dropped into its inbox, keeps the originals, and writes each one into the journal the rest of the fleet builds memories from. Chats go into the journal too, once they’ve been quiet for ten minutes.
RUNS EVERY DAY
VOICE NOTES
Keeps the voice notes the phone records, at the daily check-in or any time, and transcribes them on the box with whisper.cpp. The transcript goes into the journal and the audio never leaves for a speech service.
RUNS EVERY DAY
HEALTH DATA & PRICES
Takes steps, sleep, heart rate and the rest from the phone’s Health Connect a day at a time. It also prices the top hundred coins every minute from its own blend of seven exchanges, and BTC, ETH and SOL every five seconds, keeps the ECB’s table and the price history, and computes CRYPTO50, the fifty largest weighted by volume.
RUNS EVERY DAY
ADVERSARIAL MIRROR
A separate daemon whose job is to challenge your thinking instead of confirming it. Its charter lists 28 patterns to watch for. The first detector is live, and it says so plainly when your weekly messages to the box double past sixty. The other 27 are planned for shade. Why this matters.
STUB, FIRST DETECTOR LIVE
ghost.mistd
BACKUP & THE MIST
Not written yet, planned for poltergeist. Encrypted, sharded backups spread across other people’s boxes, so a house fire or a dead board doesn’t end the archive, with recovery coordinated from your own keys. It belongs to the last release line on the roadmap, The Mist.
PLANNED, POLTERGEIST

> SECTION_03

SURVIVAL PROTOCOL: "THE MIST"

Planned for poltergeist, the last release line on the roadmap. No code for it exists yet, and this is its design.

We do not have a server. If we go bankrupt tomorrow, your data survives. LocalGhost relies on a Distributed Hash Table (DHT).

┌──────┐     ┌──────┐     ┌──────┐
│ NODE │────▶│ NODE │────▶│ NODE │
└──┬───┘     └──┬───┘     └──┬───┘
   │            │            │
   ▼            ▼            ▼
┌──────┐     ┌──────┐     ┌──────┐
│ NODE │◀────│ NODE │◀────│ NODE │
└──────┘     └──────┘     └──────┘

NO CENTRAL NODE. NO MASTER. JUST THE MESH.
[1]
SHARDING
Your encrypted soul is broken into thousands of shards.
[2]
DISTRIBUTION
You store shards for others, they store shards for you.
[3]
ZERO-KNOWLEDGE
They cannot read yours. You cannot read theirs.

THE PACT. Dedicate 20% of your drive to the network. Gain immortality for your data.


> SECTION_04

THE ECONOMICS OF INDEPENDENCE

Why we will never ask for a subscription.

The modern technology industry is built on a single toxic premise, rent-seeking.

They don't want to sell you a product, they want to trap you in a monthly payment and keep you as a tenant in your own digital life. If you stop paying, the lights go out and the doors lock on your memories.

We reject this. Not everything needs to be a subscription.

Our business model is boring, archaic, and honest.

1. WE MAKE MONEY WHEN WE SELL YOU HARDWARE

If you choose to buy a pre-built LocalGhost box from us, we charge you a 30% margin on the parts and assembly. That is our profit. It pays for our engineers, our electricity, and our coffee.

The choice. If you don't want to pay us, you don't have to. The hardware specs are open. The code is open. You can buy the parts on Newegg, download our repo, and build it yourself. We will not earn a cent, and we will still high-five you for doing it.

2. WE MAKE MONEY WHEN WE SELL YOU UPGRADES (SOFTWARE)

Software here is a tool rather than a service. If we develop a breakthrough new daemon, say a "ghost.voiced v2" with better reasoning, or a "ghost.medicald" module, we will put it in a package and put a price tag on it.

The choice. You can buy it, or you can ignore it.

3. WE NEVER MONETIZE YOU

We cannot sell your data because we do not have it, cannot train AI on your life because we cannot see it, and cannot show you ads because the box has no ad server.

⚡ CODE, NOT PROMISES

The guarantee. If you don't buy an upgrade, your current version will keep working forever. We will never throttle, brick, or degrade your existing system to force an upgrade.

Why? Because we can't.

Once you unplug the ethernet cable or block the port, this box is an independent island. We have no backdoor, no remote kill switch, no admin access. Even if we wanted to force an update, the architecture prevents us from reaching you.

We have designed ourselves out of the loop. The architecture is the guarantee, not the company behind it.

THE COMPARISON

FEATURE THE "BIG TECH" WAY THE LOCALGHOST WAY
Payment Structure Infinite Monthly Rent One-Time Purchase
If You Stop Paying You lose access to your data Nothing happens. It keeps working.
Data Privacy They scan it for ads/training We physically cannot see it
Upgrades Forced UI changes you hate Optional packages you choose
Hardware A locked black box you can't open Standard parts. Repairable. Upgradeable.
Relationship User / Product Owner / Tool

When you pay for something once you own it, and when you pay monthly it owns you.


> SECTION_05

FREQUENTLY ASKED QUESTIONS

Where an answer describes something that isn't built yet, it names the release line it's planned for, and the roadmap lists them all. What the current release, wisp 0.0.5, does today is on the About page and in its release notes.

[?] Okay, but what actually IS it? +

Today it's software you run on a machine of your own, a Debian 13 computer with a TPM and a spare disk, much faster with an NVIDIA card, and an Android app that's the only way in. Set Up a Box has the whole setup. You install the app, run the guided setup on the box, scan the QR it draws and unlock with your PIN. There's no cloud account, no login page and no web interface.

From there the phone syncs your photos, videos, location trail, health data, notes and voice notes to the box. The box keeps them on an encrypted volume, describes and tags them with models running on its own hardware, and gives them back on the phone as days, places, memories and answers.

A small, silent box we build and sell, with the same software and nothing else to set up, is the plan. Nothing is on sale yet.

[?] How do I get my data onto it? +
  • The phone app. Photos, videos, the location trail, Health Connect data, notes, voice notes and the daily check-in, synced in the background
  • Text and email. Files dropped into ghost.noted's inbox on the box, emails saved as .eml included
  • Planned. Imports of bank, fitness and other exports through ghost.tallyd's parsers come in shade (1.x), and a browser extension in phantom

Everything goes straight from the phone to your box, over your home network or through your own domain, never through our servers, because we don't have any that hold your data.

[?] What does the AI actually do? +

The models run on the box, on its GPU when it has one and its CPU when it doesn't (Gemma 4 12B for descriptions and chat, EmbeddingGemma for search, Whisper for voice notes). In wisp 0.0.5 they do these things.

  • Describing and tagging. Every photo gets a description and tags in eleven categories, so you can find it later by what's in it
  • Days and memories. A short story of each day from the photos, the trail, the health data and the check-in, the places you keep going back to, and facts from your notes and chats, each one yours to edit or delete
  • Search and chat. Ask about your own life and it answers from your archive, with the sources it used listed under the answer
  • Noticing. Once a day it writes up a habit or a change from the last few weeks, kept only when every number in it came from your data
  • Arguing back. ghost.shadowd, the critic, runs its first detector. Correlations like sleep against spending wait for the bank and fitness parsers planned for shade

The key difference is that this AI has zero incentive to manipulate you. It can't sell you anything, can't show you ads, can't optimise for "engagement." It just tells you the truth.

[?] Why do you call them daemons and not agents? +

Because that's what they are. Daemon is the Unix word for a long-running background process that responds to events and requests, and it's been the word since the 1960s. sshd, systemd, cron are daemons. The LocalGhost fleet is the same kind of thing, processes that sit on your box, expose APIs, do their job, and stop.

Agent has come to mean something else. In 2026 it's the industry's word for an LLM in a loop, where the model decides what to do next, composes its own tool calls, and the surrounding code is scaffolding for whatever it comes up with. The whole pitch is that you don't enumerate the steps in advance. That's the architecture, and it's the architecture that carries the autonomy and trust-us framing.

LocalGhost daemons work the other way around. The daemon owns the control flow. It runs predefined steps in a defined order, and when it needs language work done, it calls a local LLM the same way another daemon would call Postgres. Sometimes it asks the model which of N predefined steps to run next, the model picks from a fixed menu, the daemon executes the choice. The model never writes the menu. It never invents a step. It never gets handed the keys.

A daemon that uses Postgres is still a daemon. A daemon that uses a local LLM is still a daemon. The model is a dependency, not the driver.

The word matters because the connotations matter. Daemons are infrastructure. Agents are something you're asked to trust. LocalGhost is built so you don't have to.

[?] How does "The Mist" backup system work? +

Planned for poltergeist. It's the last release line on the roadmap, and no code for The Mist exists yet. This is the design.

The Mist is a peer-to-peer backup network. Here's the simple version.

Step 1, shred. Your data gets encrypted with a key only you hold. Then it gets chopped into thousands of tiny pieces called "shards." Each shard is meaningless on its own, like confetti from a shredded document.

Step 2, scatter. Those shards get distributed across other LocalGhost boxes in the network. Your shards live on dozens of strangers' drives. Their shards live on yours.

Step 3, rebuild. When you need your data back, your box collects the shards from the network and reassembles them. Only your encryption key can make sense of them.

The beauty of it. The people storing your shards can't read them, they're encrypted and incomplete. You can't read theirs either. Nobody knows whose data they're holding. The network doesn't even know you exist.

If your house burns down, your data survives. If LocalGhost goes bankrupt, your data survives. The network has no central point of failure.

Technical note. This uses erasure coding similar to how Ethereum's PeerDAS works for data availability sampling. We use Reed-Solomon encoding so you only need around 50% of shards to reconstruct your data, making the system resilient even if half the network goes offline.

[?] How do the boxes find each other without a central server? +

Planned for poltergeist. It's the last release line on the roadmap, and no code for The Mist exists yet. This is the design.

This is the magic of distributed hash tables (DHT). Here's how it works in plain English.

The bootstrap problem. When your box first connects to the network, it needs to know at least one other box. We publish a small list of "bootstrap nodes," these are just regular LocalGhost boxes run by volunteers who've agreed to be discoverable. Your box contacts one of these to get introduced to the network. After that, it never needs us again.

The address book. Every box on the network has a unique ID (a long random number). Each box maintains a partial "address book" of other boxes it knows about. But here's the clever bit, you don't need to know everyone. You just need to know boxes whose IDs are "close" to yours in the mathematical sense.

The hop game. When you need to find a specific shard, you ask the boxes you know who's closest to this shard's ID. They point you to someone closer. You ask that box the same question. Within 3-4 hops, you've found what you're looking for, even in a network of millions.

No phone book server. There's no central directory. The network is the directory. If any box goes offline, the others route around it automatically. The more boxes join, the more resilient it gets.

Think of it like asking for directions in a city with no street signs. You ask a local, they point you to someone who knows better, and within a few asks you're at your destination. No map company required.

Technical note. We use a Kademlia-style DHT, the same algorithm that powers BitTorrent and IPFS. Node distance is calculated using XOR on node IDs. Each node maintains k-buckets of peers at exponentially increasing distances, giving O(log n) lookup time. The protocol is UDP-based for speed, with optional QUIC tunneling for NAT traversal.

[?] What if I lose my encryption key? +

Then your data is gone, and that's by design. We never had access to it, so there's no "forgot password" flow and no support ticket that can bring it back.

Today, in wisp 0.0.5. The volume key is sealed to your box's TPM, or wrapped by your PIN on a machine without one, and there's no recovery path yet. A dead board or a forgotten PIN loses the archive on that disk, so keep the originals of anything you can't lose somewhere else as well.

Coming in shade (1.x) at the earliest, not in wisp. The plan is two hardware security keys per box, and boxes we sell are meant to come with them. At setup you plug both in, and the box makes the master key and splits it between them with Shamir's Secret Sharing, so neither key alone can decrypt anything.

  • Key 1. Kept with the box for daily use.
  • Key 2. Kept somewhere safe and separate, a bank vault, a trusted friend's house, your parents' place. This is the recovery key.

If you lose Key 1, Key 2 makes a new pair. If your house burns down with the box and Key 1 inside, Key 2 restores everything to a new box. If you lose both, it's game over.

Technical note. The planned keys are FIDO2 hardware tokens with secure elements. The master key never leaves the secure element and only derived keys are used at runtime, with a 2-of-2 split and an optional 2-of-3 mode with a third key.

[?] Can I access my box when I'm not home? +

Yes. Point a domain you own at your home connection and forward port 443 on your router to the box, and the phone reaches it from anywhere over mutual TLS, with the certificate the box gave it at enrolment.

The phone trusts the box by its certificate's fingerprint and the box trusts the phone by its client certificate, so nothing in between, including us, can read or change the traffic. Anyone without a certificate the box issued gets the same 503 a server that's down would give.

Or keep it at home.
Leave the domain out and the box answers only on your home network. When you leave, it's a black hole. When you return, it's there waiting.

There is no option where your data goes through our servers. We don't have servers that hold your data, so we couldn't offer one if we wanted to.

[?] What happens if LocalGhost (the company) disappears? +

Nothing. Your box keeps working.

The software is open source. The hardware is standard parts. The Mist, planned for poltergeist, is designed with no centre. There is no license server to phone home to. There is no authentication service to validate your purchase.

If we go bankrupt tomorrow, here's what that looks like.

  • Your box continues running the last version you installed
  • The Mist, once it lands in poltergeist, keeps running without us, since it has no central server
  • Someone else can fork the code and continue development
  • You can maintain it yourself if you're technical
  • Everything a box downloads is on the signed setup mirror, and anyone can copy it and host it, or keep it on a USB disk

We have deliberately designed ourselves out of the critical path. Your independence does not depend on our survival.

[?] Is this legal? +

Yes. Running a private server in your home is legal, encrypting your own data is legal, and storing backups on a peer-to-peer network is legal.

We're not helping you hide anything from the law. We're helping you exercise your right to privacy, a right that exists in most democracies but has been quietly eroded by decades of "free" services that monetize your attention and data.

If law enforcement comes to us with a warrant, we'll comply. Compliance looks like this. "We have no data, no logs, and we don't know who uses our hardware. Here's our open-source code. Good luck."

The architecture is the legal defence.


> SECTION_06

THE BLACK BOX

Planned for specter, after the software is stable, and nothing is on sale. The spec below is the design and will change before launch. Today LocalGhost runs on a machine of your own, and Set Up a Box says how.

We do not manufacture silicon. We do not print circuit boards in a secret facility. We source the best off-the-shelf components we can find, verify them for backdoors, flash our OS, and bolt them into a case.

> COMPUTE ARM64 SBC w/ NPU
> STORAGE M.2 NVMe (Standard 2280 Form Factor)
> MEMORY 16GB+ LPDDR4x
> SECURITY 2× FIDO2 Hardware Keys
> CHASSIS Aluminum (Passive Cooling / Fanless)
SUPPLY CHAIN TRANSPARENCY.
This is a "Bill of Materials" product. We use standard parts you could buy yourself. The value we add is the integration, the thermal engineering, the OS configuration, and the guarantee that the components work together flawlessly. Final specs will be published before launch.

OPTION A: THE INTEGRATOR

We buy the parts. We assemble the unit. We flash the OS. We ship it to you. Your markup funds the labor, the testing, the software development, and a future where privacy isn't a premium feature.

PRICE TBD

OPTION B: THE SCAVENGER

Don't wait for us. The software runs today on a Debian 13 machine with a TPM and a spare disk, faster with an NVIDIA card, and the phone app comes signed in the same release. The setup page has what you need, the order to do it in, and what each step costs, from a bare install to a phone that unlocks the box. Show us what you build.

COST, YOUR TIME + PARTS
[ SET UP A BOX → ]