# Product and capability availability

> Distinguish implementation, release eligibility and your actual installation.

_Updated: 2026-09-07_

Availability has several layers. Code implemented in Railbase, a reproducible Product contract, a released offer and a working customer installation are different milestones.

| Capability | Current public boundary |
| --- | --- |
| Railbase company work | Company Product for documents, organisation and governed workflows; current offer in Account |
| Studio | Supported process adaptation and coordination authoring; permissions and Product extension points apply |
| Industry Suites | Exact release, capacity and deployment acceptance belong to each Product |
| AI | Core runtime exists; activation requires the exact Product, model, knowledge, provider and verification prerequisites |
| Federation | Supported distributed profiles require compatible releases and accepted readiness; no universal topology guarantee |
| Mobile | Working iOS/Android prototype; production Store release not announced |
| Hosted consumer Products | Not offered by this self-hosted B2B catalogue; a prototype or blueprint is not a hosted contract |

## Check before a rollout

Your implementation record should identify the Product and core versions, permitted roles, supported workflows, capacity, deployment profile and complete process acceptance. A release-ready lock alone does not prove that every target workflow or optional capability is accepted.

For AI, mobile or distributed work, ask for the specific capability's acceptance evidence. Do not infer support from a version number or a demonstration of a different Product.

[Contact support](/en/support) · [Current Products](/en#outcomes)