Use case / deployment decision

Hermes Agent Desktop App vs Managed Hosting

Both run the same agent; they differ in who keeps it alive. The desktop app is the fastest way to evaluate Hermes Agent and a perfectly good permanent home for a single person. Managed hosting answers a different question: what happens when other people depend on the assistant, or when it has to respond while your machine is closed.

Updated Sep 16, 20269 min read
Deployment route
  1. 01

    Count the people who will use it

    One person can run a desktop install indefinitely. Two or more people sharing one assistant need a host they can both reach.

  2. 02

    Decide when it must answer

    If the assistant only has to work when your laptop is open, the desktop is enough. Scheduled runs and out-of-hours replies need a host that never sleeps.

  3. 03

    Count the channels

    One channel on one machine is a desktop job. A shared assistant in several team channels is a hosted job, mostly because of credential handling.

  4. 04

    Decide who owns maintenance

    Self-hosting means you own installs, upgrades, backups, and restarts. Managed hosting means you own configuration and channels, and hand over the rest.

  5. 05

    Start on the desktop anyway

    Evaluate locally first, then move. The configuration and memory format carry across, so the evaluation is not throwaway work.

Four-step path

How do you decide between desktop and managed hosting?

Four questions settle it for almost every team: who uses it, when it must answer, how many channels, and who maintains it.

  1. Step 01

    Count the people who will use it

    One person can run a desktop install indefinitely. Two or more people sharing one assistant need a host they can both reach.

  2. Step 02

    Decide when it must answer

    If the assistant only has to work when your laptop is open, the desktop is enough. Scheduled runs and out-of-hours replies need a host that never sleeps.

  3. Step 03

    Count the channels

    One channel on one machine is a desktop job. A shared assistant in several team channels is a hosted job, mostly because of credential handling.

  4. Step 04

    Decide who owns maintenance

    Self-hosting means you own installs, upgrades, backups, and restarts. Managed hosting means you own configuration and channels, and hand over the rest.

  5. Step 05

    Start on the desktop anyway

    Evaluate locally first, then move. The configuration and memory format carry across, so the evaluation is not throwaway work.

Uptime and availability

A desktop install is available when your machine is. A managed deployment is available when your team is, including nights, weekends, and holidays.

  • Desktop: stops when the laptop sleeps or closes.
  • Managed: runs on infrastructure designed to stay up.
  • Scheduled jobs only fire reliably on an always-on host.
  • A shared channel needs a host that does not belong to one person's machine.

Sharing one assistant across a team

Managed hosting gives everyone the same assistant with the same memory, which a per-machine install cannot do.

  • One runtime means one set of memories and skills.
  • Access can be scoped per channel instead of per machine.
  • Credentials live in one auditable place.
  • Onboarding a new teammate is a channel invite, not an install.

Who maintains it

Self-hosting and desktop installs put upgrades, backups, and restarts on you. Managed hosting removes the server work and leaves configuration to you.

  • Desktop: the installer handles setup, you handle versions.
  • Managed: the platform handles hosting, restarts, and upgrades.
  • Either way you own provider keys and channel credentials.
  • Either way you should still back up configuration and memory.

How do the costs compare?

The desktop is free to run apart from model usage. Managed hosting trades a predictable plan fee for removed operational work.

  • Desktop: model usage only, plus your own time on upkeep.
  • Self-hosted server: lowest per-message cost, real operational load.
  • Managed: a plan fee against a VPS bill plus maintenance hours.
  • Count the hours before deciding the managed option is expensive.

Which should you pick?

Desktop for personal evaluation and single-person use. Managed hosting once the assistant has users, channels, or a schedule that cannot wait for your laptop.

Which primary sources support this page?

Product behavior is checked against the current deployment flow. These external links provide the upstream project or channel documentation used for setup details.

Direct answers

Frequently asked questions

Can I start on the desktop and move later?

Yes. The configuration and memory format carry across, so a desktop evaluation becomes the starting point rather than wasted work.

Does managed hosting mean I lose control of my data?

No. You still own provider keys and channel credentials, and you should keep backing up configuration and memory wherever the agent runs.

How many people can use one desktop install?

Practically one. A shared assistant needs a host everyone can reach, which is the main reason teams move to managed hosting.

Do I need a VPS either way?

No. That is what managed hosting removes. You only need a VPS if you specifically want to own the server and its maintenance.

Key takeaways

  • Both run the same agent; they differ in who keeps it alive. The desktop app is the fastest way to evaluate Hermes Agent and a perfectly good permanent home for a single person. Managed hosting answers a different question: what happens when other people depend on the assistant, or when it has to respond while your machine is closed.
  • Start with one model, one channel, and one controlled test conversation.
  • Use managed hosting when deployment speed matters more than operating the server yourself.

Put Hermes Agent in the channel where the work already happens.