This documentation site is about the unstable (upcoming) Comentario version.  Switch to the stable version »


What is required for running Comentario

Please read this first: this page explains what you’ll need to self-host a Comentario instance.

If you’re interested in building Comentario from the source code, please refer to Building Comentario.


Comentario requires a PostgreSQL database instance for storing comments, users, domain configuration etc.

It doesn’t matter where exactly this database is running — on the same machine, on another machine, in the cloud — as long as it’s reachable by the Comentario server.

An important thing to consider, however, is the round-trip time to the PostgreSQL server. Any network latency will negatively impact the overall server performance, so it’s a good idea to make sure the database network connection is as fast as possible.

Supported PostgreSQL versions

At the time of writing, comentario supports all PostgreSQL versions from 10 up, with 16.x being the latest available.

Please note, however, that it’s usually a good idea to use the latest available software version because of security updates and bug fixes; or, at least, the latest minor version of a major version, for the same reason.

Comentario server

The Comentario server, or the backend, currently supports the following architectures:

  • linux_amd64 (Linux x86_64, 64-bit).
  • linux_arm64 (Linux AArch64/ARMv8, 64-bit).
  • linux_armv6 (Linux ARMv6, 32-bit).

Each of these architectures is built twice:

  • Statically linked;
  • Dynamically linked.

The above flavours are assembled into a number of binary packages and tarballs: see the Releases page for available artifacts.

The official Docker builds are based on Alpine Linux and contain a statically-linked linux_amd64 binary.

It’s also possible to run Comentario on a “full-fledged” Linux variant (such as Ubuntu or Fedora), as well as to link it dynamically against libc or musl (see Building Comentario).