Documentation
Omnihorn delivers signed updates to desktop apps. Pick how you want to get set up.
If you are an AI agent
Go here. A runbook your coding agent follows to set up releases for your repository, plus the one prompt you paste to start it. It stops and asks you only for what an agent cannot do: sign in and create the key.
Open the agent runbookIf you are a human
Go here. Detailed guides, from your first build to a team release process and an enterprise rollout, in about twenty minutes for the first install.
Start with the quickstartStart by role
Developers
Integrate Omnihorn, automate releases, understand what runs on the user’s PC.
Release managers
Plan releases, stage them to testers first, keep rollback one click away.
QA
Test a build on a private channel, check updates and rollbacks before users see them.
IT, security and enterprise
Security model, signed updates, silent and all-users installs, data handling.
All guides
Get started
- Get started with OmnihornSign up, create an app, upload your Windows build, build the installer and watch the first update arrive. A 20-minute walkthrough for developers.
- How Omnihorn worksApps, builds, channels, the signed manifest, the installer and the update loop: how a release travels from your upload to every installed copy.
Ship releases
- Upload buildsDrag a folder or archive into the dashboard, set the version and release notes, and see what happens after upload: scanning, signing, channels, retention.
- Upload builds from CI/CDUpload Windows builds to Omnihorn from GitHub Actions, GitLab or any CI: API keys, workflow inputs, branch channels, tags, matrix builds and fixes.
- Channels, rollouts and rollbackHow Omnihorn channels decide which build installed copies get: access modes, assigning a build, beta and production, branch channels and rolling back.
Installer
- Installer StudioDesign the Windows installer your users run: its look, what it launches, start-up and shortcut offers, one installer per channel and the download page.
- What happens on your users’ PCsWhere Omnihorn installs your app, how often it checks for updates, what it verifies, how it applies and rolls back, the silent command line and uninstall.
Teams and enterprise
- A release process for teamsSet up a team release flow for a desktop app with Omnihorn: member roles, test, beta and production channels, a rollback plan and a release checklist.
- Test a release before users get itHow QA tests a Windows release on Omnihorn: private test channels, the test installer, a scripted update check, a rollback test and a regression checklist.
- Security and update integrityHow Omnihorn protects desktop updates: a per-app Ed25519 signature, SHA-256 per file, atomic apply with rollback, path checks, channel access and API keys.
- Enterprise deploymentDeploy an Omnihorn-delivered Windows app in an organisation: install scope, silent install and update, private channels, change control and data handling.
Help
- TroubleshootingFixes for common Omnihorn problems: failed uploads, builds stuck in processing, channel errors, installer builds, updates that do not arrive and CI failures.
- Frequently asked questionsShort answers about Omnihorn: supported platforms, shipping and rolling back releases, the Windows installer, update security, plans and enterprise use.
New here and just looking around? The blog explains the ideas without assuming you use Omnihorn yet.