No phone home
These apps talk to your infrastructure — the servers and accounts you control — not to a mystery endpoint we own.
AiMANAC is the anchor. Ten siblings extend it. Your notes, mail, chat, and tools stay on your devices and the infrastructure you choose — not on a rented account we can see or switch off.
The anchor
Think of the iPhone as the keyboard. AiMANAC is the modular synthesizer: it takes what you ask for — research, mail actions, marketplace messages, routines — and turns it into structured work you can trust.
The interface is designed to be user-friendly — clear surfaces and controls so you are not guessing what the app is doing. Future updates will let you choose from different layouts and orientations of the application so it fits how you work.
Go deeper into AiMANAC → · Walk the screens in plain English → · Chat FX gallery →
The engine
When you ask AiMANAC for something, you should not have to micromanage models, plug-ins, or “which tool goes where.” HELM is the orchestration layer: the harbor pilot that knows which channel to use, which specialist app can help, and how to pipe the job through safely.
Another image that fits: the studio engineer. You describe the song; HELM sets up the mics and calls the right players. You stay in the producer’s chair.
One more layer, still in plain English: HELM is not trapped behind a single chat window. The AI you already treat as your “main brain” inside AiMANAC can call it — and so can a cloud assistant you use elsewhere, if that service is allowed to run tools (today many products use a shared plug-in pattern called MCP, which is just “standard sockets” so one assistant can flip the right switches on your stack without you copy-pasting secrets).
So how big is AiMANAC in your head? Same product, three harmless pictures: a Swiss Army knife (one handle, many blades you fold out only when needed), a cruiser’s hangar deck (one ship, lots of smaller craft that launch for each job), or a piloted work-suit (you stay in the seat; the suit does the heavy lifting out on the deck). Pick whichever story clicks — the machinery underneath is the same idea: you steer; HELM routes.
The ecosystem
You would not buy fourteen sand wedges for a casual round — extra weight, extra clutter, and clubs that never leave the cover. The same goes here: each sibling is another club in the caddy — pull it when that shot shows up, leave it home when it does not.
AiMANAC is the bag itself: your $9.99 anchor that already runs HELM. Each sibling is $1 when a real part of your life needs that specialty (mail you host, marketplace chat you own, a team fleet, and so on).
Why not “just buy them all?” Because “just in case” usually means paying for apps you will not open and servers you will not deploy — and learning curves you do not need. Add siblings when your week actually touches that problem; skip the rest without guilt.
| Kit | Roughly for… | What’s in the bag |
|---|---|---|
| Anchor only | One trustworthy control room on your phone | AiMANAC |
| Hosted desk | Email pipelines you run yourself, not a rented inbox | AiMANAC · MailSloth |
| Marketplace floor | Buyer–seller chat you host with a serious trust posture | AiMANAC · BROILR |
| Desk + floor | Both hosted mail and hosted marketplace work | AiMANAC · MailSloth · BROILR |
| Clockwork | Repeatable sequences and “run this again tomorrow” chores | AiMANAC · HELMPC |
| Research shelf | Deep reading, collections, and topic journals | AiMANAC · DeepDive |
| Mission control | A real Linux desktop agents can drive for you, on your metal | AiMANAC · Archimedes |
| Pocket co-pilot | On-device agent layer beside the rest of the family | AiMANAC · Bombadil |
| Tool-shed rules | Many plug-in tools — one policy surface | AiMANAC · Satcheli |
| Private keys | Digest long PDFs and pasted text into flash cards beside AiMANAC — work stays on the phone | AiMANAC · PSL |
| Bridge crew | Small teams sharing work with per-member Apple identity | AiMANAC · FL33T |
| Lookout | Web crawl / sentinel workflows with a hardened stance | AiMANAC · ARACHNID |
Below, each tile is one club. Tap through for the plain-English story, pricing, and (where we have them) design previews.
The stance
Plain language, plain promises. No fine print that says we get a copy of your life.
These apps talk to your infrastructure — the servers and accounts you control — not to a mystery endpoint we own.
AiMANAC is $9.99 once. Each sibling is $1. No subscriptions. No “premium tier” locked behind monthly billing.
What persists lives on your iPhone (Apple-encrypted), your iCloud (Apple-encrypted where applicable), and any backend you deploy — not on our rental servers.
Every app is reviewed, signed, and sandboxed by Apple. That is the baseline safety net — and your baseline recourse if something ever goes wrong.
When apps sync with each other through Apple’s cloud, they use iCloud — not a sync layer we host or can read.
Recovery rides on Sign in with Apple plus a setup code you store on the deployment. We cannot “reset your password,” which also means we cannot be arm-twisted into doing it for someone else.
What’s different under the hood
You do not need the jargon to use the products. If you want it, here is the short version of what makes the architecture unusual.
Sensitive payloads travel like sealed envelopes: bound to your deployment’s fingerprint. Even a stolen database copy is not enough to unwrap them outside that context.
Installed Everplay apps share a tiny neighborhood on the phone. AiMANAC vouches once; siblings inherit trust without you re-typing passwords in every app.
Several siblings expect a server you run (VPS, Railway, a Mac mini in the closet). We ship the app; you supply the house.
Each sibling can extend what AiMANAC can do. Install a sibling, unlock new commands — like adding pedals to a board.