Last reviewed: 2025-12-08 / Plakar v1.0.6
By default, Plakar works without requiring you to create an account. You can back up and restore your data with just a few commands, without depending on external services.
Logging in unlocks additional features. These features are entirely opt-in.
Why log in?
As of today, logging in is useful for two main reasons:
- Installing pre-built packages from Plakar’s servers (integrations such as S3, SFTP, rclone).
- Enabling alerting, which provides reporting dashboards and email notifications.
More features may require login in the future.
1. Install pre-built packages
Plakar provides multiple integrations, such as:
- S3
- SFTP
- rclone
You can build these integrations from source or install the pre-built versions hosted on Plakar’s servers using the UI or plakar pkg add.
2. Alerting
When logged in and alerting is enabled, Plakar sends non-sensitive metadata to Plakar’s servers whenever you run backup, restore, sync, or maintenance operations.
This metadata powers:
- A reporting dashboard in the UI
- Email notifications about backup status
Backup data is never sent to Plakar.
Alerting notifies you quickly if something breaks — especially useful for individuals and small teams without dedicated monitoring.
How to log in
Using the UI
- Run
plakar ui. - Click the Login button.
- Open Settings to enable alerting and email reporting.
Using the CLI
Log in using GitHub or email:
plakar login -github
plakar login -email myemail@domain.com
After logging in, enable alerting (optional):
plakar service enable alerting
plakar service set alerting report.email=true
Non-interactive login (CI, SSH, automation)
While this version allows generating authentication tokens, the CLI cannot consume them. Support for token-based non-interactive login was introduced after the release of v1.0.6.
Found a bug or mistake in the documentation? Create an issue on GitHub