I grew up on an internet that felt alive. Personal sites, weird tools, software built by people who had opinions. You could feel the human being on the other side of the thing they made.
Somewhere in the last decade that went away. Not all at once. Gradually, then suddenly. Everything became the same five products. Same rounded corners, same onboarding flow, same privacy policy written to protect the company and nobody else. The internet started feeling like IKEA, functional, inoffensive, and completely indifferent to you.
I can't fix the internet. I'm one person in Lithuania with a day job, a half-built house in Labanoras, and a toddler who started figuring out the world in July. I build after work, after the kid is asleep, in the hours that aren't spoken for. Sleep is the thing that gives.
But I can build one thing the way I think it should be built.
The premise
File transfer felt like the right place to start. Small enough to be doable alone. Useful enough to matter. And thoroughly, depressingly enshittified. WeTransfer got acquired, gutted the free tier, then quietly updated their ToS to claim rights to train AI on your files. The alternatives are mostly Google products or trying to become one. Nobody was building it like they gave a shit.
So I did.
The premise was naive: file transfer should just be free.
Not free-with-limits. Actually free. No account, no size limit. Sessions stay open for hours, long enough that "both people need to be online" stops being a real constraint for most transfers.
How it actually works
That's not a business model. So I built a dual approach.
P2P for direct one-to-one transfers. Files travel directly between browsers over WebRTC, no file storage on my end. Unlimited size. No account. The sender stages files, leaves a tab open, the receiver joins within a few hours and the transfer starts automatically. The sender's tab is the server. Nothing to store, nothing to breach, nothing for anyone to train a model on.
It sounds simple. It's not. Browsers were never designed for this. They break in creative ways once you push past a few gigabytes. But it works, and it works well enough that people use it for real things.
The cloud tier exists for one-to-many sharing and real async delivery. When you need to send something to multiple people or can't keep a tab open. That's also where the money comes from, so I can keep working on things I find interesting.
The unexpected second act
Then something unexpected happened.
Once the P2P architecture was solid I realized the same properties that make it good for humans make it good for agents. No UI to navigate. Structured output. Scriptable. Headless.
Every major file transfer service assumes the user has hands. Increasingly that assumption is wrong. Agents run pipelines at 3am. Automations need to move files between steps without a human anywhere near the screen. Nobody had built for that.
So I built around it. CLI with JSON output. npm package. A2A agent card. llms.txt. Agent-native from the start, not retrofitted.
The name
The name comes from Perkūnas, the Lithuanian god of thunder. He's not Zeus, remote, political, self-interested. He's the one who actually shows up. Perkūnas is active, furious, and on your side. His eternal enemy steals what belongs to the living and drags it underground. Perkūnas chases it across the sky and strikes it where it hides.
Yes, I created a business to lecture people about Lithuania.
What this is
Perkoon is not trying to be the next WeTransfer. It's trying to be the thing that exists after you stop trusting WeTransfer. Fast, weird, honest about what it is. Built by one person who wanted the internet to feel like something again.
It's free to use.
Perkoon is free to use. If you're building agent workflows, the automation docs are at perkoon.com/automate.
Top comments (0)