1% of the bytes
A 2 GB monthly upgrade typically transfers about 20 MB. Lower bandwidth bill, faster updates, happier users.
Ogamita Delta OTA
Ship the change, not the whole release.
Efficient over-the-air software distribution for multi-GB applications: binary deltas, atomic switch-over, a self-contained client, and AGPL plus commercial licensing.
Vanilla auto-updaters re-download the full payload at every release: 1 to 4 GB per user per month for a typical desktop application. Ogamita Delta OTA ships only the binary delta between two releases, typically about 1% of a full reinstall.
Users on flaky Wi-Fi, constrained corporate VPNs, and laptops that go on and offline can update reliably without paying the cost of a full payload every time.
Why It Matters
Delta OTA is built for products where update reliability, bandwidth, and operational control are product concerns, not afterthoughts.
Never breaks the install
Atomic switch-over: the agent flips to the new release only after the bytes have been downloaded, hashed, patched, re-hashed, and extracted. Failures leave the prior install untouched.
Zero-dependency client
Single static binary per OS. No DLL hell, no admin rights, no OpenSSL, no installer. Drop it next to your app.
Cryptographically signed
Every release manifest is Ed25519-signed and pinned to the publisher's public key. Tampered bytes are refused before a single file is written.
The Numbers
Operational targets from the Delta OTA marketing datasheet.
~1%Typical upgrade transfer as a share of the full blob.
~10 MBClient binary size.
0Client runtime dependencies.
~80 s10,000 simultaneous upgrades on 2 x 10 GbE.
8 GBMaximum supported release blob, configurable.
3Client OSes: Windows, macOS, Linux.
How It Works
Publish, distribute, and switch over without leaving users in a broken intermediate state.
1. Publish
Your CI runs ota-admin publish. The server hashes the payload, deterministically packs it, and builds binary patches against every prior release.
2. Distribute
The agent fetches the signed manifest, picks the smallest viable patch, downloads it with streaming SHA-256 verification, and reconstructs the new release locally.
3. Switch over
The new distribution lands in a sibling directory. Once verified, an atomic symlink flip points current at it. Old material is pruned automatically.
The client side, in one command:
$ ota-agent install schms \
--server https://ota.example.com \
--install-token YOUR_TOKEN \
--latest
installed schms 3.4.1
What You Get
A complete update system for server, client, operations, and documentation.
| Server | Linux x86_64 / arm64. Multi-arch container image. HTTP/JSON API. sendfile(2) for blob downloads. SQLite catalogue, PostgreSQL sub-phase. Filesystem or S3 storage. |
|---|---|
| Client library | Embeddable C-ABI shared library plus static archive. Pure-Go internals, no cgo, no OpenSSL. libota.h header for Python, .NET, and AutoLISP integration. |
| Client CLI | Single-file ota-agent per OS, about 10 MB. Commands include install, upgrade, revert, doctor --recover, and watch. |
| Operations | Garbage collection, content-integrity verification, backup/restore scripts, audit log, install-token bulk issuance, and recovery rollback to anchor releases. |
| Documentation | Datasheet, user manual, operator runbook, performance notes, and threat-model walkthrough, all PDF-ready. |
Licensing
Use Delta OTA under the AGPL for open-source work, or license it commercially for proprietary distribution.
Open source: AGPL-3.0-or-later
Free for open-source distribution and self-hosted use under the AGPL. If your service runs Delta OTA and is reachable over a network, your modifications must be made available to its users.
Commercial
If you ship libota linked into a proprietary application, or run a modified server without offering source to its users, a commercial licence from Ogamita Ltd keeps you compliant. Commercial terms can include support and response commitments.