Skip to content
Ashlane

One pipeline from build server to player disk

The platform has five parts. You can use one of them or all of them, and each has the same dashboard, the same API and the same invoice.

Chisel delta engine

You push a build directory. Chisel compares it with the previous release using a rolling hash over content-defined chunks (64 KiB average, 16 KiB minimum, 256 KiB maximum), then runs a second pass on executables and shared libraries that understands relocations, so a recompiled binary diffs to kilobytes instead of megabytes.

Chunks are compressed with zstd. Hot releases use level 9 for fast first delivery, then recompress at level 19 in the background once traffic settles. Version 2.9, released 23 September 2026, cut median patch size on our benchmark set by another 6%.

How delta patching works

Ashlane Edge

A two-tier cache: 24 edge sites in front of four regional shields. A chunk that no edge holds is fetched once per region, not once per site, so a launch against a cold origin produces a handful of origin requests rather than thousands.

Connections are HTTP/3 with HTTP/2 fallback, and TLS sessions resume across sites so a player who changes networks mid-download does not start over. Range requests are aligned to chunk boundaries. Pre-warming lets you push a release into every edge before the embargo lifts.

Launcher SDK

A native library, not a web view. It owns the boring parts of installing a game: free-space checks, resumable downloads, atomic swaps, file verification and repair, and polite bandwidth use when the player is also on a video call.

The progress API reports bytes that will actually cross the wire, after delta and compression, so your progress bar matches the download. Version 3.4.0, released 28 October 2026, can resume an install after the disk fills and the player frees space, without re-verifying finished files.

Launcher SDK guide

Signed manifests

Every release is described by a manifest listing each file and chunk hash. The manifest is signed with an Ed25519 key that you hold. Clients refuse any build whose signature does not match, so a compromised cache or a tampered mirror cannot ship code to your players.

On Launch and Enterprise plans the signing key can live in a hardware module, and rotation is a documented, two-step process that never strands old clients. Read how rotation works.

Pulse analytics

The studio dashboard shows each rollout as it happens: percent patched, bytes delivered by region and platform, install failures by error code, and the slowest ten autonomous systems for your players. Export to CSV or stream events to your own warehouse.

Guardrails watch the same signals. If install failures on a channel exceed 2% for ten minutes (the default), the rollout pauses and the on-call contact is paged.

What each plan includes

PlaytestStudioLaunchEnterprise
Titles110UnlimitedUnlimited
Builds retained per title330200Custom
RegionsEurope, North AmericaAll fourAll fourAll four, reserved lanes
Staged rollouts and guardrailsNoYesYesYes
Manifest signingShared keyYour keyYour key in an HSMYour key in an HSM
Origin storage included50 GB1 TB5 TBCustom
Launch rehearsalNoGuideWith an engineerTwo per year
Uptime commitmentNone99.9%99.95%99.99%

Prices and egress allowances are on the pricing page.