These come from our own test builds, 29 Sep – 5 Oct 2026. Each card shows the owner’s description word for word, what Chirai built from it, and the numbers from the build record. Every site was built by Chirai from that description.
What the owner asked“A website for delivery food from the local restaurants, and shops, and cloud kitchen, with proper user account for their ordering and history.”
What the owner asked“A website for buying and selling vintage cars, where sellers post listings with photos and buyers browse, save favourites, message sellers and make offers.”
What the owner asked“An online store selling hand-painted kalamkari sarees, dupattas and cushion covers from Andhra Pradesh — GST-inclusive prices, Razorpay and cash on delivery, coupons, order tracking.”
What the owner asked“A website for the public to track government-related complaints, file a complaint, and track their own complaint for any government body in India.”
What the owner asked“A website for job seekers to find jobs in the engineering field in Bangalore — only verified companies can post.”
What the owner asked“A community recipe site for home cooks. Members post recipes with photos, ingredients and steps, save favourites, comment and rate. Grouped by cuisine and diet (veg, vegan, Jain).”
What the owner asked“A website for booking business-class flights, comparing what airlines offer business travellers, with pick-up and drop from home to the destination hotel.”
What the owner asked“A website for selling handmade crockery in Bangalore, India — filter by bowls, mugs and plates, reviews, gift wrapping, the artisan’s story.”
What the owner asked“A job board only for engineering roles (software, aerospace, chemical, civil) in Bangalore — resumes, company profiles, job alerts, application tracking for employers.”
“Test build” sites were built to test Chirai and checked in the preview; they aren’t published. Minutes are from the description to a working preview.
We build real sites, use them like an owner and a customer would, and read every build log. When something is wrong we don’t patch that one site — we fix Chirai, so every site built after gets it right. A few of the things testing found:
Found: A form allowed a description shorter than the database accepted, so visitors saw a raw database error.
Now: Every site now reads its own database rules: forms enforce the same limits, and anything refused is explained in a plain sentence.
Found: Page titles sat under the navbar, and signed-in visitors still saw “Sign in”.
Now: The navbar takes its own space and shows “Account” when signed in; the site check measures overlap and contrast on the running site.
Found: The preview failed on a quote mark, and the database setup broke because the AI’s file stopped mid-line.
Now: A repair engine fixes such slips in milliseconds without AI, and unfinished database statements are completed or left out.
Found: Ticket numbers (GRV-2026-01000) needed a counter that didn’t exist yet when the table was created.
Now: Database counters are created before the tables that use them, on every site.
Found: Restaurants added in Manage site didn’t appear on the live page.
Now: Lists the AI writes into a page now come from the site’s database, so Manage site changes show on the live site.