For automation and CI

Make “send it to the client” a step in the pipeline.

The nightly export, the release build, the monthly report. If a person needs it, a job should be able to send it — without anyone opening a browser.

IMeet Ingrid, release engineerOslo · ships a desktop app every two weeks · an illustrative example

Release engineer

A week with Ingrid.

Release day
The build hands itself to QA.
The CI job runs yungle send on the build folder and gets the link back as JSON. The testers receive it without anyone copying files around.
API, CLI & MCP
When the runner hiccups
Interrupted uploads carry on.
If the job is interrupted, running the same command again continues from the last finished part instead of starting over.
Transfers
The day after
Check who has it.
The team gets a webhook when each build is downloaded, and a script records it.
Secure sharing

A signed webhook tells you when a client downloads; or poll the API.
API uploads beyond a free monthly allowance are metered; downloads never are. See the pricing page.

How do I install the CLI?

npm install -g yungle-cli. On your own machine, yungle login signs you in through the browser; in CI, store an API key as a secret instead.

Can a job send to several recipients?

Yes. A transfer can go to up to ten people at once, each with their own download receipt.

Is there an allowance for API uploads?

Yes. Every account gets a monthly allowance of free API uploads; the pricing page has the details.

10 GB, free, right now — no account, no card, no ads. Pay us only when you want your work to stay put.