Railbase-Module und Business Suites

Railbase is available On-premise and in Railbase Cloud by invitation.

Workflow Studio, approval workflows and industry capabilities are modules or capabilities of Railbase. They use its identity, company structure, authority, documents and operating services. They do not run as independent products.

Business Suites group related Railbase modules around an industry or business function. Each Suite has a Product contract covering its scope, capacity, price and release. Its capabilities run inside Railbase, with one Product subscription rather than a separate purchase for each component.

Current availability: Railbase is available On-premise and in Railbase Cloud by invitation. Industry modules are not included by default; consult signed-in Account for current offers and release readiness. Other industry Suites remain in preparation. Review deployment choices and the Cloud service terms.

Build your own routes or start with prepared ones

Workflow Studio is a Railbase module for configuring supported workflows and adapting permitted process settings.

Industry modules add prepared domain workflows, business rules, forms and specialist workspaces inside Railbase. They reduce the need to design every business process from scratch.

Business lines on a common foundation

Module group	Examples of work inside Railbase
Accounting	Invoices, journals, payments and close.
Budgeting	Budgets, revisions and transfers.
GRC	Risks, obligations, audit and remediation.
Education	Admissions, academic review and administration.
Farm	Purchases, operational processes and inventory decisions.

These are examples of module groups. Check each Product's current availability before planning a rollout; the GRC guide provides its scope and offer.

GRC scope and release conditions

The current GRC Product contract covers risk and value analysis, compliance, audit, internal controls and SOX, financial planning context, and governed source ingestion in one company workspace. Each role sees the records and actions it is authorized to use. Reviews, evidence and remediation remain traceable across the workflows; an action in one company never grants access to another company.

GRC has one company subscription for new purchases, with the complete capability set and the current grant of 500 audit engagements started per contract year. A monthly invoice does not reset that annual allowance. Retrying the same admission does not count twice, and reaching the limit does not stop work already admitted. Existing accepted grants remain unchanged.

Railbase Core, Accounting Suite and GRC Suite each cost the greater of USD 99 and 0.5% of monthly company revenue; Product prices add together. There is no new Basic/Pro/Max choice for these three Products. Individual components have no separate checkout. See pricing and billing examples.

AI assistance, including Smith, requires an approved model connection and context policy. Until the required configuration and evaluations are accepted, AI execution remains unavailable. A suggestion does not approve, sign or replace a human decision. The local Codex connection used for synthetic acceptance tests is not an approved connection for customer data. Country-regulated actions likewise require an applicable approved jurisdiction package; GRC does not promise universal legal compliance or a particular physical data location.

Signed-in Account shows the current offer and availability. Purchase is enabled only for an approved price and a published, signed, installable Product release. GRC is a separate Product subscription inside Railbase; it is not included automatically in every Railbase subscription. Start with the GRC learning path before configuring real company work.

Shared organization and authority

All modules work inside Railbase. They share the company context, people, positions, authority, workflow services and evidence. They do not create independent identities, databases or approval systems for each business domain.

Commercial scope

Railbase is available On-premise and in Cloud by invitation. GRC has its own Product offer and release conditions. Calling a capability a module does not mean that it is already released or included in every subscription.

The current Railbase offer and accepted agreements define the included modules, supported scope, limits and any additional charges. This guide does not change existing contracts or billing terms.

FAQ

Why add modules if we can build workflows ourselves?

Workflow Studio configures your own supported routes. Industry modules add prepared business rules, workflows and specialist workspaces, so you do not have to design everything from scratch.

Does each module have its own authority engine?

No. Railbase provides the shared organization, authority, workflows and evidence. Modules use those services inside Railbase.

Are all the module groups shown here available now?

No. Check signed-in Account for the current release and offer. Other industry Suites remain in preparation. Confirm the specific Product and its scope before planning implementation.

Railbase On-premise and Cloud · Module availability · Plan your first workflow