Prepare your first Suite implementation
Move from company verification to a production-ready Railbase Suite.
Updated
Railbase starts with a business outcome, not a command line. This checklist gets the buyer, implementation owner and IT owner aligned before deployment.
1. Choose the outcome
Open the relevant Suite page and decide which business boundary should move first. Confirm the target users, decisions, approvals and evidence that must be working at acceptance.
2. Choose Basic, Pro or Max
Use the plan table on the Suite page. Basic, Pro and Max belong to the entire Product contract. The plan is not a technical package selector.
3. Create the Account and company
Use Get started, register the legal company that will use the Product, and provide the requested KYC information. Purchase stays unavailable until the company is approved.
4. Buy in the Account
After approval, open Products in the customer Account, choose the named company and plan, accept the applicable agreements, and complete checkout. There is one Product subscription and one renewal date.
5. Plan implementation
Agree these items with Railbase or your implementation partner:
- private hosting destination and operating owner;
- users, responsibilities and separation-of-duties constraints;
- source systems and migration scope;
- required integrations and data residency restrictions;
- acceptance scenarios and production date;
- backup, recovery and update windows.
6. Install the Railbase Runtime
For macOS, the approved Account provides a signed and notarized installer. Linux and Windows production packages are provisioned during guided implementation with the correct service permissions and managed update channel. No customer workflow requires downloading a raw executable or manually changing file permissions.
7. Activate and accept
Railbase provisions the complete Suite, links the estate to its Product entitlement and runs the agreed acceptance scenarios. Production activation is complete when the named responsibilities can perform their real workflows and the operator has verified backup, recovery, audit and update procedures.