For developers

Hand a big file to a human, from your code.

Your build, export or agent produces something a person needs. Yungle turns it into a link they can open, with download receipts you can read back.

JMeet Jonas, backend developer at a small SaaS companyBerlin · ships a nightly export to customers · an illustrative example

Backend developer at a small SaaS company

A week with Jonas.

Monday
The export that was too big for email.
Jonas replaces a flaky SMTP attachment with three API calls. The customer gets a link, and a dropped upload resumes instead of failing the whole job.
API, CLI & MCP
Wednesday
Did they actually get it?
Download receipts come back through the API, so the support team can answer “we sent it on Tuesday, you downloaded it at 09:14” without asking engineering.
Transfers
Thursday
A one-off from the terminal.
Someone needs the staging database dump. Jonas sends it from the CLI in one line, without opening a browser.
API, CLI & MCP
Friday
Letting an agent look, but not touch.
The team’s AI assistant gets the MCP server, which can read transfers and receipts but has no tool that sends, deletes or shares anything.
API, CLI & MCP

There are no webhooks yet. Poll for download receipts instead.
The vault and end-to-end encrypted transfers are not reachable through the API, and cannot be: their keys never leave the browser.
There is no service level agreement. Yungle runs on a single server.

Is the API available on the free tier?

Yes. Transfers are fully available through the API, CLI and MCP server without paying, with a monthly allowance of free API uploads.

How do I authenticate?

With an API key you create in the dashboard, sent as a bearer token. Keys can be revoked at any time.

Can the MCP server send files?

No. It is read-only on purpose: it can list and describe transfers and collections, and nothing else.

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