Made by someone who patches servers for a living.

Marshal is built by a systems engineer in the EU who looks after Windows and Linux servers for many customers, day to day. Every month that meant the same work: deciding which updates go where, waiting for the right hour, rebooting servers in the right order, and checking each one came back before touching the next.

Marshal started as the in-house tool for exactly that job: first an Ansible-based tool, then its own agent, once remote logins, jump hosts and stored server passwords became the weak spot. It became a product when it was clear that other small teams and MSPs had the same problem, and that most tools treat server reboots as an afterthought.

We’re small, and we say so. That’s why Marshal is self-hosted, why Free needs no account, and why everything on this page is written down.

What Marshal is, and isn’t

Marshal does server patching orchestration: approvals per customer, install and reboot windows, reboots in order, health checks, and a run that stops when something goes wrong. On Windows Server it works with Windows Update, on Linux with apt or dnf.

• Operating-system updates only. No third-party apps, by design. Keep patching browsers, Java and the rest with the tool you already have.
• Not an RMM. No inventory, monitoring, remote access or app deployment. Keep Intune, Action1 or your RMM for laptops and desktops, and let Marshal handle the servers.
• Built for small teams. In-house IT and small MSPs, from a handful of servers up to a few hundred machines across many customers.

Support

Write to us any day, at any hour. We answer every message within a week. Support is by email at [email protected], for every edition, Free included. Security reports go to the same address.

If something is urgent, say so in the subject. The docs cover most questions before you need to write.

If we stop

A small vendor is a fair worry. Our promise first: If we ever shut down, every Pro license you have paid for becomes unlimited: it never expires and needs no check-in. We do that before we go, so it doesn’t depend on us afterwards.

And here is what happens to a self-hosted console if we simply stop answering:

• The console, its database and the agents run on your servers. Patching never goes through us.
• Free never checks in with us. It keeps working, with all its patching features, for as long as you run it: 1 organisation, up to 25 machines.
• Pro checks in once a day for its license. If we can’t be reached, nothing changes for 30 days; then come 30 days’ grace; then the console goes read-only until an admin switches it to Free with one click.
• Nothing is ever deleted. Over Free’s limits, the oldest customers, machines and users stay active and the rest wait, intact.

Get in touch

Sales, support, privacy and security: [email protected]. Everything goes through that one address.