Overview

Overview

How a self-hosted Personal Agent Proxy fits together, and the ways to run it.

Personal Agent Proxy is one server and a Postgres database, on one address such as https://proxy.example.com.

What runs

PartWhat it does
Personal Agent ProxyThe ghcr.io/personalagentproxy/proxy image: the api and the web app on port 4000. It applies the database migrations every time it starts.
PostgresAccounts, agent logins, the activity log, and connections' credentials and vault entries, which are stored encrypted.
CaddyHTTPS in front of Personal Agent Proxy, with certificates from Let's Encrypt. Any reverse proxy that terminates TLS works in its place.

The server needs to reach the services you connect: for email, IMAP on port 993 and SMTP on 465 or 587.

Ways to run it

OptionForYou look after
Docker ComposeOne server, or trying Personal Agent Proxy on your own computerThe server, backups and upgrades
The image on its ownA container platform, such as Render, Fly or Kubernetes, with a managed PostgresHTTPS in front of it, and the database

What you need

  • A server with Docker and Docker Compose. A small one is enough for personal use.
  • A domain name for it, so Caddy can get a certificate.
  • Optionally, a Google OAuth client and a Resend account, for signing in with Google and receiving sign-in links by email.