A single self-contained binary. No installer, no account, no cloud, no telemetry — a Synthetic Data Center that lives entirely on your hardware and answers only to you.
Three engines govern every cycle the daemon runs. All arithmetic is local; nothing is ever negotiated with a network.
Admission control where time is pi: work is admitted only while the pressure integral over the pacing window stays strictly inside the circle. The irrational bound never resonates with periodic load, so the node converges to its sustainable rhythm instead of oscillating into overload.
When infinite negative data weight (tombstone debt) meets positive stored weight, classical accounting collapses to NaN. The balancer binds opposing infinities into preserved dipoles held in equilibrium tension — balance is maintained, never annihilated.
Every request bound for the local Ollama instance passes the pi gate first — payload weight is normalized asymptotically, so even unbounded data is scheduled without breaching the window. Loopback allowlist enforced before any socket opens.
The daemon's entire network surface is a loopback proxy. There is no code path that can reach the internet.
┌───────────────────────────────────────────────────────────────┐ │ YOUR MACHINE (air-gap optional) │ │ │ │ local tools ──┐ │ │ VS Code ──────┤ http://127.0.0.1:11834 │ │ console ──────▼ ┌──────────────────────────────┐ │ │ │ ggg-daemon.exe │ │ │ │ ┌────────────────────────┐ │ │ │ │ │ π-gate admission │ │ │ │ │ ├────────────────────────┤ │ │ │ │ │ OllamaRouter │──┼──► 127.0.0.1:11434 │ │ │ (loopback allowlist) │ │ Ollama │ │ │ ├────────────────────────┤ │ │ │ │ │ CryptoBrand HMAC-SHA256 │ │ │ │ │ │ every response sealed │ │ │ │ │ ├────────────────────────┤ │ │ │ │ │ VaultBalancer (⇄ dipole)│ │ │ │ │ └────────────────────────┘ │ │ │ └──────────────────────────────┘ │ │ │ │ egress to internet: ∅ (empty set — no code path exists) │ └───────────────────────────────────────────────────────────────┘
You are never locked into a single ecosystem. The daemon speaks the
OpenAI-compatible request shape on its loopback proxy, so any AI tool,
extension, or web UI that accepts a custom base URL can route through
http://127.0.0.1:11834 — every request passes the π-gate and every
response returns sealed with the node's HMAC brand.
Paste this model block into ~/.continue/config.json. Continue then talks to the daemon instead of any cloud — completions never leave the machine.
{
"models": [{
"title": "GGG Local (π-gated)",
"provider": "openai",
"model": "qwen2.5-coder:latest",
"apiBase": "http://127.0.0.1:11834/v1",
"apiKey": "ggg-local"
}]
}
Any OpenAI-compatible provider entry works — the daemon enforces the loopback allowlist regardless of what the client requests.
Open WebUI, LibreChat, or your own frontend: set the OpenAI base URL and any placeholder key. With the official openai Python SDK it is three lines:
from openai import OpenAI
client = OpenAI(
base_url="http://127.0.0.1:11834/v1",
api_key="ggg-local", # loopback only
)
resp = client.chat.completions.create(
model="qwen2.5-coder:latest",
messages=[{"role": "user", "content": "ping"}],
)
Raw REST works too: POST http://127.0.0.1:11834/chat with {"model": …, "messages": […]}.
Swapping tools never swaps your trust model: the π-gate schedules every payload, the router refuses non-loopback upstreams, and each response carries the cryptographic brand — no matter which UI sits in front.
Start the proxy with ggg-daemon.exe --serve (or let install-startup.bat register it in shell:startup so it is always on).
No code. No developer tools. No command line. If you can install an app and paste one line of text, you can run AI on your own machine — privately, with the daemon watching over every request.
Desktop apps like LM Studio or Jan give you a chat window that feels like any messaging app — no programming required. Download one, pick a model from its built-in catalog, and you're 90% done.
These apps handle the AI model for you. The daemon adds the security layer around it.
Every such app has a settings field called something like "server address", "API base", or "custom endpoint". Type in http://127.0.0.1:11834 — that's it. Your app now talks to the daemon instead of the internet.
The address never leaves your computer. 127.0.0.1 literally means "this machine".
Stuck on a step? Hand this prompt to any AI assistant and it will explain, in plain English, exactly where to click in your specific app:
I am not a developer. I use a desktop AI chat app (LM Studio / Jan / similar), and I have the GGG daemon on my computer. Please give me simple, numbered, click-by-click instructions — no code, no technical jargon — for setting my app's "server address" or "API base URL" field to this local address: http://127.0.0.1:11834 Then tell me how to check that it worked, and what to do if my app shows an error.
Works with any AI assistant — including the one inside LM Studio or Jan itself once you're connected.
1Computation is property. Your hardware, your cycles, your keys. Anything else is trespass.
2The cloud is someone else's computer. Every byte off your device is a byte you no longer control.
3Air gaps are a feature. The daemon assumes the network is hostile or absent — and runs perfectly either way.
4Zero telemetry, by construction. We cannot sell what we never collect. There is no collection code to audit because it does not exist.
5Sovereignty is a right, not an enterprise tier. The personal daemon is free forever — run it, audit it, own it.
6Prove it, don't promise it. Read the source. Verify the checksum. Watch the wire.
→ Full text: MANIFESTO.md (downloads locally) · License: source-available, non-commercial
From the release page, grab ggg-daemon_v1.4.5_windows.zip (or the .tar.gz for macOS/Linux) plus SHA256SUMS.txt.
Confirm the binary is byte-identical to what the build pipeline produced:
Get-FileHash .\ggg-daemon_v1.4.5_windows.zip -Algorithm SHA256 # compare against the matching line in SHA256SUMS.txt
The binary is self-signed, so Windows shows "Windows protected your PC". This is a reputation warning, not a detection.
Click "More info" → then "Run anyway"
Windows remembers your choice for that exact file.
On first launch the daemon runs its built-in verification — pi-gate admission, non-zero-sum balancer, and HMAC brand round-trip — then prints a signed heartbeat:
[SELF-TEST OK] pi-engine gate, non-zero-sum balancer, HMAC brand, Ollama loopback router all verified.
With ollama serve running, start the daemon's loopback proxy and point your tools at it:
.\ggg-daemon.exe --serve # listening: http://127.0.0.1:11834 → upstream http://localhost:11434
Commercial deployment (fleet, OEM, marketplace) requires a signed license.
This form never transmits anything — it seals your inquiry into this browser's
local vault. Email partners@garzaglobalgraviton.com when you're
connected, or see
ENTERPRISE_PARTNERSHIPS.md for the full framework.