Eight.ly Platform Services
The product continues after checkout.
A working operating system still needs a way to reach its buyer. We built the licence and update service, catalog delivery and supporting distribution that connect Eight.ly's storefront to a running appliance.
Explore Eight.ly- End to endpurchase through activation
August 8, 2026 real production order verified checkout, signed notification, emailed key, appliance activation and download access.
- Homebrew + Scoopdistribution channels
Package definitions make installation part of the supported product path.
- Offline catalog useupdates without constant permission checks
The downloaded catalog stays available between syncs.
- PurchaseReceive and verify the order notification.
- Deliver the keyIssue the licence and email it to the buyer.
- ActivateBind the installation to an available licence seat.
- MaintainServe eligible releases, changed catalog content and documentation.
The problem
Checkout, licence creation, email delivery and activation can all work independently while the complete purchase fails. Synthetic requests can even confirm the wrong assumption on both sides. Until the real sequence runs, the most important integration is still unproven.
An installed appliance adds another constraint: a licensing or update service should not become a hidden dependency for every local action. Catalog updates need access control without making the last downloaded catalog disappear when the internet does.
Who it’s for
For customers installing and maintaining Eight.ly, and for software businesses that need their commercial and technical systems to behave as one product.
What we built
We built the service that verifies purchase notifications, issues licences, emails keys, activates installations and serves licensed release and catalog downloads. Supporting work includes Homebrew and Scoop distribution definitions and the Eight.ly wiki.
Licence seats belong to explicit installations. The documented service tracks separate activation tokens, supports releasing a seat and records licence events. Software delivery and entitlement have their own checks rather than treating possession of a download URL as proof of everything.
How it works
A verified order notification creates the licence. The buyer receives the key and uses it to activate an installation. That installation then presents its activation token when requesting protected updates and catalog content.
Catalog manifests carry content digests so a client can identify what changed. Release delivery identifies the correct artifact, while local catalog data remains available between syncs. The distribution definitions and documentation give the surrounding installation work a maintained home.
What was hard
The first real order exposed a subtle signature defect: the service checked a reconstructed JSON document instead of the exact bytes the payment service signed. We corrected the contract and repeated the real delivery. In August 2026, checkout, email, activation and downloads completed in sequence on the production systems.