Railbase Federation — controlled distributed operations
Supported Product placement, explicit authority and honest recovery boundaries.
Updated
Start with a standalone Railbase installation. Federation extends a supported deployment across approved nodes when the Product's deployment contract and infrastructure are ready.
What is distributed
Each node has its own storage, responsibilities and admitted connections. A Product deployment specifies where its supported work and user experience run. Authority, replica and projection are different responsibilities: a projection does not become a writable source of truth.
Company bindings make the permitted cross-node company relationship explicit. A local tenant identifier or an administrator's server access does not grant access to a remote company's records.
Plan and activate
- Define the business goal, participating companies, supported Product profile and required locations.
- Confirm compatible releases, licences, capacity, networking, signing and independently issued readiness evidence.
- Review the proposed topology and impact through the governed installation process.
- Admit the nodes and connections, then install the exact approved Product placement.
- Wait for every participating node's verified current state before treating deployment as active.
- Test loss of connectivity, recovery and the user's visible status before production use.
Federation is not a generic shared database, an automatic replica of every record or an unconditional high-availability promise. Supported profiles and recovery behaviour depend on the Product release and accepted infrastructure.
Operations and data location
Monitor drift, connectivity and replication lag. Failover, repair and removal require their supported authority and lifecycle paths. Removal revokes the named Product source while retention decisions preserve the required data and history.
Document the locations of primary data, replicas, backups, AI processing and support exports separately. A deployment location alone does not establish legal compliance or physical-residency certification.