# Railbase Suites

> How one commercial suite stays modular at install, runtime and licensing boundaries.

_Updated: 2026-08-16_

## One plan is not one monolith

A Railbase Suite packages a business outcome into Basic, Pro and Max. The buyer
gets one subscription and one invoice. Railbase still installs every component as
its own signed, encrypted Marketplace bundle, mounts its own site UI and checks its
own entitlement at execution time.

That separation is deliberate. A plugin remains purchasable on its own, has its own
version and can be upgraded independently. A suite adds composition, pricing and
shared quota claims; it does not introduce a second runtime or a hidden direct
plugin-to-plugin API.

## What happens after checkout

1. railbase.app resolves the selected suite plan to an immutable list of component
   plugins, versions, tier claims and quota additions.
2. The subscription itemises those components so tax, revenue attribution, upgrades
   and refunds remain explainable.
3. The Marketplace grants each component to the selected company/workspace.
4. Railbase downloads and installs each bundle through the normal lifecycle path.
5. Components discover and amplify one another through declared event contracts.

If a company already owns a paid component independently, self-serve suite checkout
is refused before Stripe creates another recurring charge. The owner first chooses
which commercial source to keep and cancels or changes the overlapping subscription.
Entitlements still remain source-aware: removing or changing a suite must never
revoke access supplied by another active, non-overlapping subscription.

## The three suites

- **Financial Suite** connects ledger, payables, receivables, assets, tax, treasury,
  budgets and controlled migration.
- **GRC Suite** connects risk, compliance, audit and, when released, internal
  controls/SOX.
- **Education Suite** connects the education shell and mobile experience with
  school, library and LMS operations.

Plans containing an unreleased component are shown as Planned and cannot enter
self-serve checkout. Individual plugins remain visible in the Marketplace so a
customer can start narrower than a suite.

---

[Compare suites](../suites) or [browse individual plugins](../plugins).