Skip to content

Security

How Hedlo protects your installation, and how to tell us about a vulnerability.

Report a vulnerability

Email [email protected] with the affected version, the steps to reproduce and the impact you see. We reply within three working days and keep you updated until a fix ships.

[email protected]
  • Please give us a reasonable time to fix the issue before you publish it.
  • Do not access data that is not yours, and do not degrade other people's service.
  • Test only against installations you own.

How Hedlo is built

Signed releases

Every release archive is listed in SHA256SUMS, which is signed with Ed25519. Installers refuse archives that do not match.

Signed plugins

Plugins and themes only install when signed by a key you trust, and you review their permissions first.

Sealed secrets

Node tokens, database passwords and integration secrets are encrypted at rest with a vault key that never leaves your server.

Strong sign-in

Passkeys, TOTP two-factor, per-account and per-address limits, and session rotation on sign-in.

Separated apps

Staff, customers and the API run as separate apps, so a customer session can never reach admin pages.

Hardened nodes

Shuttle drops privileges, confines containers and filters their outbound traffic.

Security guides