Officer OpSec Suite

Your whole digital life as services on a machine you own, reached over a network only your devices can join — and nothing of it on anyone else's computer.
Degoogle yourself!

Secure Server Services Demos

Passwords

Mail

Photos

Files

Contacts

Calendar

Agent

Automation

Browser

iPhone

Your server

Passwords

Mail

Photos

Files

Contacts

Calendar

Agent

Automation

Browser

Graphene / Android

One machine, and it is yours.
For you, for your family, or for your company.

Security is not a feature here. It is the whole point.

Everything below this — the mail, the photos, the agent — is downstream of one decision: your machine has no front door, and only you can open it.

The most private machine you will ever run

Nothing here is published to the internet. Your devices reach the server across a private mesh that is yours end to end, and the whole of it — every service, every app — answers only from behind that one perimeter. There is nothing to find, so there is nothing to try.

How it holds, and how you break it in a hurry →

Your own network

Headscale and Tailscale, both yours: a private mesh your phone and server join wherever they happen to be, coordinated by a server that answers to you and to nobody else.

One gateway, one URL

Every service lives behind a single private address that only your own devices can reach. No public hostname, no open port, no certificate for the outside world to check.

No front door

Something sweeping the internet for machines to break into finds nothing to knock on, because on the public internet there is nothing there. Exposure is the one risk deleted rather than defended.

Kill it in a panic

A phrase you chose, said out loud with the app open, signs you out — or takes the whole server down. Nothing to unlock, nothing to tap, and no phone that can bring it back.

The foundations

The services your life actually runs on — each one on your own server, and reached from every device you own.

Passwords

Credentials are the root of everything else.

A vault on your server and a fill provider on the phone. Logins and one-time codes go straight into other apps and into the browser — no copy-paste, no clipboard for another app to read. The one-time-code secret sits beside the password it belongs to, so a second factor is one tap instead of a second device.

WhyEvery other protection you have runs through this one. Take someone's mailbox and you have their password resets; take the resets and you have everything else. A vault is the actual key to the rest of a life — which is why it should not be a subscription to a company that can be breached, acquired, or handed a warrant. Yours is a Vaultwarden on your own machine, reachable only across the mesh.

Runs on Vaultwarden

Automation

The reason the whole thing got built.

A team of butlers on your machine, given the run of everything on it. Whisper, ffmpeg and the rest sit on the server as tools, and an agent points them at the repetitive work of a life: transcribe the recording, tag the music library, sort what came in, compile the thing you asked for out of your own mail and files. It works over your data, in place, because that is where the work already is.

WhyThis is where the project started. Every other service here is a place your data lives; automation is what finally does something with it without your hand on every step — and doing that over data somebody else holds was never going to be safe. It has to be your own machine. Much more of what it can already do, written down and shown, is on the way.

Runs on Officer

Agent

Your files, your terminal, your agent — not a copy in someone's cloud.

A coding agent that runs on the server, in your real directories, with a terminal and a browser of its own. Talk to it from the phone or the browser and it works where the work actually is, rather than on an upload of it somewhere else. Claude Code and opencode run as themselves; the app just carries the session to wherever you happen to be.

WhyAn agent is only ever as trustworthy as the place it runs. One that lives in your files, on your machine, behind your mesh, can be handed real access — because the blast radius is your own box, not a shared tenant on a platform that logs every prompt. The power and the privacy turn out to be the same decision.

Runs on Claude Code & opencode

And the rest of what you own

Mail

Your own mailbox — as many accounts as you keep — read and written across the phone and the web.

Runs on IMAP & SMTP

Photos

Every photo and video off the phone and onto your own server. The end of Google Photos and iCloud.

Runs on Immich

Files

Your files on every device, synced and yours — an open drive that answers to no one but you.

Runs on Officer

Contacts

Your address book, served natively to the phone over CardDAV, held on your machine and nobody else's.

Runs on CardDAV

Calendar

Your calendars on every device over CalDAV — native to the phone, owned by you.

Runs on CalDAV

Inside one app, or all of them apart

One door to everything — or a home screen full of them. Your call, and you can change it.

Every service ships twice. There is one central app, Officer, that holds all of them behind a single sign-in and one session; and there is a standalone app for each, on its own home-screen icon. Run the whole suite inside the one door, or pull the ones you live in — Music is the one most people want loose — out as apps of their own. Same code, same server, same session. Install all of them, or only Passwords and Mail: what you install is what you have.

WhyThe one central app means one place a credential ever lives and one place to sign out of. Standalone apps mean the thing you reach for twenty times a day is one tap from the home screen, not two taps inside a container. You should not have to choose between the two, so you do not.