Skip to content
Melbora

What is Melbora?

Melbora is the platform an agency or freelancer uses to run many client websites without doing the wiring by hand every time.

One command — vantage websites create --name "Joe's Plumbing" --slug joes-plumbing — turns into all of this:

  1. A new GitHub repo created from a website-template (Next.js App Router on Vercel)
  2. A Vercel project, linked to the repo, deployed
  3. Environment variables seeded
  4. A CMS document the client can edit through their own portal login
  5. A node in your Blueprint canvas at /admin/websites/:id

From there you opt into more: a Shopify store with channel publishing to TikTok / Meta / Pinterest / Google, Cal.com bookings, AI-assisted SEO scanning + GEO probes, Resend email, OpenRouter for any LLM calls the site needs. Each integration is a node on the Blueprint, each is provisioned through the same orchestrator pipeline, each is teardownable when the client churns.

Who it’s for

Section titled “Who it’s for”
  • Agencies + freelancers building 5+ client sites where setup is the bottleneck
  • Operators who want a single dashboard for every client they manage
  • AI agents acting on behalf of a human — the same CLI/SDK works for both, and there’s first-class MCP support for Claude Code and Cursor

If you’re building one site for yourself, you don’t need Melbora. The value compounds with the second, fifth, twentieth website.

What’s special about it

Section titled “What’s special about it”

Programmable end-to-end. Anything the portal UI does, the CLI does too — same API, same auth. The portal is one client of the API; you and your agents are others.

Multi-channel commerce out of the box. A Shopify store + channel apps for TikTok / Meta / Pinterest / Google / Marketplace Connect get provisioned and status-detected automatically. Your Blueprint shows which channels are live for each store.

Visual + textual together. The Blueprint canvas at /admin/websites/:id is the operator UX. The CLI is the agent UX. They edit the same underlying graph.

The CMS is a document, not a schema. Each website has one JSON document the client edits through their own portal. The template reads it at request time. Adding new sections to the site is editing the document + the template — no migrations, no headless-CMS ceremony.

What it isn’t

Section titled “What it isn’t”
  • Not a website builder. You bring the template (today: website-template); Melbora runs the platform around it.
  • Not a Shopify alternative. Melbora uses Shopify as the commerce backend; we don’t reimplement checkout.
  • Not a hosting provider. Vercel hosts the sites; Melbora manages the Vercel projects.
Section titled “What to read next”
  • Quickstart — get from zero to a deployed site in under 10 minutes
  • How it fits together — the request flow, AWS infrastructure, where state lives
  • Concepts — the data model: Website, Service, Blueprint, Provisioning