Skip to content
Install

A graft is an extension that adds features to an Orchard instance, so you can add what your team needs without forking Orchard and keeping the fork up to date. It can add pages, API endpoints, its own database tables, Model Context Protocol (MCP) tools, instance settings, and cards or tabs on existing pages. You find grafts in the Extension Marketplace. You install them with orchardctl graft add or with Helm values, and Orchard rolls out the change like an upgrade.

Kind Publisher Label in Orchard
Official Orchard Official
Community Another author, listed in the Extension Marketplace Community · by the author
Tap Anyone, from a catalog that you added Tap: the tap’s name

Your trust policy controls which kinds can load.

Orchard publishes these first-party grafts:

  • Greenhouse (greenhouse): Cloud machines with coding agents.
  • The Grove (forum): A forum for the people on an instance.
  • Announcements (announcements): Notices on project and app pages.
Part Runs as Location
Server module A NestJS module loaded into the Orchard server /apiv1/<graft-id>/...
UI An island: a bundle with its own copy of Svelte, mounted in pages Orchard renders /<graft-id>/... and the slots
Migrations SQL that Orchard runs in a transaction The graft’s own schema, ext_<graft_id>
MCP tools Tools registered in the MCP server Named <graft_id>_..., or claimed by name
Settings Sections in Instance admin > Configuration Stored as instance settings
Cluster chart An optional Helm chart for CRDs, namespaces, and RBAC Its own Helm release, orchard-graft-<id>
  • Doors: A graft reaches Orchard through versioned interfaces called doors. A stable door does not change shape. A change ships as a new version next to the old one. orchardctl refuses a graft that needs a door the instance does not have. For the list, refer to the graft API reference.
  • Islands: A graft’s UI carries its own Svelte and its own copy of Orchard’s components, and draws in an element that Orchard gives it. Colors and fonts come from the shared theme.
  • Claims: A graft’s names live under its ID, such as /apiv1/<id>, /<id>, and <id>. events. A graft can ask for a name outside its ID with a claim.
  • Data: Each graft has its own Postgres schema. When the database user can create roles, the graft also has a role that can read only the core columns it declared. Removing a graft keeps its data until you purge it.
  • Failure handling: Orchard skips a graft that fails to load, migrate, or boot, and shows it as failed in Instance admin > Grafts. Orchard itself still starts.