Your AI built the app. Tofu puts it online in 10 minutes.

A sped-up demo of one session in a coding agent, one short request at a time, each typed by the owner of Frank’s Kitchen, a restaurant. Asked to take the restaurant app live with a database, the agent signs in to Tofu once the owner approves its code in the browser, uploads the app and confirms it as Next.js, then asks before creating the database. Tofu creates the database, writes its six connection settings as write-only values, builds the app and checks that its public address answers, and only then does the booking page appear. Asked where the bookings are stored, the agent counts the database’s tables, and a guest who books a table for four at 7:30 shows up as a new row in the reservations table in Tofu’s table editor. Asked to connect frankskitchen.com, the agent has the owner approve DNS access once at their DNS provider, granting Tofu access to that one zone, and the address changes to frankskitchen.com with HTTPS. Asked to let staff sign in with Google, the agent turns it on, adds the button’s one line and deploys again, and the owner signs in with Google to the back-of-house: tonight, 42 covers, the reservations with their tables (the guest’s booking marked new), the prep list and what is sold out. Asked to send the sign-up email from the owner’s domain, Tofu sets up send.frankskitchen.com; Frank, a new staff member, creates an account on the restaurant’s sign-in page, and his confirmation comes from that domain. Asked for analytics and how busy the booking page is, the agent adds one line and deploys; views count with no cookie, and the agent answers: six views today, five of them the booking page. The demo clock ends at 9:41, on one Tofu account.