Getting started

Vincia is an extensible no-code builder. People spin up two kinds of sites — website (public site; always includes a sign-in for the site owner; optionally adds customer accounts) and portal (sign-in-gated app, every page behind a login). That's it, no third option. The contributor surface is one CLI, one SDK, and one marketplace — every kind of contribution goes through the same flow.

Designers ship the visual layer: themes, design templates, section libraries, ready-made collections, plus seven specialty packs (icons, motion, chrome, backgrounds, email, microcopy, imagery). Developers ship the functional layer: blueprints (full apps or modules), connectors (payment / storage / notification / sign-in / mailbox), workflow steps, widgets, and solution packs.

Design templates and solution packs earn recurring income on every install — set your own price, or take the $1 / recipient / month default. Other contribution types (themes, section libraries, specialty packs, connectors, workflow steps, widgets, blueprints) aren't paid standalone — they're the parts that make templates and packs cheaper to build, and they ride inside the templates and packs that use them. Dashboard at /admin/contributor. Beyond the marketplace, you can also build for one specific client — same kit, same flow, contribution stays in your team's private library.

The shortest path: open the kit in your AI agent

1. Download the kit zip from Studio (Designer Kit or Developer Kit) and unzip it. 2. Open the folder in your AI agent — Claude Desktop (Settings → Projects → Add a project → pick the kit folder), Claude Code, Cursor, or Codex. 3. Tell it what you want to ship in plain English. The agent reads the kit's CLAUDE.md on its own and learns what to ask, what to scaffold, and what to publish.

From there the agent handles the rest: on first use it installs the Vincia CLI and signs you in, then it asks the right questions for the contribution type you picked, scaffolds the project, runs the preview, applies your feedback, and publishes when you're ready. You stay in chat — the agent runs the terminal commands for you.

> Note: Agents with shell access (Claude Code, Cursor, Codex) run the CLI directly. Claude Desktop with project files is read-only, so the agent guides you to copy-paste two install commands the first time. After that everything happens in chat.

Prefer the CLI directly?

Same flow, run manually. Useful if you don't want an agent in the loop, or if you're iterating on existing files in your own editor.

Prerequisites

Install

curl -fsSL https://get.vincia.io/install | bash    # macOS / Linux
# Windows (PowerShell):
# iwr -useb https://get.vincia.io/install.ps1 | iex

Verify:

vincia --version
vincia doctor

vincia doctor walks through your environment and reports the first thing missing.

Sign in

vincia login --token <vct_…>

Issue a contributor token from Studio (your /developers/tokens page) and paste it. Interactive browser sign-in is rolling out — until it ships, --token is the path. Your credentials are stored at ~/.vincia/credentials.

If you're using a self-hosted Vincia install, point the CLI at it once: vincia login --token <vct_…> --studio-url https://studio.your-host.com. Without --studio-url, the CLI talks to the default Vincia Studio.

Scaffold

Pick a type and a name. Connectors require a --capability flag; design templates accept an optional --build-type and --logo:

# Developer-side
vincia create blueprint my-app
vincia create connector my-payment --capability payment
vincia create workflow-node my-transform
vincia create widget my-kpi-card
vincia create solution-pack my-clinic-pack

# Designer-side
vincia create theme my-theme
vincia create design-template my-template --build-type website
vincia create section-library my-sections
vincia create ready-made-collection my-data-seed

Connector capabilities: payment, storage, notification, auth-provider, mailbox. The --logo <path-or-url> flag on a design template generates favicons, apple-touch, OG image, and monochrome variants for SVG sources.

You get a working directory with:

Develop

vincia dev          # developer-side — sandboxed sidecar with hot reload
vincia preview      # designer-side — multi-brand preview

Discover what already exists

vincia capabilities          # current capability list (payment, storage, …)
vincia interfaces            # SDK interface contracts for each capability
vincia examples              # worked examples bundled in the kit
vincia info <id>             # details on a specific marketplace contribution
vincia search <query>        # search the marketplace

Publish

vincia publish --dry-run

Runs the same checks the marketplace will run, locally, and prints the diff against the latest published version. Drop the --dry-run to submit.

Mix and match

Nothing stops you from scaffolding with the agent, hand-editing in your favorite editor, and running vincia publish from a terminal. Both paths produce the same contribution and go through the same LLM gate + human review.

Next steps