Software Distribution

Signed update packages, per-client entitlements, installs with automatic rollback and application health checks. Secure delivery to customer sites.

On-prem software distribution and updates

If your software runs on customer servers, every update is a risk: files copied by hand, versions drifting apart between customers and no visibility into where an update failed. We built a platform that closes this problem.

How it works

• Cryptographically signed release packages (ECDSA P-256) — the customer's server installs only what genuinely comes from the vendor, with a standby key ready for rotation
• Per-client entitlements — release channel, maximum available version, support period and the ability to suspend access, checked on every download
• Selective component updates — the customer downloads only the parts of the system that actually changed
• Resumable downloads of large packages with checksum verification of every component
• Installs with automatic rollback — after an update the system checks the application's health itself; if the check fails, the previous version comes back automatically
• A version overview — who runs which version, when they last checked in and where an update failed

Honest about downtime: a component update happens in a short, announced maintenance window — users see a maintenance page during the swap, and the system returns to service after the health check passes.

Who it is for

Software vendors who ship their systems to customer environments — and companies that want to bring order to updates of their own internal applications. This is the channel we use to deliver our own software to on-premises installations; we can deploy the same mechanism for your product.

Let's talk about distributing your software

Tell us how your releases reach customers today — we will show you what it can look like with a signed update channel.