Install Railbase
Get the authorised installer, start your private runtime and complete browser setup.
Updated
Railbase is the company Product for documents, governed workflows and organisation. Its customer runtime is source-closed and delivered through railbase.app.
Before installation
- Create your railbase.app Account and register the legal company.
- Complete the required verification and destination checks.
- Review the Railbase Product, current price and taxes, and accept the applicable agreements.
- Choose the exact release and architecture available to that account.
- Nominate the person responsible for installation, company access and recovery.
An unavailable release or pending company verification is a prerequisite to resolve. A public demo does not grant a customer download or production licence.
macOS
Download the available signed .pkg for your Mac from Account and complete the
normal macOS Installer process. It installs Railbase.app in Applications and
the managed update helper. Open Railbase.app and use the browser workspace it
launches; no source build or Terminal permission command is part of this path.
The app keeps its state under ~/Library/Application Support/Railbase. Follow
first-run prompts for private unlock material and browser setup. On an existing
installation, preserve the data and matching secrets when updating.
Linux server
Use the supported Account package or authenticated apt/dnf repository. The package installs a dedicated service, protected configuration and local state. Follow the step-by-step server deployment guide for the exact packaged paths, HTTPS, first-run setup and recovery checks.
Windows
Use the currently available installer from Account and follow its installation prompts. Confirm the signing status of that exact release and read the SmartScreen guidance. Availability and architecture are shown in Account; do not infer support from a CI file or source repository.
First browser setup
A fresh installation opens its first-run form. Create the first user with installation authority and supply the company details, or use the supported connection to adopt your verified Account company. Connect the Product entitlement, then invite people and grant the company roles they need.
Installation authority does not automatically grant work in every company. Use actual requester and reviewer identities to complete the first business process.
Private data and updates
Keep the Vault unlock material and installation master secret private and recoverable. Backups must include the complete configured state and file stores, not just a single database file. Customer builds reject the shared development fallback.
Use the authenticated update channel and compatible verified releases. Do not replace the runtime with a file taken from a demo or an unverified distribution channel. Additional industry Products can be installed only when available for the account and supported release.