Addon Modules Backend

Related documentation: Backend Modules · Finance Module Backend · Ticketing Addon Backend

Purpose

This page groups the addon modules in the current Kisum module taxonomy.

Addon modules extend a company’s chosen base module.

Rule

Each company has:

• exactly one base module
• zero or more addon modules

Current addon modules:

• finance
• ai
• touring
• venue_marketplace
• ticketing — NOT a Kisum addon anymore: it’s a standalone platform (Backend-Nextkt) Kisum integrates with as a white-label partner (see below)

Current documentation state

Finance

• implemented and documented

AI

• module exists in taxonomy
• production addon/backend split is still evolving

Touring

• module exists in taxonomy
• some touring workflow currently lives in Market
• dedicated addon/backend split is still evolving

Venue Marketplace

• module exists in taxonomy
• dedicated backend contract is still deferred

Ticketing — standalone platform (not a Kisum addon)

• Backend-Nextkt became an independent ticketing platform (Go modular monolith; ~86 endpoints) with its own auth + tenancy — organizations, operator users + roles, ticket buyers, per-org API keys. It does not use Kisum Auth/Core and is not a Core module/addon row or an Auth permission seed. Canonical doc: Ticketing Addon Backend (Backend-Nextkt).
• Kisum is a client, two ways: (1) white-label partner — provisions an org + drives /admin headlessly via a per-org API key (“Mode A”); (2) read-only venue + artist data source (the only outbound Kisum touchpoints). Monetized via a per-ticket fee in its own checkout.
• Listed on this page only because it lives in the workspace and Kisum integrates with it — it is not part of the Kisum module taxonomy. This supersedes the older finance.ticketing.* sketch in Backend Core Addons §3.3.

Notes

Add-ons extend capability, but they do not change the company’s base persona.