Encrypted secrets
OAuth tokens, API keys and SMTP passwords are encrypted with AES-256-GCM.
Harly is self-hosted and open source. You decide where candidate data lives, who can see it and how long you keep it.
OAuth tokens, API keys and SMTP passwords are encrypted with AES-256-GCM.
Passwords use scrypt. API keys and tokens are stored as SHA-256 hashes.
HSTS in production, and automatic certificates with the bundled Caddy proxy.
Add one flag to encrypt database backups with age.
On sign-in, password reset, the API, apply forms, uploads and more.
Webhooks and outbound requests can’t reach private networks.
File type, content and size are validated before anything is stored.
Incoming and outgoing webhooks are signed and verified.
Harly is MIT licensed. Audit it yourself or have your security team do it.
View on GitHubSend reports privately through GitHub Security Advisories.
Report privatelyRun npx @harly/cli doctor to check your configuration against the security baseline.
On the servers you run Harly on: your Postgres database and your file storage, either local disk or an S3-compatible bucket. There is no hosted version of Harly, so the data stays on infrastructure you control.
Only to the integrations you turn on, such as your calendar, email provider or AI provider. The web app sends no usage telemetry.
No. Harly is open-source software you run yourself, so your own infrastructure and processes determine your compliance. You can read every line of the code on GitHub.
Harly includes tools for GDPR workflows: consent records, export and erasure requests, legal holds and retention policies. How you configure and run them is up to you.
Report it privately through GitHub Security Advisories on the Harly repository. Please don’t open a public issue.
Open source. Self-hosted. Built for growing teams.