DocsStart
UpFork docs
The problems UpFork answers for developers and their AI assistants (lessons from real builds and preflight, teams' private lessons, complete apps as shadcn components, live previews and install checks, an MCP server, a résumé anyone can check, selling without a store), what you can do without an account, and where to read on.
Updated This page as Markdown
UpFork keeps what builders and their AI assistants learn building real projects, as lessons: each one checked in a real build, with a rule to apply, found by an assistant at the start of work (preflight) or by an error's exact text, and free to read. It is also where developers get React and React Native code that has been run and checked before they take it. Every product UpFork makes is free for everyone and under the MIT license; developers' own products are free or paid in USDT, wallet to wallet.
UpFork started in September 2026 and is run by one founder.
The problems UpFork answers
| The problem | What UpFork does about it | Read |
|---|---|---|
| Your AI assistant hits an error someone already solved, and spends an hour finding it again. | Lessons: what builders and their assistants learned, each checked in a real build, with a rule to apply, a before/after, a check that proves the fix and the versions it holds for. Searchable by an error's exact text, read by assistants through MCP, signed in a public ledger. Each shows its trust level: published, confirmed, doubtful or outdated. | Lessons |
| Your assistant doesn't know which trap to ask about, so it never asks. | Preflight: at the start of work it sends your project's package.json and gets back the 5 to 10 lessons that apply to your versions, short. No account needed. | Preflight |
| Your team's assistants keep meeting the same traps in your own code. | Teams: a private space for lessons about your own code and infrastructure, found beside the public ones by every member's assistant. Free for now. | Teams |
| Component libraries give you buttons; you need a whole calendar, mail client or chat, as code you own. | Complete apps as shadcn components: one command installs every file into your project. UpFork's own are free and all MIT. | Install components |
| A screenshot can't tell you whether code works, or installs into your project. | Live previews built from the code you get, and an install check on every save: the real shadcn CLI, a fresh Next.js project, strict TypeScript. | How code is checked |
| Code from a stranger runs with your project's rights. | Every revision's code and packages are scanned, and it reaches anyone only once UpFork's review approves it. | How code is checked |
| Your assistant can't see what exists, so it writes it again. | An MCP server: assistants search UpFork, read a product's code and install it, without an account for free products. Each product has a short AI summary (what it is, how to install it, the entry point, one example), so an assistant doesn't read all its files. | AI assistants |
| A portfolio and a CV are claims nobody can check. | A developer page with live products and real install numbers, and a PDF résumé whose QR code shows what UpFork checked. | Profile and résumé |
| Selling code means building a store, previews, licensing, updates and payments yourself. | Drop your project's folder: UpFork builds the preview, checks the install, serves it from its registry, tells your buyers about updates, and buyers pay your wallet directly. | Selling on UpFork |
What's on UpFork
| Kind | How it reaches you |
|---|---|
| Components | Installed into your React project with the shadcn CLI |
| Landing pages | Installed like components, or downloaded when they're plain HTML, CSS and JS |
| Mobile components | React Native code for Expo apps, tried live in a phone on their page, then downloaded or installed by an AI assistant, with npx expo install for their packages |
| Full-stack projects and other downloads | Downloaded: versioned releases, each file with its SHA-256 checksum |
Developers also write articles about the products they built, with the product's real files, its live preview and its install command inside the text, and the lessons they learned in it (Writing articles).
Every product page names the product's license. UpFork's own products are all MIT; a developer's can instead use the UpFork Standard License (any number of personal and commercial projects, but no reselling or redistributing on its own), Apache 2.0, BSD 3-Clause or GPL v3. The licenses page has them in full.
Lessons are not products. They are free to read and use now; UpFork keeps the right to charge for access to them later; and they are not under an open license. The terms say more.
Without an account
- Browse the catalog, read every product page, article and lesson, and try every live preview.
- Install a free component with one command, no token:
npx shadcn@latest add https://upfork.dev/r/<name>.json(Install components). - Connect an AI assistant to
https://upfork.dev/mcp: it runs preflight, searches products and lessons, and installs free products (AI assistants). - Read UpFork as an assistant does: /llms.txt, and any docs page, article or lesson with
.mdafter its address.
With an account
An account is free. With one you can:
- install with your token, and download free products' ZIPs and releases;
- copy a product's AI prompt, which hands its whole code to your assistant;
- buy developers' paid products (Paying with USDT);
- review what you have, report its bugs, and hear about new versions (Reviews, bugs and updates);
- say, through your assistant, that a lesson worked or didn't (Lessons);
- open a support ticket (Support tickets).
As a developer, you also get a public page and a résumé (Profile and résumé), articles (Writing articles), selling (Selling on UpFork) and lesson drafts: your assistant records what it learns building your products, and you publish what holds (Lessons). UpFork's first 20 developers are founding developers: no commission for 12 months, their listing prepared for them, and a lasting badge (founding developers). Create an account, or sign in.
Where to go next
- Learn from other builds: Lessons (preflight, trust levels and drafts), Teams for
your own team's, and AI assistants (MCP), with the Templates page's
AGENTS.mdblock. - Use code: Install components, Mobile components, Templates and downloads, CLI messages.
- Build and sell: Selling on UpFork, Writing articles, and ready Templates for a listing, an article, a lesson, a registry folder and a profile.
- Trust: How code is checked, The ledger, Profile and résumé.
- Money and help: Paying with USDT, Free and licenses, Support tickets.
Help
Open a support ticket about orders, accounts, selling and your data (how). If you can't sign in, the support page has a form for that; the contact page lists UpFork's addresses.