Deploy, update and support Railbase
Make infrastructure, recovery and operational ownership explicit.
Updated
Railbase On-premise runs on infrastructure your organisation controls. You or your appointed operator own server access, networking, storage, patching, backups and recovery. Managed services or support response commitments exist only where expressly ordered.
The On-premise baseline is $99 per verified company (tenant) per month, plus applicable taxes. This is the software subscription; infrastructure, industry Suites and separately ordered services are additional. See pricing and full cost.
Railbase Cloud — Coming soon
Railbase Cloud will offer managed hosting by Railbase. Availability and pricing will be announced separately. Cloud hosting is not included in the On-premise subscription. Hosting Railbase yourself on a VPS or private cloud is still On-premise/customer-hosted deployment.
Deployment checklist
- Confirm the exact supported operating system and release through Account.
- Arrange HTTPS, outbound service requirements, storage capacity and recovery access.
- Separate installation permissions from company membership and business roles.
- Keep secrets and backup keys recoverable by authorised operators.
- Back up the Vault and every configured file/artifact storage location required for recovery; do not infer a complete restore from copying one database file.
Updates and migration
Use the authenticated update channel and compatible signed Product releases. Before an update, review dependencies, preserved process revisions, published Studio configuration and retained data. Test backup/restore and follow the supported migration and rollback path.
Existing customer pricing and accepted terms are historical evidence. A new public price or document does not silently rewrite an old invoice or establish that the customer accepted changed terms.
Offline and recovery
Self-hosting does not promise perpetual disconnected licensing. Read the offline licence guide and current agreement. On reconnection, reconcile current entitlements before resuming work. Federation replica and failover behaviour depends on the accepted profile; backups remain necessary.
Support and data
Support should start with versions, correlation references and a description of the failed step. Supply sanitised diagnostic material through the agreed channel. Installation-level diagnostics do not give support automatic access to tenant business content.
Response targets, recovery objectives, implementation scope, training and premium support must be explicit in your Order. No unpurchased SLA is implied by a feature page.