HYP.

HYP. is a monthly hybrid-fitness race run across partner gyms worldwide. Athletes compete locally at their nearest HYP. Arena, then rank globally on a shared leaderboard. James, the founder, had proven the idea with a prototype built on base44. It looked the part, but it was the wrong foundation to build a business on.

base44 is good for getting an idea moving quickly. The trade-off is that the code lives on base44's own platform, tied to infrastructure you don't control and can't grow past. James needed something he owned: a site he could pitch to investors and gym partners, a platform he could run real races on, and content he could change himself without a developer on call.

Getting a founder off a no-code prototype and onto a platform they own is exactly what our Vibe Code to Production service is built for. Platforms like Base44, Lovable, and Bolt typically generate a React or Next.js web app to prove the idea. Our job is to rebuild that as a properly architected production app on foundations the client owns: a Next.js web platform, or a React Native or Flutter mobile app, depending on what the product actually needs. For HYP., the right target was the web. The method is the same either way: a fixed-price discovery to map what carries forward, then a clean rebuild with a proper dashboard.

We rebuilt HYP. from the ground up as a Next.js site on Vercel, with Keystatic as the CMS. What James got back works as an operating platform, not a brochure: a filterable global leaderboard, race pages with the full movement breakdown, gym Arena profiles, booking links, gyms entering their own race results, and a gym-recruitment flow, all backed by content he edits himself.

Key Features

• Global leaderboard: A single ranked table across every Arena, searchable by athlete and filterable by sex, age group, gym, and city.
• Race pages: Each race has its own page with venue detail and the full seven-stage movement grid, including the sex-differentiated weights.
• Arena profiles: Every partner gym gets a profile with its location, schedule, and imagery, opened from the homepage in a quick detail view.
• Self-managed CMS: James adds races, gyms, and circuits himself through Keystatic, with no code change and no developer involved.
• Membership foundation: Athlete and gym accounts plus subscription plumbing are built into the platform, so HYP. runs as a membership business rather than a static site.
• Booking integration: Race entries flow through Eventrac, with each Arena carrying its own booking link.

Getting off base44

Like every Vibe Code to Production project, this one started with scoping, not code. A short, fixed-price discovery mapped what could carry forward from the prototype (the brand, the data model, the race concept James had already validated) and what needed building fresh. That is how we handle a no-code migration: keep what works, rebuild what doesn't, and don't pay for a rewrite you don't need. We know the source platforms (Base44, Lovable, FlutterFlow, Bolt, Bubble), so the assessment of what survives is grounded rather than a default "start from scratch".

The first job in the build itself was ownership. We lifted HYP. out of base44 and onto a codebase the client controls: Next.js 16 with the App Router, React 19, and TypeScript throughout. Nothing about the new build ties James to a third-party platform. The repository is his, it deploys to his own Vercel project, and it can grow in any direction the business needs.

A CMS the founder runs himself

The point of the rebuild was that James shouldn't need us to change a race time or add a gym. We used Keystatic, which runs against the local filesystem in development and against Keystatic Cloud in production, locked to the HYP. domain. It gives him three content types to manage: Races, Gyms (the Arenas), and Circuits (the race formats and their movements).

Underneath, every piece of content is validated against a Zod schema before it loads. We chose a typed JSON content layer with server-only loaders and a fail-soft design on purpose: if James ever publishes something that doesn't fit the schema, that one record is skipped and logged rather than taking the whole site down. He can publish confidently without a developer standing by, which is the entire reason the build exists.

The race platform

The leaderboard is what HYP. is built around. We built it as a single global table that an athlete can search by name and narrow by sex, age group, gym, and city, with the active filters reflected in the URL so a view can be shared or bookmarked. Each race has its own page carrying the venue (pulled from the linked Arena) and the seven-stage movement grid, from Ignition through to the Finisher, with separate weights for men and women. Partner gyms appear as Arena profiles that open in a detail view built on Radix UI, and entries route through Eventrac, with a built-in gym application form (validated with react-hook-form and Zod) feeding new Arena enquiries straight to James.

Built to be found

A platform pitched to gyms and athletes has to be discoverable, so we built the SEO in from the start. Every route carries its own metadata, the sitemap generates dynamically and includes each published race as it goes live, and a custom OpenGraph card renders for social shares. The whole site is statically generated and served from Vercel's edge, so it loads fast and reads cleanly for search engines.

Shipped continuously

Deployment runs through GitHub Actions into Vercel using a prebuilt pipeline: a push to the main branch builds and ships to production with no manual steps. Playwright end-to-end tests and Vitest unit tests guard the routes and core components, so a broken route gets caught before it ships.

HYP. now has what the prototype could never become: a platform James can put in front of investors and gym owners, and actually run races on. The first pilot, PILOT_07, has its Founding Arenas signing up for races from July 2026, including MRK5 Fitness in Stockport, Fierce Spirit CrossFit in Congleton, Movement. in Lincoln, The Hub MCR in Manchester, CrossFit Buxton, and a Leeds venue.

The founder runs it himself

The clearest measure of success is that James stopped sending us content to publish. He adds new Arenas and races through Keystatic directly, sets up the Eventrac booking links, and iterates the copy himself. As gyms have come on board, he's onboarded them without waiting on us.

"I've got gyms coming thick and fast now, and an excellent platform to support me." James, Founder, HYP.

Built to grow

Because the platform was built to run accounts and subscriptions rather than just display a leaderboard, HYP. has a clear path from pilot to membership business without a second rebuild. The hard architectural decisions are already made, the content model is proven, and the deployment pipeline is hands-off.

What's next

We continue to support the platform as HYP. grows from its founding cohort toward a national, then international, race series. If you've proven an idea in a no-code or vibe-coded prototype and need to turn it into a platform you own and can scale, that's what our Vibe Code to Production service does. It starts with a fixed-price discovery that tells you what carries forward before you commit to a build. Get in touch to talk it through.