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
- After an authenticated B2B Account and the company's effective KYC are approved, run the compiled Railbase Core on infrastructure your organization controls. Core is free; paid Products and Suites are subscribed to in the Account per named company and per month. Optional provider-managed full KYB/KYC is off by default and becomes an additional approval condition only while enabled.
- What it does not let you do
- Resell or sublicense Railbase, reverse-engineer it or decrypt a Component bundle, separate a Component from its Product, exceed the Product Plan you bought, or work around entitlement enforcement and quotas.
- Support and updates — the ceiling
- The free Core carries no obligation on us to provide updates, fixes or support. A retired Product stays licensed for the paid term, but may stop 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
- Product subscriptions are generally non-refundable. Core is free after the Account and company-verification gates; a Product has a trial only where one is expressly offered. Statutory and the named policy exceptions apply.
- Your data versus ours
- Your ordinary business records stay in your self-hosted Vault. The railbase.app control plane receives limited Account/team, company-verification, billing/tax, Product/Component entitlement, deployment, version and heartbeat metadata. If enhanced KYB/KYC is enabled, company and representative evidence is submitted to Sumsub's hosted workflow while railbase.app retains decision evidence rather than document images.
- Sanctions and export control
- Core distribution and Product commerce require an approved B2B company. We screen at purchase, renewal, reactivation and Product Plan-change boundaries and fail closed when current data is unavailable; a later sanctions hit can suspend paid Product/Component execution. If optional full KYB/KYC is on, provider non-approval has the same fail-closed distribution and entitlement effect.
The documents
Terms of ServiceThe account you hold with us: sign-up, payment, suspension, disputes.2.2End-User Licence (core)The Railbase binary you download and run on your own infrastructure.1.7Product & Suite Subscription AgreementProducts and Suites: Product Plans, billing, included Components, installation, plan changes, cancellation, and one automatically applicable Schedule for every marketed Suite.2.3Refund PolicyWhen money comes back — and the free path we offer instead.1.8Data Processing AgreementThe personal data we process for you, and the security behind it.1.5Master Services AgreementNegotiated and enterprise engagements that supersede the standard terms.1.6Privacy PolicyWhat we collect about you on this site and in your account.2.1Cookie PolicyThe cookies this site sets — and the analytics it deliberately does not.1.3
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.