Support and contact

Before writing to us

Two reflexes that answer most questions:

1. This documentation’s search (top left) covers the whole corpus.
2. The frequently asked questions gather the most common cases.

Reporting a problem

What makes a report actionable:

• Your version and your edition: the leftmost cell of the status bar shows Restorm v<version> - <Plan>;
• Your operating system and the installation method (AppImage, .deb, .rpm, Windows installer, .dmg);
• The steps to reproduce;
• for a problem with a scenario, the execution log — the copy button produces text ready to paste;
• for a network problem, the matching block from the console, which is already a reproducible shell command.

Caution

Before pasting a log or a command, read it over: it may contain a token or an identifier. The secrets Restorm knows about are redacted, but a value you typed in the clear into a field is not.

Requesting a feature

Describe the problem rather than the solution: what you are trying to do, what is blocking you today, and what you do instead. That is what makes it possible to propose the right answer — sometimes a feature that already exists.

Priority support

The Pro and Enterprise editions include priority support. See Plans and capabilities.

Getting in touch

From restorm.app — and, for any commercial or Enterprise-plan question, from restorm.app/pricing.