What's new in hetsnap

A lot has landed over the past few weeks. Here is a quick look at everything that is new, improved, or fixed.

Email reports

You can now configure automated email reports for any set of servers. Pick a delivery schedule — daily, weekly, or monthly — add one or more recipients, and hetsnap sends a summary of snapshot activity, storage usage, and any failures straight to your inbox.

Reports are great for keeping a team or a client in the loop without anyone having to log in. Each report shows all snapshots created during the analysis period, their sizes, and any errors that occurred. You choose how far back to look: 1, 3, 7, 14, or 30 days.

Manual sync buttons

Servers and snapshots are synced automatically every few minutes, but sometimes you want data right now. Both the Servers and Snapshots pages now have a Sync button that triggers an immediate refresh from the Hetzner API. You will see a notification as soon as the sync starts so you know it is running.

The same button is available inside each server's detail view, so you can refresh that server's snapshots without leaving the page.

Feedback when connecting a project

When you connect a new Hetzner Cloud project, hetsnap now confirms that the sync has started with a success notification. Your servers and snapshots will appear within seconds — no need to refresh the page manually.

Documentation

hetsnap now has a full documentation site at /docs. It covers everything from connecting your first Hetzner project and setting up a backup schedule to understanding retention policies, reading email reports, and managing billing.

The docs are linked from the main navigation and from the hero section of the landing page.

Reliability improvements

A few quieter fixes shipped alongside the visible features:

• Fixed a crash that occurred when Hetzner returned a snapshot without a created_from field — this happens when the source server no longer exists.
• Sync jobs triggered from project creation are now scoped to that single project, so other tenants' data is not touched unnecessarily.
• Snapshot deletion no longer silently swallows errors — failures are now logged with full context for easier debugging.

What's next

We are working on snapshot restore instructions, Slack and webhook notifications for backup failures, and a more detailed storage breakdown per project. If there is a feature you would find useful, drop us a line — we read every email.