A plan should describe an operating boundary
Pricing becomes difficult to trust when the marketing page, application interface and server enforcement each carry their own interpretation of a plan. A public page might promise one allowance while an API applies another. A downgrade might look harmless in the interface but trigger destructive behavior deeper in the system. For an Event operations product, those inconsistencies are more than commercial friction: they can interrupt work at the exact moment a team needs the system to be predictable.
Pricing V3 treats a plan as a set of explicit operating boundaries. Events and one-off locations remain unlimited on every plan. Managed Venues, internal Workspace seats and retained Templates have clear capacity limits. Commercial capabilities—such as External Ticketing, Full Event Performance and periodic reporting—are separate decisions rather than being inferred from an informal plan label.
One catalog, from Free to Enterprise
Free supports one managed Venue, three internal seats and three Templates. Core expands those limits to three Venues, five seats and ten Templates. Scale supports ten Venues, fifteen seats and fifty Templates. Commerce supports twenty-five Venues, fifty seats and unlimited Templates. Enterprise is unlimited by default, while its model leaves room for future contract-specific overrides without rewriting the plan itself.
The final public presentation follows the same catalog and lets organizers compare Monthly and Annual billing views directly. Free is €0 with an 8% NOCTRA Ticketing rate. Core is €49 monthly or €39 per month billed annually, with a 6% rate. Scale is €149 monthly or €119 per month billed annually, with a 4% rate. Commerce is €500 monthly or €400 per month billed annually, with a 2% rate. Enterprise remains custom. Annual figures are monthly equivalents—€468, €1,428 and €4,800 billed for the full year respectively—so the interface shows both the comparable monthly value and the actual commitment.
Capacity follows the work being created
The same capacity decision appears in the product and at the point where work is created. Venue creation and restore, Workspace invitation and membership activation, and Template creation all use the catalog's current allowance. The interface can show the limit and remaining space before a team acts, while the protected operation keeps simultaneous requests from silently exceeding it.
Seat counting follows the operating reality of a Workspace. Active memberships include the owner, and valid pending invitations reserve capacity. Suspended memberships do not count, but reactivation checks the quota again. External Door invitations remain outside the internal-seat count because they grant focused Event access rather than general Workspace membership. Venue capacity counts active, non-archived managed Venues; restoring one rechecks the limit. Template capacity counts retained, non-deleted Templates.
Downgrades preserve the record
A smaller plan never deletes or hides existing resources. If a Workspace moves below its current usage, the resources already present remain visible and editable. The system blocks only actions that would add capacity: creating or restoring another managed Venue, adding or reactivating an internal seat, or creating another Template while the Workspace is at or above its current allowance.
The same principle applies to commercial features. A plan change can prevent a new paid operation, but it must not erase customer data or make an unrelated edit impossible. Historical reports remain readable and necessary customer-data export paths stay available. The plan also cannot override a disabled product module or grant a member permission they do not otherwise hold.
A clearer progression for Event teams
Every plan retains the core operating loop: Event planning and actuals, Guestlist, Door and Live operations, managed Venues within the plan limit, native NOCTRA Ticketing and Compact Event Recap. Core is the first plan with External Ticketing and adds Full Event Performance. Scale adds periodic reports, report exports and Campaigns. Commerce expands operating capacity without inventing a separate product model. Intelligence remains commercially unavailable for now; capabilities that are not customer-live are not made available merely because they appear in the commercial catalog.
This progression lets a team start with a working product rather than a hollow trial, then upgrade when its operation becomes broader or more demanding. It also removes old descriptive mismatches that blurred what a plan could actually do. The catalog is explicit, versioned and enforceable, which gives future billing work a stable authority to provision against rather than asking billing to become the source of product truth.