Choose a Railbase Business Suite
Understand the Product-level Basic, Pro and Max model.
Updated
A Railbase Suite is a complete, supported business outcome deployed on the customer's private Railbase estate. It is the unit of purchase, licensing, implementation, renewal and support.
Current Business Suites
- Education Suite — academic delivery, learner services and institutional operations;
- Financial Suite — governed financial operations, control and management insight;
- GRC Suite — risk, compliance, assurance, evidence and remediation.
Each Product page describes buyer outcomes, workspaces, governed workflows, implementation and a live demonstration where available.
Basic, Pro and Max
Plans live at Suite level:
| Plan | Monthly price | Best fit |
|---|---|---|
| Basic | USD 1,000 | The first complete operating outcome and guided rollout |
| Pro | USD 1,500 | Broader workspaces, workflows and operating coverage |
| Max | USD 2,000 | The complete outcome, advanced control and widest scope |
Prices are per named company before applicable tax. The plan table on each Suite page is the current Product contract. Public-beta status does not create an arbitrary blanket discount.
One Product contract
The Account shows one owned Suite, one plan, one price, one renewal and one installation relationship. A plan change updates the Product atomically. Technical implementation detail does not become separate customer licences or prices.
Purchase path
Purchase is available only inside the customer Account after legal-company KYC approval. Public Suite pages explain the outcome and link to Get started; they never originate an anonymous charge.
Implementation and support
The recurring subscription covers the Product entitlement and plan. Migration, integration, implementation and premium support may be scoped and charged as separate services. This keeps recurring Product value distinct from one-time delivery work.
FAQ
Can plans be mixed inside one Suite?
No. One company owns one plan for the complete Suite. Basic, Pro and Max do not apply to individual implementation building blocks.
Can one company own several Suites?
Yes. Each Suite is an independent business outcome and subscription, while all of them can run on the same private Railbase operating layer.
Can we buy only an integration layer?
No. Required connectivity is delivered within the outcome and implementation that needs it; it is not a standalone commercial Product.