Operator desk
Greenfield, jMac
Jared's own agents live here, along with scheduling and the operator knowledge brain. This is the control desk, not a client runtime.
A public map of the computers and servers behind 828 Pros, and the path used to stand up a managed client agent. Nothing here is a credential, a private address, or a client name.
828 Pros builds and maintains managed AI agents for professionals in Western North Carolina. Each client agent is isolated. It talks to the client on Telegram, uses only the systems that client approved, and keeps customer messages, money movement, and public posts behind a human yes.
Separately, Jared runs an operator desk: agents that do the shop's own work. Those sit on the Macs. Client agents do not.
Hermes is the runtime used for both. The public offer is still a managed agent, not a software login.
Greenfield, jMac
Jared's own agents live here, along with scheduling and the operator knowledge brain. This is the control desk, not a client runtime.
Dorado, DBZ
One isolated home per client. New production bots go on Dorado. Earlier pilots still live on the Mac Mini. The Mini also remains the local Mac endpoint when a bot needs a real signed-in browser.
Rove, clawdbot
Static sites and a few always-on web apps. This page is on Rove, which serves every *.828.fyi site. 828pros.com and jcl.help live on clawdbot.
JBrain, Vault
Durable operator notes live in JBrain on Greenfield. Encrypted backups of operator and client state land on Vault, a small local box kept for that job.
| Name | Kind | Job |
|---|---|---|
| Greenfield | Mac Studio | Current operator desk. Runs the operator agents and hosts JBrain, the shop's durable notes. |
| jMac | Mac | Original operator machine. Still used for work that only exists there: signed-in browser sessions and desktop services that never moved. |
| DBZ | Mac Mini | Earlier client-bot host. Isolated runtimes for the first pilots. Also the local Mac endpoint when a client bot needs a real browser session instead of a headless one. |
| Dorado | Hosted Linux server | Production host for new isolated client bots. Public SSH is closed. Each client is its own container home, not a folder on Jared's laptop. |
| Rove | Hosted Linux server | Static websites, including this one. Client domains can point here and get HTTPS without sitting on the operator Macs. |
| clawdbot | Hosted Linux server | 828 Pros public site, jcl.help, and a handful of always-on web apps. Not the general client-bot host. |
| Vault | Small local Linux box | Encrypted backup store. Client archives and operator snapshots land here so a single machine failure is not the last copy. |
| DGX Spark pair | Two local GPU machines | Commissioned on the shop network for local model work. Not the live client-bot path. Fabric and serving cutover are still open. |
New production clients go on Dorado. A few earlier pilots remain on DBZ. The sequence is the same either way. The public intake is at 828pros.com/onboarding.
The form takes a business name, contact, requested systems, and similar bounded facts. It rejects anything that looks like a password, bot token, or API key.
Jared reviews the row. A checkmark authorizes scaffold only. It does not authorize account connection, a live gateway, outbound messages, or spending.
A provisioner builds a clean runtime on the chosen host, with its own config and workspace plus empty secret slots. It does not clone another client's files, keys, or chat history.
The Telegram bot token, model credentials, and any Google access are written into restricted files on that host. They never go through the website, a spreadsheet, or chat.
The bot starts with Jared as the only admitted Telegram user. He proves a round trip, one polling process, and that a restart still answers.
The client opens the bot and receives a short-lived pairing code from Hermes. Jared approves that code from the trusted runtime. The page that introduces the bot never carries a token or a code.
A website on Rove, email and calendar, documents, or a CRM each get their own approval and their own live check. Read paths are proven before any write path is opened.
Isolated home, one poller, a human start, tools matching the plan, and no secrets in public pages or notes. A green Docker light is not enough.