vibesdiy.app is built with React, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics and PostHog.
Built with React and React Router, hosted on Cloudflare. Domain registered in 2025.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| – | 7 Nov 2026 | |
| – | 7 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| – | 7 Nov 2026 | |
| CDN & Hosting1 | ||
| – | 7 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 7 Nov 2026 | |
| Authentication & Identity1 | ||
| – | 7 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 7 Nov 2026 | |
| Security, WAF & Bot Protection1 | ||
| – | 7 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
naomi.ns.cloudflare.comrex.ns.cloudflare.com# The prompt entry, draft builds and the API do work per request (a guest # build is a platform-funded LLM run), so crawlers stay on the pages meant to # be read. /vibe/prompt is matched exactly: handles that start with "prompt" # stay crawlable. User-agent: * Disallow: /chat/prompt Disallow: /vibe/prompt$ Disallow: /vibe/prompt? Disallow: /draft/ Disallow: /api/
# Vibes DIY > Vibes DIY makes a working web app from a sentence and hosts it at a link to share. Apps keep their data, sign people in, take payments into the owner's own Stripe account and connect to GitHub. An AI agent can build one for the person it's helping, from a terminal or over MCP. The app belongs to the person: they sign in, and everything you make lands on their account. Where a step needs them (signing in, connecting Stripe or GitHub, trying the app), hand them the link and wait. ## Follow a guide Each guide is the same steps as its page on https://vibes.diy, written as terminal commands: the questions to ask, the build prompt, the connect step and the first real use. Read the whole guide before starting. - [A shop with Stripe checkout](https://vibes.diy/guided/jchris/shop-guide/agent.md): A product catalog, a bag and Stripe Checkout, paid into the person's own Stripe account. Vibes DIY takes no cut, and a test sale comes first. - [A pull request reviewer](https://vibes.diy/guided/jchris/pr-reviewer-guide/agent.md): The team's rules in plain words, and a comment on every pull request in a connected GitHub repo where one applies. - [A bug report page](https://vibes.diy/guided/jchris/bug-report-guide/agent.md): One link where anyone sends a bug or an idea, no GitHub account needed, and each one lands in the person's repo as a labelled issue. ## Build any app from a terminal Node.js 20 or newer; nothing else to install. ```bash npx vibes-diy login # the person approves this device in their browser npx vibes-diy generate "Make a sign-up sheet for our book club potluck" --json npx vibes-diy pull <handle>/<slug> --published --dir app # read or edit the code cd app && npx vibes-diy push --vibe <handle>/<slug> # deploy your edits ``` The last line of `generate --json` names `ownerHandle`, `appSlug` and `url`; the app is live at https://vibes.diy/vibe/<ownerHandle>/<appSlug> as the build finishes. Every command: [the CLI handbook](https://good.vibes.diy/docs/cli). No browser on this machine: `npx vibes-diy login --no-browser`, then hand the person the link it prints. ## Connect over MCP The hosted MCP server is `https://mcp.vibes.diy/mcp`, with an OAuth sign-in as the person. It lists their apps, makes new ones, pushes code and reads and writes app data: [Connect Claude or ChatGPT](https://good.vibes.diy/docs/claude-connector). ## More - [Works with Stripe](https://good.vibes.diy/docs/works-with/stripe): payments, memberships and checks, with no cut.
| – |
| 7 Nov 2026 |
| – |
| 7 Nov 2026 |