Built by one person who needed a chief of staff and couldn't hire one.
Roy started as its founder's own agent: something that would read everything he had to read, write the first draft of everything he had to write, and never — not once — send a thing without him. It has run his working day every day since. Now it can run yours.
The problem it was built for
A working day is mostly reading and deciding. Mail, chats, calendar, calls, documents, notes — most of it needs a look, a fraction needs a decision, and a smaller fraction needs a reply. The looking is where the day goes. Assistants that answer questions don't help with that; you still have to bring them the question.
Roy inverts it. It reads first, on its own loop, across every channel you connect. It ranks what needs you, writes the reply it thinks you'd write, preps the meeting you're walking into, and holds the door on the block you said you needed. Then it waits. The queue on Home is the whole product: everything Roy couldn't decide alone, with the work already done.
Why it runs on your machine
An agent that reads your mail, your calendar, your notes and your calls holds the most sensitive picture of you that exists. We didn't want that picture on our servers, and we didn't think you'd want it there either. So Roy runs on your own computer, keeps its secrets in your operating system's keychain, and is reached from your phone over a private network that never touches the public internet. You bring your own AI keys, so nothing you say to Roy is proxied through anyone.
It is a less convenient way to build a product. It is the only way to build this one.
Why it never acts without you
Every outward move — an email, a post, an invite, a phone call, a HubSpot update, a trade, a lock — is a draft until you tap. That's a rule, not a setting. You can pre-approve the routine and low-risk, and some things always ask no matter what. Every action Roy takes is written to a log on your disk, in plain text, yours to read.
We call it propose, don't act. It's why you can hand Roy your inbox on day one.
Why it's named Roy
Because a chief of staff has a name. You talk to Roy, you ask Roy, you tell Roy to remember something and it does. The name is a reminder that the thing on the other end has a role — and that the role stops at the decision.
Who built it
Bryce Jurss built Roy in 2026 to run his own working week, and has used it every working day since. He writes at brycejurss.com. Roy the product is that year of daily use, made installable — first for one life, then for one job, and now, through Enterprise, for the software an industry or a company runs on.
Six rules every feature has to pass.
Local by default
Your data, your machine, your keys. The server binds to your own computer; your phone reaches it over a private network. No public ports, ever.
Propose, don't act
Reads are free. Anything that sends, posts, places, calls or unlocks is a draft until you approve it. Denied means stopped.
One queue
Everything that needs you lands in one place with the work already done. No hunting across tabs for the thing that's waiting.
Learn the person, not the average
Roy learns how you write, defer, focus and follow up — and shows you what it thinks it knows so you can correct it.
Evidence-linked
A project item, a deal stage, a person's open loop — each points back to the message or meeting it came from.
Inspectable
A log on disk, a learned profile you can read, memory as plain notes in your own folder. Nothing hidden behind "the model decided".
One agent in front. A roster of AI specialists behind — all software, all gated.
Roy leads; the specialists work their own loops and hand Roy proposals. Each has a name so you can read its thread. None of them can send, post, trade or merge without you.
Boring where it should be, careful where it must be.
A small local server, a web app that installs on your phone, eight interchangeable AI providers, and a tool layer where every tool declares itself read-safe or write-gated. Roy improves itself through the same review-before-merge workflow a careful engineering team uses — and it can't merge its own work.
Talk to a person.
Questions, something Roy should do that it doesn't yet, or a team you'd like to set up — write to us.
Working with teams and industries
Roy runs one person's day, and every install stays local to that person. For a team, or for an industry whose day runs on software Roy doesn't speak yet, there's Enterprise: semi-custom when it's your industry's systems, fully custom when it's your company's own.
About Enterprise →