Real applications built on Run402, each one live on its own subdomain and each one deployable as your own copy from a single command. Every example has a schema, row policies, a serverless function, a front end, and a README that contains the whole thing.
The smallest complete app: one table, public reading, sign in to write
One task list that everybody shares. Anyone who opens the page can read it. Signing in is what lets you add a task, tick one off, or delete one. Five files, and the README reproduces every one of them.
Auth, image upload through a function, and blob storage
A public feed of short posts that anybody can read without an account. Sign up to write a post of up to 500 characters, attach one photo, like a post, and delete your own. The feed refreshes every five seconds, so two browsers stay in step.
Per-user data with row ownership, and a spaced repetition scheduler
Anyone can study the built-in starter sets. Sign in and you get your own decks, a deck editor, and a review schedule that remembers which cards you found hard. One HTML file, one function, two SQL files and one manifest: no build step, no framework.
Server-side logic a client cannot be trusted with, under real row policies
One person starts an exchange and shares a six-character code, everyone joins, and the organizer draws the names. Each person then sees exactly one name: the person they are buying for. Nobody sees anybody else's, the organizer included.
Multiplayer with a shared countdown, polled from the database
A live quiz. One person opens a room and gets a short code, everyone else joins from their own phone, and each question runs against a countdown. Answers land in Postgres as they happen and the final standings come from a single ordered query.
Functions alone, with no REST surface at all
Share a note behind an eight-character code. Lock it with a password, give it an expiry, or make it burn so the first reader is the only reader. The interesting part is what it does not have: no exposed table and no REST endpoint, just two functions.
A real framework, with posts read from Postgres at build time
A blog called Field Notes whose posts are rows in Postgres. Astro reads those rows during the deploy and writes the whole site to disk, so every page a reader loads is a static file. One path is not a file: the search box queries the database live.
A script that goes from nothing to a live URL with no human in the loop
Starts with no project, no database and an empty wallet, and ends with a URL you can open. It draws testnet money from the faucet, pays for a tier, provisions Postgres, applies a migration, deploys a site, then fetches the result to prove the URL is serving. Nobody types anything after the first line.
An endpoint that answers 402, takes payment, then serves the content
An API that answers HTTP 402 Payment Required with its own price list, and returns the goods once an x402 payment settles. Five cents a call, paid by the caller, with no account, no key and no sign-up anywhere in it.
From inside an example folder of kychee-com/run402-examples, one command provisions a project on the free Prototype tier, applies the schema, deploys the function and the site, and prints your live URL. Change subdomains.set in its run402.json first: the name in the file is the deployment above, and it is taken.
# from inside an example folder
npx run402 up --yes --verify