For independent designers and developers shipping to Vincia.

Forge for Vincia.

Vincia is the durable no-code canvas. Designers contribute the visual layer (templates, themes, section libraries); developers contribute the functional layer (connectors, workflow steps, widgets, blueprints, solution packs).

Start in 5 minutesSee the full catalog
curl -fsSL https://get.vincia.io/install | bashvincia loginvincia create design-template my-newsletter --build-type websiteready in 12s — open my-newsletter/ in Claude Code

One install, one login, one scaffold — same CLI for designers and developers.

Pick your path

Designer, developer, or just here to browse what's shipped? Each card routes you to the kit and the scaffold command that fits.

DesignersShip reusable templates and brand packs — for marketplace (free or paid) or directly for your own clients. One template renders dozens of brand sites and portals.DevelopersShip connectors, workflow steps, widgets, blueprints, and solution packs — the functional layer every Vincia website and portal plugs into.MarketplaceBrowse everything designers and developers have already shipped. Studio users install with one click; design-template and solution-pack publishers earn on every install.

See how it feels

You describe what you want in your AI agent (Claude Desktop, Claude Code, Cursor, Codex). The agent reads the kit’s CLAUDE.md, runs the CLI on your behalf, and shows you the preview. You give feedback in chat; the preview updates. When you’re happy, the agent publishes. You never type a command yourself.

Claude Desktopcreator-newsletter
You

Build a creator-newsletter template — warm cream, weekly literary feel.

preview.vincia.io/creator-newsletter
Preview pending…
Step 1 of 4You describe what you want — in plain English, to your AI agent. No CLI to learn.

Set your own price — or take the default

$1/ recipient / month

Default for design templates and solution packs — the two surfaces that ship a complete end-to-end experience. Other contributions (plugins, widgets, blueprints, connectors, workflow nodes, themes, sections) aren’t paid standalone — they’re the parts that make packs cheaper to build, and they ride inside the packs that use them.

Vincia stays. The catalog grows around it.

Vincia isn’t a Webflow alternative, a Zapier alternative, or a Bubble alternative. It’s the durable platform that absorbs new tools as they appear. When a new payment processor matters, it becomes a connector. When a new AI capability lands, it becomes a workflow node. When a new UI pattern catches on, it becomes a widget. The tenant’s build stays where it lives — only the catalog around it grows.

That’s the contributor pitch too. Your connector or template joins a surface that businesses sit inside and try many things from. Their data stays portable, the runtime scales with them, and they don’t need to migrate to chase the next tool — the next tool shows up in the marketplace as a plugin. Every install adds to that durable shape; your work is part of the reason a Vincia build outlasts the trend cycle.

Free or monetize — both motions matter

When you ship to the Forge marketplace, you pick one of two modes. Both go through the same LLM gate plus human review; both appear in the same marketplace browse.

FreeShip it open. Every install grows your reputation and shows on your contributor profile. Free contributions get the same marketplace placement signals (install counts, freshness, archetype-fit) as paid ones — the only difference is the price.
MonetizeSet your own price on design templates and solution packs (default $1 / recipient / month) and earn on every install. Component contributions — plugins, widgets, blueprints, themes, sections — aren’t paid standalone, but shipping them publicly makes packs cheaper to build for everyone. Dashboard at /admin/contributor.

You can also skip the marketplace entirely and ship a template or plugin directly for one specific client — the same kit handles both motions. Promote it to public later if you want marketplace earnings on top.

How it works

Two paths, same outcome. Both produce a registered template or a published plugin that any Studio tenant can install.

Agent path (recommended)

  1. Download the kit from Studio (Designer Kit or Developer Kit) and unzip it. Each kit ships a CLAUDE.md and structured prompt files an LLM agent reads on its own.
  2. Open the kit folder in Claude Code (or any agentic LLM that reads CLAUDE.md — Claude Desktop with project files, Cursor, Codex). The agent reads the rules, schema, and exemplars, then asks you what to build.
  3. Describe what you want — “A creator-newsletter template, warm cream, weekly literary feel” or “A Stripe payment connector for the marketplace.” The agent handles login, scaffold, preview, and register; you make the brand and product calls.
  4. Publish — vincia publish (or, from the kit, node tools/register.mjs --register) submits to the marketplace; the LLM gate plus a human reviewer approve before users see it.

Manual path

  1. Install the CLI — curl -fsSL https://get.vincia.io/install | bash. See Quickstart.
  2. Scaffold — vincia create connector my-first (developer) or vincia create design-template my-first (designer) gives you a working starter wired to the SDK.
  3. Develop locally — vincia dev (developer) or vincia preview (designer) runs against a real sidecar with hot reload.
  4. Publish — vincia publish submits to the marketplace; same review path as above.