Your agentic OS. Run anywhere. Share what works. Walk into what others built. The place AI-native makers ship from. An agentic OS that runs anywhere, a Walkable Showcase that ships your work as a place, and a Suite Library that shares your whole vibe-coding setup with the next maker.
Current product lock (R7 Train A, 2026-05-22): Endenza is four layers, one product. The Agentic OS is the headline identity; the other three flow from it.
| Layer | Surfaces | What it does |
|---|---|---|
| Agentic OS (headline identity) | Maestro · Council · Terminal · Dashboard · Atlas | Multi-chat orchestration + remote project management. Run your AI projects from anywhere. Full spec in AGENTIC_OS.md. |
| Walkable Showcase | Studio · Canvas · Cadenza · Ensemble | Publish as a place. Visitors walk in as sprites. |
| Suite Library (the moat) | /marketplace + /settings → Suites |
Share your full vibe-coding setup: CLAUDE.md, Claude skills, MD files, themes, agentic-OS layout, brand. Install someone else’s with one click. Full v2 schema in CREATOR_ECONOMY.md. |
| Substrate | CF Pages + Worker + D1 + Neon + Polar + BYOK | Auth, billing, storage, multi-provider LLM, telemetry. Invisible when working. |
We don’t compete with Cursor or Claude Code on building: the build loop is already solved. We compete with Vercel, Netlify, and Linktree on the production + distribution side of AI-native making. Nobody has built a great place to show what you built with AI: and nobody has wrapped that around a remote-orchestration cockpit you can drive from anywhere. That’s the gap.
The identity tagline + promise triplet are canon language across every public surface:
- Identity tagline: “Your agentic OS.”: the category claim.
- Promise triplet: “Run anywhere. Share what works. Walk into what others built.”: the three-beat capability cadence.
- Hero h1 (homepage): “Your studio runs itself.”: the agentic promise in plain English.
Every public surface, marketing claim, and downstream doc inherits this
language. See ART_DIRECTION.md §1 for the locked
tagline rules, and ../CANON_VOICE_ANCHORS.md
for the full voice canon (duality framing, verb triplet, spatial vocabulary,
music-arc sibling positions, three-tier voice register, words-to-avoid).
Terminology
Five words carry this product. Use them precisely.
| Term | Definition | Cardinality |
|---|---|---|
| Ensemble | The public neighborhood. A 2D top-down map of doors, each one a creator’s Cadenza. The place a visitor lands. | One |
| Studio | The editor app where creators author canvases. | 1 per creator |
| Canvas | A creator’s place inside their Studio. Anything they can imagine: wrapping games, websites, embeds, visual elements placed via toolbar or Claude. | 2 (free) / 10 (pro) per creator |
| Showcase | The ONE canvas a creator publishes as their Cadenza. Visitors walk through their door and enter the Showcase. | 1 per creator |
| Setup | A creator’s optional power-user configuration: connected providers, local runner, keybindings, plugin set, and workshop activations. | 1 per creator (forkable) |
“Room” is no longer used as the public place: it’s Canvas now. “Workshop” is reserved for optional power-user setup modules. Ensemble is the public neighborhood, not the product brand.
What Endenza is, in one paragraph
Endenza is a creator’s playground built around four things: Ensemble (the public neighborhood of creator doors), the Studio (an editor app), the Canvases inside it (the creator’s places: or, when published as a Cadenza, the Showcase), and a customizable sprite that walks through them. Powered by AI and built for makers who treat AI as a partner. Replace the link in your bio with a place on the map. Walk your sprite through your friend’s Showcase. Buy and sell sprites, themes, and worlds to other creators. A page is alone. Endenza is together. A place you walk through, a Studio you author in, a Showcase that lives in Ensemble.
Endenza is creator-built first, generative-assist second. Sign up, build a sprite, link your GitHub, and within 60 seconds Claude has built a starting Canvas from your actual work: a bookshelf of your Substack drafts, an arcade cabinet for your Steam release, a tape deck for your Bandcamp. Then you make it yours. Place an arcade cabinet on the floor; walk your sprite up to it; press X: your game launches. Stand a book on a shelf; walk over and press X to read the essay. Drop a podcast as a tape deck; press X to listen. Customize the canvas with pixel-art sprites, vector environments, sound, and Claude-generated components: total creative freedom inside a safe sandbox. The Endenza Studio is the linktree your work actually deserves, and the Showcase is the door visitors walk through.
Endenza is also the cockpit for the work itself. The Agentic OS - Maestro, Council, Terminal, Dashboard, Atlas: is a tier-1 surface roster, not back-office plumbing. From your phone in a coffee shop you can push a project from autopilot into warp, escalate Maestro to the five-voice Council, watch the Terminal stream all the chats at once, and check the Atlas graph for the decision you made last Thursday. The Walkable Showcase is what visitors see; the Agentic OS is what you drive. Both are the product.
The thesis
The bio-link category is a $1B+ market and it’s wide open for depth.
Linktree, Bento, Carrd, Beacons, Spotlight: every product in the category is a variation on the same shape: a list of links with a header image. The category is enormous and ripe for a deeper experience, but no incumbent has the appetite to be weird, opinionated, or character-led. They chase the TikTok-bio market and stay strictly within the box. That’s the gap.
Meanwhile a new generation of creators has emerged who use AI as a partner. They produce more, ship faster, and care more about expressing themselves in their tools than any prior generation. They aren’t served by the current crop of personal-brand surfaces. They want a place that:
- Looks like nobody else’s. Not because it’s a different color, but because it’s a different kind of thing: a Canvas you walk through, not a page you scroll.
- Holds their work, not just their links. Click to play. Click to read. Click to demo.
- Lives. Updates as they ship. Reflects who they are this week, not last year.
- Connects to others. Their friends are also making things. The internet should reflect that.
- Doesn’t require a designer. Claude is the partner; the maker articulates intent, the system delivers craft.
That platform doesn’t exist today. Endenza is it.
Who it’s for
The audience is solo creators and small businesses who use AI as a partner to ship work and want a place that represents them and their projects with the same care they put into the work itself.
Creators:
- The musician with five albums on Bandcamp + a Substack + a YouTube channel + a small Patreon: currently bouncing visitors between five platforms. Their Showcase puts the whole world in one canvas: walk to the vinyl, press X, the track plays; walk to the typewriter, press X, the latest essay opens; the merch table links to Bandcamp; the door at the back leads to the Patreon community.
- The indie game developer with three Steam releases + a devlog on itch.io + a Twitter/Bluesky presence. Their Showcase is their arcade: walk up to any cabinet, press X, the game launches inline.
- The newsletter writer with a year of essays + a podcast + book recommendations. The bookshelf is real; walk over and press X to read an essay; press X on the microphone to play the latest podcast episode.
- The product designer with a portfolio + side projects + a moodboard practice. The Showcase is the moodboard itself, with embedded Figma frames + interactable case study links the visitor walks up to.
- The illustrator with a portfolio + commissions + tutorials + Patreon. The Showcase is their gallery; the visitor walks the floor; each piece is hoverable, interactable, story-bearing.
Small businesses:
- The two-person creative agency that wants a portfolio that reflects their actual taste, not a SquareSpace template. Their Showcase is their pitch.
- The indie SaaS founder running their personal brand + the company brand. The Showcase is the home page that doesn’t suck.
- The local restaurant that wants more than a Beacons page: a canvas with the menu as a chalkboard sprite, the dish photos as plates, click-to-order links, an animated wood-fire oven, all walked-up-to and pressed-X-on.
- The micro-publisher with a small catalog. The Showcase is the bookshop the visitor walks into.
They share: many small projects (not one big one); real interest in self-expression as part of business; comfort with AI-as-tool but tired of “AI inside” being a feature, not an experience; care about how things look and feel; a network of peers also making things.
They are not: enterprise teams; beginners learning to code; casual ChatGPT users; influencers chasing TikTok virality (we’re not the right tool for that).
The wedge
We are deliberately, specifically, not a:
- Code editor (Replit, Cursor)
- Note app (Notion, Obsidian)
- Design tool (Figma)
- Social network (Twitter, Bluesky, Mastodon)
- Code host (GitHub, Glitch)
We are a personal creative space + living portfolio you walk through. Our specific competitors:
| Platform | Their thing | Where Endenza wins |
|---|---|---|
| Linktree | List of links | We’re a Canvas, not a list: and the visitor walks through it as a sprite. Press X on any component to play, read, watch. Customizable to a degree they don’t allow. |
| Bento | Curated cards on a single page | Static cards vs. our animated, interactive, soundscape-having world. Plus AI as the design partner, not just a sprinkle. |
| Carrd | One-page sites | Static one-pager vs. our living, AI-augmented experience. |
| Beacons / Stan | Creator landing pages with monetization | We don’t try to be a checkout flow. We’re the place visitors want to be in before they buy. Beacons is the cash register; we’re the storefront. |
| Spotlight | Influencer multi-link pages | Same critique: TikTok-bio shape with no creative ceiling. We have no ceiling. |
| Glitch / Replit | Code playgrounds | They’re for code. We’re for the surface around the code: the persona, the home, the gallery. Their projects can embed inside our canvas as walk-up-and-press-X components. |
| Behance / Dribbble | Visual portfolios | Static + uploaded. Our portfolios are interactive worlds you walk through, and live updating. |
| Are.na | Curatorial blocks | Beautiful but static. We can embed Are.na blocks in our canvases. They’re a citation, we’re the artifact. |
| Notion personal pages | Long-form personal sites | Document-shaped. Ours are scene-shaped. Different metaphor. |
The breakthrough
What makes Endenza different from “another customizable linktree”:
1. Click-to-launch interactive assets, walked-up-to
Every component can be wired to an interaction. Walk your sprite up to a vinyl record, press X → the track plays. Walk up to an arcade cabinet, press X → the game launches in a sandboxed embed. Walk up to a book, press X → the essay opens. Walk through a door → travel to another canvas. (Click still works everywhere; sprite-proximity is the new default.) Nobody else does this. The Canvas is not a static portfolio; it’s a runtime for your work that you walk through.
2. Composable connected canvases
Your canvas has doors. Doors lead to other canvases: within your own Studio and, over time, across Ensemble where you walk between Studios via the multi-tenant neighborhood. Browse the network of creator-canvases as a continuous space, not a list of bookmarks. Habbo Hotel’s social-geography superpower, applied to AI-augmented creators in 2026. Nobody else has this: and the moment Ensemble unfolds, the social loop is real.
3. Live presence
When someone’s walking your Showcase, they appear as a ghost-sprite drifting through the canvas: their custom avatar, semi-transparent. They can leave notes pinned to your components. You see them when you’re both there. The canvas becomes an attended space, not a static page. Figma multiplayer cursors applied to creator portfolios: viral-shaped. (Live presence is v1.5; v1.0 ships single-visitor sprite-walk.)
4. Generative living canvases
A mode where Claude composes the canvas itself. “Show what I worked on this week” → fresh scene from your commits, smoke logs, state changes. Daily canvases. Mood canvases. Canvases that recompose themselves while you sleep, with walk-paths preserved so you can still explore them. The space becomes a living organism you witness. Defining demo for launch.
5. Programmable creator-bots
Place a bot sprite component. Define its personality + give it the context of your work. Visitors walk up, press X, and chat. It speaks in your voice: Claude impersonating you as the curator of your portfolio. Your canvas gets an attendant. The AI-native move that actually distinguishes Endenza: Claude isn’t a sprinkle of features; Claude is the texture of how your canvas behaves.
6. Procedural empty-state fill (sprite-aware)
When a brand-new user signs up: after the character creator builds their sprite: their first Canvas is already populated. Endenza reads their signup answers + GitHub repos (if connected) and seeds a 4–8 component scene that feels personal, not generic, with walk-paths preserved so the sprite can explore from the entrance. The cold-start problem that kills creator platforms inverts: instead of asking the user to imagine what their space could become, Endenza shows them on signup, then invites them to walk through it and edit. Disposable by design: one click wipes it back to blank if they want a clean slate. Nobody else solves day-zero this way, and without it Ensemble would be a wall of empty canvases. See PRODUCT_SPEC.md §3.6.5.
7. Ensemble: a collective showcase you walk
Ensemble’s /index.html isn’t a manifesto-with-CTA: it’s “the work everyone created together.” A beautiful grid of published Showcases, each one a door visitors enter and walk through with their sprite. Tier limits keep the world high-signal. Procedural fill makes this work on day one: every signup contributes at least something recognizable, so Ensemble looks lived-in starting at user #1. Over time, the grid unfolds into a navigable walkable neighborhood per V1_5_WALKABLE_WORLD.md. The first impression is community, not pitch. See PRODUCT_SPEC.md §3.6.6.
These seven together describe a category of product that doesn’t exist yet. Each is meaningful alone. Together they’re a different kind of thing: a place a visitor walks through, in a sprite they made, looking at canvases the creator authored, with their friends ghosting around them.
(Embed-everywhere: the Canvas iframe-embeddable into Substack/Notion/Bluesky bios: remains as a sharing mode in PRODUCT_SPEC.md §3.10, but is no longer elevated to breakthrough status; canvas-as-primitive + Ensemble are the differentiators that took its slot.)
Setup as content: the rig you wear, share, and inherit
R7 Train A refinement (2026-05-22): The Suite Library is the moat and the Agentic OS is the headline. A Suite now carries a creator’s whole vibe-coding setup:
CLAUDE.md+ Claude skills + MD files + provider mix + Canvas layout + theme/appearance + agentic-OS layout + brand identity + house rules + autopilot defaults: so installing someone else’s Suite drops their full creative environment on your machine. The earlier “optional power-user infrastructure” framing has been retired; share-the-setup is a tier-1 capability. Full v2 schema + portable filesystem format inCREATOR_ECONOMY.md.
A creator’s Setup is their rig: which providers are wired, which runner is paired, which BYOK keys are stocked, and which workshops are activated. It is a piece of personal expression at the same tier as the Canvas.
Power is in the inheritance, not the configuration. A new user signs up and gets sensible defaults. Advanced setup, provider keys, runner pairing, and remote-control features are opt-in. Configuration screens are not the entry point.
Workshops are federated, not monorepo’d. Agent Builder, Tool Builder, and future builders are separate GitHub repos. A Setup includes a manifest listing which workshops are active + version-pinned. Activating a workshop from the profile UI clones the repo, registers its skills, wires its hooks. Deactivating reverses the steps. Each workshop ships independently; no merge-conflict risk; each can be sold or published on its own terms.
The Setup Marketplace (v1.5+) is where Setups are browsed, forked, and (eventually) sold. A creator publishes their Setup, complete with workshop list + screenshots of their dashboard + a description of what kinds of work it suits. Visitors hit Use this Setup and inherit it (with their own credentials substituted for BYOK fields). This is how the second product on the platform: the way you make canvases: becomes itself a creative artifact people can share.
The Agentic OS: the cockpit, not back-office plumbing
Status: R7 Train A (2026-05-22) reclassification. The five Agentic OS surfaces: Maestro · Council · Terminal · Dashboard · Atlas: are tier-1, headlined as part of the product identity. The earlier “agent-controller plumbing behind the Studio” framing is retired. Full spec:
AGENTIC_OS.md.
The Walkable Showcase (above) is what visitors see. The Agentic OS is what the maker drives. Both are first-class. A Studio without a cockpit is a template gallery; a cockpit without a showcase is just another chat app. Endenza is the place where both exist together.
The Agentic OS roster:
- Maestro: one decisive voice. Hosted free / BYOK / local-runner.
- Council: the five-voice deliberation surface for the call that matters.
- Terminal: multi-chat orchestration: N Claude conversations in one panel.
- Dashboard: every project on one view, drivable from any browser.
- Atlas: the long-term memory graph of
CLAUDE.mdfiles, skills, decisions, and notes.
Together these compose remote project management for AI projects: the “run your AI projects from anywhere” value prop the homepage hook carries. From a phone you can flip autopilot on a paused project, hit warp speed on a worker bundle, escalate a Maestro turn to the Council, or browse Atlas for the decision from last Thursday.
Marketing surface for v1: the homepage names ALL FIVE Agentic OS surfaces in the Promise card. The Walkable Showcase preview tile and the Agentic OS preview tile share top-of-fold real estate. Visitors see both the place they walk into AND the cockpit they drive from.
Brand positioning. The current canon hook is:
Your agentic OS. Run anywhere. Share what works. Walk into what others built.
The orchestra metaphor stays as the design vocabulary (Maestro icon,
music staff in the brand mark, the “Endenza” wordmark itself: a tempo
marking). The 1,400+ commits of Claude Code orchestration that shipped
this platform aren’t backstory; they’re the cockpit itself, available
to every user. See ART_DIRECTION.md §1 for the
locked tagline rules.
The aesthetic stays
Habbo Hotel × crypto-vibe-coding power user × Apple-quality bar. Pixel sprites + vector environments + bronze + CRT overlay. The taste anchors. See ART_DIRECTION.md.
Who’s watching this work
The first ten beta users (full personas in GTM_PLAN.md) shift slightly with the new positioning. Less “developer” weight; more “creator.” Roughly:
- Indie musician with multi-platform release strategy.
- Indie game developer with portfolio of releases.
- Newsletter writer with adjacent podcast + recommendations.
- Product designer building personal moodboard practice.
- Illustrator with commissions + tutorials + Patreon.
- Two-person creative agency (small business case).
- Indie SaaS founder running personal + company brand.
- Educator / course creator.
- Local creative business (restaurant, shop, studio).
- Multi-disciplinary creator (writes + makes + ships).
These ten span solo and small-business, span purely-creative and creative-with-commerce, span established and emerging. They are the proof set.
The bar
Apple-quality, no compromise:
- Every page designed.
- Every animation earned.
- Every empty state designed.
- Every error state designed.
- No template-feeling components.
- Performance is a feature.
- Onboarding is a moment.
Plus the platform bar:
- Sandbox is airtight. Click-to-launch can never compromise the parent. Allowlist + trust tiers + per-Studio policy.
- Moderation is real. Bad-actor playbooks defined before launch.
- Cost structure is modeled. Unit economics validated before pricing locks.
The promise
If the manifesto were one line:
A place on the internet that looks like you.
If three:
Replace your linktree. Build a world. Let visitors play your work.
If the wedge:
A page is alone. Endenza is together. A creator’s playground.
If a feeling:
You opened your Studio at 9 AM and your Showcase had recomposed itself overnight from yesterday’s work. The arcade cabinet you placed last week glows because someone’s playing your game right now: you can see their ghost-sprite standing near the cabinet. There’s a note pinned to the bookshelf: a stranger left a comment on your latest essay. You walk your sprite through the door at the back, into your friend’s canvas in Ensemble, leave a note on their newest component, and walk back. Your tape-deck plays softly in the corner; you walk over and press X to change the album. You close the laptop and go for a walk.
That is the moment we are building toward.
What this manifesto is not
See PRODUCT_SPEC.md, ARCHITECTURE.md, ART_DIRECTION.md, GTM_PLAN.md, and INTERACTIVE_ASSETS.md. This manifesto is the why. The other docs are the how.
If anything in those documents conflicts with this manifesto, the manifesto is wrong, the document is wrong, or both: the conflict must be resolved before work proceeds.
Current lock (R7 Train A, 2026-05-22): Endenza is four layers, one product. Agentic OS (Maestro · Council · Terminal · Dashboard · Atlas) is the headline identity: run your AI projects from anywhere. Walkable Showcase (Studio · Canvas · Cadenza · Ensemble) publishes as a place visitors walk into. Suite Library (the moat) shares your whole vibe-coding setup so other makers can install it. Substrate (Cloudflare + Neon + Polar + BYOK) is invisible when working. Hook: “Your agentic OS. Run anywhere. Share what works. Walk into what others built.”