Forgeon Docs

Documentation, guides, and patterns to help you build on Forgeon — from your first deploy to running serious infrastructure.

Marketplace overview

The Forgeon Marketplace for templates and paid listings.

Last updated: 2026-03-17

Forgeon Marketplace lets creators publish templates and teams deploy them in minutes.

Two listing types

  • Free — open templates anyone can deploy
  • Paid — licensing required before deploy

What gets deployed

A listing can include:

  • A project (repo + runtime)
  • Optional bundles (e.g. database)
  • Required env schema
  1. Open listing and review runtime/framework requirements.
  2. Validate required env keys before clicking deploy.
  3. For paid listing, complete checkout and confirm entitlement.
  4. Deploy to staging first, then promote to production.
  5. Verify domain + metrics before team handoff.

How deploy works

flowchart LR
  A[Checkout] --> B[Payment]
  B --> C[Entitlement issued]
  C --> D[Deploy]

Troubleshooting

Deploy button says “Purchase required”

  • Complete checkout to get entitlement

Deploy blocked by missing env keys

  • Open listing required schema and fill all mandatory keys.

Deploy works but app fails at runtime

  • Check listing docs for expected port/start command and required services.

Publisher quality checklist

  • Listing README includes setup steps and health endpoint.
  • Environment schema marks required vs optional keys clearly.
  • Bundles are versioned and tested with current runtime profiles.
  • Pricing and entitlement rules are documented without ambiguity.

See also