A private chief of staff,
not another chat window.
Most operator tools are built to add another tab to your day. Anamora is built to subtract one. The premise is simple: your business has a shape, and someone should be holding it for you.
Right now, that someone is you — at 06:30 with a coffee, scrolling Slack, opening Gmail, checking Calendar, and trying to remember what you owed Aiyana three Fridays ago. That loop is what Anamora is designed to dissolve.
The thesis.
A small operator — a founder, a chief of staff, an agency lead — runs a business that looks like a graph: people, projects, commitments, decisions, risks. Tools today treat that graph like a stack of inboxes. Anamora treats it like a graph.
The assistant captures context (transcripts, threads, voice memos), maintains a structured business memory in a vault you own, runs a small set of bounded routines on a schedule, and proposes the work — then asks before it acts.
A chief of staff who reads the night, lays out the morning, and never sends an email without showing it to you first.
Why an embedded runtime.
Anamora ships as a desktop app — Mac, Windows, Linux — with the agent runtime bundled inside. There is no separate CLI to install. The runtime, the vault, and the routines live wherever you choose to keep them. Most operators run it on a laptop. Some run it on a Mac mini in the office, reachable over Tailscale. A few run it on a small Linux box they already own.
The vault is plain Markdown. The cache is SQLite. The model is whatever you choose to point your key at. Nothing leaves the device unless you say so — and the things that do leave wait behind an approval object first.
The five-part shape.
- The board · a quiet operating desk, composed overnight.
- Memory · a vault of entities — people, projects, decisions, risks.
- Routines · YAML-defined background work, bounded and replayable.
- Approvals · the control plane between intent and action.
- Chat · the relationship layer, scoped to anything in the system.
What onboarding looks like.
You don’t download Anamora. You get installed for.
Each operator install is hand-shaped — to your stack, your tools, the routines you already keep, the language your team uses. Eight stages, about four to six weeks end-to-end, and a real person on the other side of every one. We onboard ~3 operators per month. That’s the rate at which we can actually do the work.
Your time investment is small: ten minutes for the intake, thirty for the fit call, two hours scattered across the build for stack walkthrough and pack review, a pilot week where you actually use it and tell us what’s wrong. Three to four hours total.
What we ask for.
A short intake — how you work, what you’d want held, the texture of your week. We read every application. The fit call follows within a week. After that, the scoping doc tells you exactly what’s in scope, what’s not, the price, and the calendar — before you commit to anything.
What we won’t do.
We won’t accumulate state we don’t show you. We won’t ship a routine that sends without asking. We won’t pretend the assistant is autonomous when it’s really just bold. The autonomy ladder grows one rung at a time, per skill, per surface — you decide where the line lives.
If this sounds like your desk.
Tell us a little about how you work, what you wish was being held, and which tools the assistant would have to know. We read every application; the fit call follows within a week.