About Fork
What Fork is
Most software never gets written. Not because the idea was bad, but because the distance between "I wish I had an app that…" and a running app is measured in toolchains: a language, a framework, a build step, a deploy pipeline, a store review. Every one of those is a place to give up.
Fork removes the distance. You describe the app in plain language. Our agents build it, host it, and put it on every platform you care about. There is no npm, no config file, no deploy. The app exists a few minutes after the sentence does.
What comes out is not a mockup or a code snippet you still have to run somewhere. It is a working app with a URL, a backend, storage, and an install button.
Why I built it
I've always built tools for myself — small things that made my own life easier and a lot of it more comfortable.
What I needed was a place to keep them. I wanted them on my phone, and nothing out there could do that. So I built Fork. I hope it improves your work and your life as much as it improved mine.
How it works
Two agents do the work. Manager talks to you, asks the questions worth asking, and plans the app. Builder writes the frontend and the backend and ships them. You watch it happen in the chat, and you can interrupt at any point — it is a conversation, not a form submission.
You choose the model per app: Claude Sonnet, Claude Opus, or Gemini 2.5 Pro. Swap anytime. The app itself can call those models too — every app you build has an AI teammate inside it, with no API keys to manage.
Apps are self-contained by design. No build tools, no dependency tree to rot. That constraint is what makes an app forkable: anyone can take yours, change one sentence, and have their own version running immediately.
Where your apps run
Ship once and the app is available on iOS, Android, the web, and inside Telegram — automatically, from the same source. Native builds are real native builds, not a web page in a frame.
Every app gets its own address at {app-id}.fork.me and a clean link at
fork.me/{handle}/{app} you can hand to a friend. The Fork SDK ships with
audio, video, image generation, games, push notifications, calls, and a component
library, so an app can be a toy, a tool, or a small social product without leaving the
platform.
What we believe
Software should be personal
The best app for tracking your weight, your D&D rolls, or your sister's birthdays is the one shaped exactly around you. That app is not worth a company. It is worth a sentence.
Forking is the point
An app you can read, copy, and change is worth more than an app you can only use. Every app on Fork carries its own fork button. Remixing is not a feature we added — it is the reason the platform is called Fork.
Your apps are yours
We provide the road and the road signs. What you build on it belongs to you. We do not sell your data and we do not run third-party advertising or analytics cookies — see the Privacy Policy and the Cookie Policy.
The company
Fork is built by FORK Apps, Inc., a Delaware corporation. We are a small team, and we use the product every day — most of what ships was first an app one of us wanted and did not want to build by hand.
If you are building something on Fork and it breaks, tell us. If you are building something on Fork and it works, tell us that too — we read everything.
Contact
FORK Apps, Inc.
1111b South Governors Avenue, Suite 84934
Dover, DE 19904, United States
General: hi@fork.me
Support: fork.me/support
Abuse / takedown: abuse@co.fork.me
Copyright: fork.me/dmca
We post what we ship on Telegram at @forkapps.