Publish to the catalog

Publishing puts your tool on the Vendo catalog. Any tenant browsing vendo.run sees the listing, runs through your wizard, and gets a managed deployment — billed in credits, isolated from every other tenant, upgraded when you ship new versions. You author one template manifest, submit it as a PR against vendo-templates, and Vendo handles the rest.

What you're publishing

Three things, in three places:

1. A catalog entry in apps_catalog (slug, name, type, marketing copy, pricing model). Created by a DB seed migration in the Vendo monorepo.
2. A template manifest in runvendo/vendo-templates (services, databases, secrets, integrations, wizard layout). The file the deploy worker reads to provision a tenant's instance.
3. A release row in tool_releases pointing at the manifest version. The pairing of catalog entry + active release is what makes a tool deployable.

The catalog entry is created once. Manifests and releases are versioned and replaceable.

The submission flow at a glance

1. Build and verify the tool locally (Run locally as OSS).
2. Author the template manifest (Manifest format).
3. Define the deploy wizard (Wizard layout).
4. Submit a PR against runvendo/vendo-templates (Submission).
5. Ship updates as new versions (Versioning & releases).
6. Manage tenant upgrades and rollouts (Rollout & upgrades).

Read these in order

Where it fits in the bigger picture

The manifest references the SDK and integration declarations you authored in Build a tool. Publishing is the bridge between "I wrote a tool" and "any tenant can deploy it." Operating the deployed tool — logs, debugging, upgrades, suspend/resume — lives in Operate.