48 States, One Cyberbeast goes live

48 States, One Cyberbeast is live. It is the first Vinyatan venture and the one that taught us most of what the studio now does: a campaign site, a payments system, and a live broadcast pipeline for an independent owner attempt at Tesla's 2026 Free Supercharging Competition.

It is an independent project. It is not affiliated with, sponsored by, or endorsed by the vehicle's manufacturer or the competition's organisers. We say that plainly on the site and we say it here.

What we built

The venture has three parts that had to work together from the first day.

• A campaign site. The public face of the attempt: the story, the schedule, the live view, and the ways to follow and support it.
• A supporter system. Payments, memberships, and recognition for the people backing the attempt, with receipts and a supporter wall that updates in real time.
• A live broadcast system. Everything needed to go live from a vehicle across a long trip, reliably, with one person operating it.

The site is Next.js, served from the edge for the parts that never change and rendered on demand for the parts that change every minute. Payments and memberships are Stripe. Supporter data, live state, and the realtime feed are Supabase, with row-level security so the public site reads only what it should.

The hard part was live

A marketing site with a checkout is a sprint. A broadcast that has to stay up while the thing it is broadcasting is moving is not. We needed a studio that could switch cameras, overlay live state from the campaign database, handle unreliable connectivity, and be operated by the person who was also driving the whole project.

Nothing off the shelf did all of that, so we built Cyberstudio. It gets its own post, but the short version is a native desktop application for X Live built in Electron, with native Swift where it mattered for capture and performance.

import { createClient } from "@/lib/supabase/server";export async function GET() {  const supabase = await createClient();  const { data } = await supabase    .from("live_state")    .select("status, title, viewers, updated_at")    .eq("id", "current")    .single();  return Response.json(data, { headers: { "cache-control": "no-store" } });}

What it taught the studio

This was the venture that made The Forge real. We stood up the environment, the agent roster, and the sprint cadence for it before we had a name for any of them. Three lessons carried straight into partner work.

1. Instrument first. The supporter wall, the live view, and the checkout all report to one dashboard. Every decision since has come from that dashboard, not from opinion.
2. Ship the boring parts early. Receipts, refunds, and account recovery were done before the first broadcast. Nobody remembers them when they work.
3. One operator is the constraint. Every feature was designed to be run by one person with one hand free. That discipline made everything simpler.

Follow along

The live view, the schedule, and the supporter options are on the campaign site. We will publish an engineering write-up on the broadcast system once the attempt is complete.