Start with an evaluation deployment
Palpo combines a Rust/Salvo application with PostgreSQL. Its README documents Rust 1.94 or later and PostgreSQL 16 or later for the inspected source baseline. Confirm the current toolchain and deployment guide before building a different revision.
Use a dedicated evaluation database and back it up. Palpo’s maintainers describe large-scale, long-running production evidence as an ongoing effort; select your deployment purpose accordingly.
Build and configure
The source path below builds the server. Copy the documented example configuration and set the server identity, PostgreSQL connection, listener, and public URL before starting it. Docker deployment is also documented upstream; pin an image appropriate to your evaluation.
git clone https://github.com/palpo-im/palpo.git
cd palpo
cargo build --release
cp palpo-example.toml palpo.tomlVerify the path your clients use
Confirm HTTPS, authentication, room history, media, and sync through the public URL the client will use. A process running on the server does not prove the route from a user’s device works. For Robrix2, verify native Sliding Sync support on the selected build.
Decide whether to enable federation and configure its discovery and network requirements separately. The Hagency web-admin companion is a distinct Node service and is not part of the v0.4.0 server package.