---
title: "For Hermes operators"
description: "What Hervi needs from your Hermes Agent: the releases it supports, how phones reach it, and which sign-ins and front doors work."
url: https://www.hervi.app/operators/
---

# For Hermes operators

Everything to check before you set Hervi up for your household or team: what it needs, how phones reach your Hermes, and which sign-ins work.

## What you need

- **Hermes Agent 0.22.5 or later, before 0.24.** Run as the dashboard, `hermes serve`. Hervi talks to the dashboard’s own socket and REST routes, never the API server or the messaging gateway’s listener.
- **A computer that stays on.** Linux, macOS, a NAS, Docker or Kubernetes. Hervi doesn’t need a Mac anywhere.
- **A model.** Any provider Hermes supports, or a model running on your own hardware. Hervi never sees or chooses it.
- **An address phones can reach.** HTTPS, or a private address such as your home network or a Tailscale tailnet. Plain HTTP over the internet is refused.
- **A profile per person.** Each person pairs to their own Hermes profile, so chats, memory and permissions stay apart. Invites never default to yours.
- **iPhones with iOS 26 or later.** Hervi comes through TestFlight for now and is coming to the App Store.
- **Your assistant’s name, if you like.** Hervi calls it what Hermes does: your skin’s `branding.agent_name`. Hermes’s built-in skins read as “Hermes”. A name typed when a phone is set up, or carried in its invite, stays.
- **The Hervi plugin, if you want it.** Optional, per profile. It adds the iPhone’s own apps (Reminders, Calendar, Weather, Location, Apple Health) and notifications when Hervi is closed.

## How phones reach Hermes

| Way in | Works | Notes |
|---|---|---|
| Tailscale | Yes | A tailnet name with HTTPS certificates. Private while Tailscale carries it; keep Funnel off or Hermes’s sign-in on. |
| Home network | Yes | A private address or a `.local`, `.lan` or single-word name. Not encrypted, so Hervi says so. |
| Public HTTPS | Yes | With Hermes’s own sign-in on, or a front door in front of it. |
| Under a path | Yes | Such as `https://home.example/hermes`, with `X-Forwarded-Prefix` and Hermes’s public URL set to match. |
| Plain HTTP over the internet | No | Refused before anything is sent. |

## What can stand in front of Hermes

Hervi finds out what answers at the address when a phone is set up, picks how to sign in, and says what it picked. Whoever sets the phone up can choose another way, then or later in Settings.

| In front | Works | How Hervi signs in |
|---|---|---|
| Nothing | Yes | Hermes’s own sign-in does the work. With it off, only at a private address. |
| Cloudflare Access with managed OAuth | Yes | “Sign in with your browser”: the system sheet, any identity provider Access uses, including Google. Hervi registers itself; add `me.dbee.hervi:/oauth/callback` as a redirect. |
| Sign-in pages: oauth2-proxy, Authelia, Authentik, Pomerium, plain Access | Yes | “Sign in on a page inside Hervi”, once, then a cookie kept on the phone. Google can’t sign in inside an app’s page, so use another provider or managed OAuth. |
| A key your proxy checks | Yes | “Use a key”: header names and values, such as an Access service token. Kept in the Keychain on the phone that set the home up, and able to travel in invites. |
| Client certificates (mTLS) | No | Not in this version. Put one of the gates above in front instead. |

## Hermes’s own sign-in

| Sign-in | Works | How it goes |
|---|---|---|
| Password | Yes | Hermes’s `basic` provider. Typed once on the admin’s phone and never stored; every other phone joins with an invite. |
| OpenID Connect | Yes | Hermes’s `self-hosted` provider: Pocket ID, Keycloak, Authentik, Zitadel, Authelia, Okta and the like, passkeys included. The provider’s own page, in the system sheet. |
| Off | Behind a front door, or at a private address | Checked again before every connection. A front door that disappears stops Hervi with “Your home isn’t protected right now.” |

## What doesn’t work yet

- Hermes’s API server (port 8642) and the messaging gateway’s listener: Hervi uses `hermes serve` only.
- Hermes releases outside the supported range.
- Client certificates (mTLS).
- A sign-in page that uses Google, inside the app: Google refuses embedded pages.
- Signing out one phone on its own with the password sign-in: Hermes’s `basic` provider has one shared login and no revoke. Cut a lost phone off at the network (remove it from the tailnet), or rotate the secret, which signs everyone out.
