All articlesSharing

How developers deliver builds and install packs to clients in 2026

Developers still add a client to the repo, or smash a build that dies before QA. Build delivery in 2026 is one URL: notes they can read, a price if they owe you, the zip they can install in week six.

Henrik Aalto

TurkuUpdated 3 min read

How developers deliver builds is still, in too many shops, a repo invite or a smash that expires before QA. Each hop is a place a client stalls, or walks the working tree. Build delivery should be one door they already have open.

This is the year of jobs: a staging zip, a production pack, docs, a revision. Agencies have the deck cousin. This page is the install.

Notes they can read. The build stays packed. Approval or checkout ships the zip.

Why builds still wander

  • A repo seat is a room in your house.
  • A smash expires before the release window.
  • A new PM asks in week six. The zip is gone.
  • The remaining fee is unpaid, and production already left.

How this looks on a year of ships

Staging

A changelog and a build they can install. Password the door. Not a seat on main. Replace the zip when the build moves. The URL does not change.

Production

The pack they go live with. If the remaining fee is due, put the price on that URL. Get paid before sending files.

Docs

A readme, env notes, versions. Put them in the same folder so the pack is complete. Sample pages in the unpaid view if the docs are the product.

Hotfix

Replace the file. Tell them the URL did not change. A new smash for every patch is how versions get lost.

The repo stays yours. The install pack is the door the client opens.
What you getA split build hand-offOne install link
They read the notesA Slack dumpA changelog on the page
They pay if a fee is dueInvoice in another appCheckout on that URL
They get the zipA repo seat or a smashUnlock on the same page
A new PMRebuild the archivePoint at the same link

  1. Put this release in one folder

    The zip, the changelog, env notes. Nothing from another client.

  2. Decide the unpaid view

    Notes they can read. Not the production zip if money is due.

  3. Price it if they still owe you

    The studio payment link is the folder. When checkout completes, the same URL is the download.

Spike takes 5% on Free, 1% on Pro, 0% on Business, from the payout, when you price the folder. Sharing can stay free when the fee already cleared. Free shares last three days. A release window that slips belongs on Pro or Business. How freelancers deliver files is the generic year. Write the node version and the env keys they must supply. People install these packs at midnight. The page should already have answered the run question. Changelog text lives next to the zip, not in Slack.

If they can read the notes, they should be able to take the build without a seat on your repo.

Questions

Good to know

Put the install pack and a changelog in one folder. Let them read the notes. Do not add them to the repo. Unlock the zip on that URL after approval or payment.

Keep reading

Related articles

Try the workflow in the article.

Upload a folder, protect the preview, share or sell from one link.

Product guides