FOR VIBE CODERS

You shipped the demo. Now what?

Claude Code, Cursor, Replit, Lovable, v0, Bolt: they get you to a working prototype faster than ever. Endenza links your GitHub and turns what you built into a walkable studio you can extend by asking Claude, then share as a place people step into.

Link your GitHub and each repo becomes a room you can walk into. Talk to your studio to change it: “add an arcade cabinet by the window that runs my demo,” and it appears. Publish one room as your Cadenza, the door people walk through on the Ensemble map. Bring your own AI tool; Endenza is where your work becomes a world.

Free to start, BYOK. $12/mo when you’re ready to ship — see what unlocks →

THE GAP

Your AI tool is a Ferrari. The road is a footpath.

Pick the one that sounds like your last week.

Context died, again.

You burned the context window getting Claude to understand your architecture, the chat compacted, and now you’re re-explaining things it knew an hour ago. Multiply by every session.

The prototype works. Nothing else does.

The app runs locally. Sign-in is a stub. Billing is a TODO. Database is SQLite in a tmpfile. Three different deploy attempts, none stuck. You’re back to building the boring parts the AI tool sped past.

One model, one voice, one angle.

You asked the AI “should I ship this?” and got a confident yes. Six hours later the production bug was the thing the question implied but didn’t ask. You wanted five voices; you got one.

Skills don’t carry.

You figured out a great workflow in Cursor. It’s in your head and three Notion docs. Next time you start a project, you re-derive it from scratch. The lesson didn’t install.

Your portfolio is a screenshot.

The demo lives on your machine. You can show people a video; you can’t hand them a URL that does the thing. Conversion: low. Polish: invisible.

The next session forgets you.

Every new chat is cold. The AI never “learns” you, your codebase’s shape, your style. You manage the memory by hand — pasting CLAUDE.md, re-explaining canon, re-establishing trust. Friction tax: hours per week.

WHAT ENDENZA ADDS

Six things your AI tool can’t do alone.

Endenza isn’t another AI coder. It takes what you already built and makes it a place: generated from your GitHub, changed by asking Claude, and walked by anyone you share the door with.

Generated from your GitHub.

Link a repo and each project becomes a walkable 16-bit room: a tiny browser game, a track, a long-form piece, all playable. Your studio raises itself in about 60 seconds. No install.

Extend it by asking Claude.

Talk to your room and it changes. “Add a synthwave arcade cabinet by the window that runs my demo,” and the thing springs into the studio, wired and placed. No editor tour, no config. You describe it; it appears.

Suite Library — install someone else’s whole setup.

Share your CLAUDE.md, Claude skills, themes, provider mix, sprite packs, and house rules as one Suite. Install another vibe coder’s whole rig with one click. The moat.

Walk it, then share the door.

Publish one room as your Cadenza and it opens on the Ensemble map. Visitors walk in as a sprite, click your work, leave knowing what you make. Hand someone a link, not a screenshot. Take a walk →

EndenzaOS — the operator layer, if you want it.

Run the agents underneath: Maestro, Council, Terminal, Dashboard, Atlas, drivable from any browser. It’s a separate product for people who want the cockpit; the studio never needs it. Meet the Council →

Substrate — auth, billing, BYOK, wired.

GitHub sign-in. Polar checkout (no per-transaction tax overhead for you). Multi-provider LLM routing. Tier-gating middleware. Hash-chained audit log. The boring parts your AI tool sped past: landed, tested, in prod. See the tiers →

YOUR AI TOOL STAYS YOURS

BYOK. Or bring your subscription.

Endenza doesn’t replace your AI tool — it gives it a place to live. Three ways to wire intelligence into the substrate:

Free daily · hosted. 3 Council sessions a day, no key required. For the “just trying it” visitor.
BYOK Anthropic. Plug in your sk-ant- key. Pay Anthropic per token; Endenza adds nothing on top. For when you want predictable costs and full control.
Local runner. Pair a Mac with your installed claude CLI. Council + Maestro relay through your Claude Code session — uses your Pro/Max subscription quota, no per-token billing. For Pro/Max subscribers who don’t want a separate Anthropic account.

Cursor, Replit, Lovable, v0, Bolt users: your tool keeps shipping the code. Endenza orchestrates around it. The next phase — native connectors to those tools — lands in v1.2.

THE LOOP

What signing in actually does.

Five steps. About a minute. Then you have a place to put the next thing you build.

01

Sign in with GitHub.

One click. No credit card. You get a starter Canvas in your Studio, a door on the Ensemble map, and access to the orchestrator.
02

Drop the project you’re working on into a Canvas.

Or start fresh. The Canvas is the unit — one project, one URL, one place your work accumulates.
03

Wire your AI tool.

BYOK Anthropic key, or pair your Mac for local runner. Now Council + Maestro answer your questions with intelligence you paid for, not a metered intermediary.
04

Ask the Council before you ship.

Five voices in parallel. ~30s. They’ll tell you what your prototype is missing — the kind of thing the demo glosses over but production catches.
05

Publish. Share the URL.

Anonymous visitors can walk your studio. Friends, prospects, X. Conversion path, lit. Then start the next Canvas.

Your tool ships code. Endenza ships the place.

The AI tools you already use stay in your hands. Endenza links your GitHub, turns what you built into a walkable studio you extend by asking Claude, and gives it a door people can walk through. It turns “works on my machine” into something you can charge for. Free to start. $12/mo when you’re ready.