What governs your use of Railbase
The short version first — each answer links to the document that actually governs it. The full texts are below, with the version currently in force.
Limits at a glance
- What the licence lets you do
- Run the compiled Railbase core on infrastructure you control, for your own business, for as long as you like. The core is free; paid modules are licensed per company and per month.
- What it does not let you do
- Resell or sublicense Railbase, reverse-engineer it or decrypt a plugin bundle, run a paid module beyond the tier you bought, or work around licence enforcement and quotas.
- Support and updates — the ceiling
- The free core carries no obligation on us to provide updates, fixes or support. A retired module stays licensed for the term you paid, but stops receiving updates. Compatibility with future core versions is commercially reasonable effort, not a guarantee.
- Liability cap
- Our total liability is capped at the greater of what you paid us in the preceding twelve months or USD 100. Neither side is liable for indirect or consequential loss.
- Refunds
- Subscriptions are non-refundable; the free core and the free trial exist so you can evaluate before paying. Statutory and a few named exceptions apply.
- Your data versus ours
- Railbase is self-hosted: your business data stays in your Vault and never reaches us. What we do hold is your account, billing, licensing and company-verification data, as an independent controller — plus anything you send us in a support bundle.
- Sanctions and export control
- We screen the buying company against sanctions lists before a purchase completes. A confirmed match stops the sale, and funds are held rather than returned while it is reviewed.
The documents
Terms of ServiceThe account you hold with us: sign-up, payment, suspension, disputes.1.1End-User Licence (core)The Railbase binary you download and run on your own infrastructure.1.0Plugin Subscription AgreementEach paid module: what a subscription grants, and for how long.1.0Refund PolicyWhen money comes back — and the free path we offer instead.1.0Data Processing AgreementThe personal data we process for you, and the security behind it.1.0Master Services AgreementNegotiated and enterprise engagements that supersede the standard terms.1.0Privacy PolicyWhat we collect about you on this site and in your account.1.1Cookie PolicyThe cookies this site sets — and the analytics it deliberately does not.19 June 2026
Related
- Versioning and support — how versions are numbered, which ones get fixes, and what a module's minimum core version means.
- Security and trust — how we secure the parts we operate, and what we can answer in a security review.