Skip to content

Architecture ​

SilentSuite self-hosting runs two containers on a single Docker network. You provide your own reverse proxy for HTTPS.

Overview ​

    Your Server                         SilentSuite Apps
  ┌─────────────────┐
  │  Your Reverse   │◄──────────── app.silentsuite.io
  │  Proxy (HTTPS)  │              (or mobile apps)
  └────────┬────────┘              enter your server URL
           │                       in Advanced Settings
  ┌────────┴────────┐
  │   SilentSuite   │
  │     Server      │
  │      :3735      │
  └────────┬────────┘
           │
  ┌────────┴────────┐
  │  PostgreSQL 16  │
  │    (internal)   │
  └─────────────────┘

Service Roles ​

ServiceImageRole
SilentSuite Serverghcr.io/silent-suite/silentsuite-serverSync server built on the Etebase protocol. Handles encrypted data sync, user authentication, and the admin panel. All data is encrypted client-side; the server never sees plaintext.
PostgreSQLpostgres, pinned to the immutable OCI index digest in the installed release bundleDatabase. Stores encrypted sync data and user accounts. Existing installations keep their installed digest. Only accessible within the Docker network.

The Compose file references no mutable image tag. The repository Compose file pins PostgreSQL 16.16-alpine to postgres@sha256:81e77a4833487b8132fe4b00bedd39dc3f74b8641e387f19312a48f7de218c2e, and the server image comes from SILENTSUITE_SERVER_IMAGE, which the installer writes as the release's immutable index digest. New installs use 16.16 only once a published release bundle includes that Compose file; earlier bundles keep the reviewed 16.9-alpine digest. Moving a tag upstream cannot change what your instance runs.

Network and Security ​

  • Both services run on an internal Docker bridge network (silentsuite).
  • PostgreSQL is not exposed to the host -- only the server container can reach it.
  • The SilentSuite server binds to 127.0.0.1:3735 -- not directly accessible from the network.
  • You bring your own reverse proxy (Caddy, nginx, Traefik, Cloudflare Tunnel) for TLS termination.
  • All sync data is end-to-end encrypted. The server stores only ciphertext.

Why No Web App Container? ​

Self-hosters only need the sync server. Users access SilentSuite through:

  • app.silentsuite.io -- the hosted web app (works with any SilentSuite server)
  • SilentSuite mobile apps -- available for Android

Both support entering a custom server URL in Advanced Settings during signup or login. This keeps the self-hosted stack minimal (2 containers) while giving users the full SilentSuite experience.

Data Volumes ​

VolumePurpose
pgdataPostgreSQL data directory
server_dataServer secret key and media files

Both volumes are Docker named volumes. They persist across container restarts and updates.

Released under the AGPL-3.0 License.