Commissioner
Pack discovery Ready

Browse the add-on packs that expand Commissioner beyond the base subscription

Packs group post types, modules, and extra features into coherent sellable add-ons. Each pack route stays explicit about minimum activation tier, shared-code gating, and planned versus shipped depth.

Browse-only while logged out Base subscription covers site setup, hosting, upkeep, and release train Add-ons gate down from shared implementations
7 Active pack contracts
1 path Shared-code rule
/pricing Commercial handoff
Pack-by-pack expansion
Pack-by-pack expansion Pack discovery routes widen the funnel without pretending unfinished depth is already shipped.
Tranche-owned

Base subscription is separate

Site setup, hosting, upkeep, and release operations remain covered by the single base subscription.

Add-ons stay tier-aware

Pack routes surface Basic, Plus, and Premium clarity while avoiding fake claims for lower tiers not yet setup-ready.

Parity stays enforceable

Pack selling must eventually reconcile to the same shared code later shipped to tenant snapshots.

Pack discovery

Every pack gets its own discovery setup

Dedicated pack routes keep breadth visible and make the base subscription versus add-on boundary explicit.

Ready Minimum activation tier: Plus

Commerce Subscription

Products, plans, checkout, billing, and subscription-aware commerce for sellable digital or physical offers.

  • Required post types 9
  • Required modules 14
  • Required capabilities 8
Plus Browse-only setup Shared-code add-on
Open pack detail

Commercial handoff: Route to pricing via /pricing

Ready Minimum activation tier: Basic

Content Publishing

Editorial, documentation, resources, changelog, and roadmap flows for content-led operators.

  • Required post types 9
  • Required modules 17
  • Required capabilities 5
Basic Browse-only setup Shared-code add-on
Open pack detail

Commercial handoff: Route to pricing via /pricing

Ready Minimum activation tier: Basic

Essential Intro Systems

Forms, legal, SEO, analytics consent, and fallback systems every launch needs before any vertical depth.

  • Required post types 1
  • Required modules 22
  • Required capabilities 17
Basic Browse-only setup Shared-code add-on
Open pack detail

Commercial handoff: Route to pricing via /pricing

Ready Minimum activation tier: Plus

Events Bookings Education

Events, sessions, bookings, tickets, classes, and education workflows across timed experiences.

  • Required post types 17
  • Required modules 18
  • Required capabilities 9
Plus Browse-only setup Shared-code add-on
Open pack detail

Commercial handoff: Route to pricing via /pricing

Ready Minimum activation tier: Premium

Property Directory Automotive

Listing-heavy experiences for property, directory, and automotive operators with rich search and detail flows.

  • Required post types 9
  • Required modules 16
  • Required capabilities 8
Premium Browse-only setup Shared-code add-on
Open pack detail

Commercial handoff: Route to pricing via /pricing

Ready Minimum activation tier: Plus

Services Business

Service catalogs, pricing, team, branches, and conversion systems for lead-driven businesses.

  • Required post types 8
  • Required modules 17
  • Required capabilities 8
Plus Browse-only setup Shared-code add-on
Open pack detail

Commercial handoff: Route to pricing via /pricing

Ready Minimum activation tier: Plus

Support Community Knowledge

Knowledge bases, support desks, communities, directories, and trust-building self-service surfaces.

  • Required post types 9
  • Required modules 13
  • Required capabilities 9
Plus Browse-only setup Shared-code add-on
Open pack detail

Commercial handoff: Route to pricing via /pricing

Route setup

What a public pack route must prove

Every pack route must point to real post-type, module, and capability authority and end in a deterministic CTA into pricing.

  • Authoritative catalog only No preview pack language without a named owner and state marker.
  • Tier clarity Client-facing Basic, Plus, and Premium semantics stay visible where sellable scope exists.
  • Browse-only behavior Logged-out discovery explains scope; only signed-in subscription surfaces can mutate commercial state.

Choose the pack before checkout

Public selling routes stay browse-safe until pricing, signup, and signed-in subscription flows take over.