Railbase Cloud Service Schedule

Version: 1.1 Effective date: 22 September 2026

This Schedule supplements the Terms of Service, Railbase Subscription Agreement and Data Processing Agreement between the accepting business customer and Silkway Tech LLC. It applies only to a company for which Cloud hosting is expressly offered and accepted in the authenticated Account. Publication does not open general availability. Invitation-only or synthetic test installations are identified as such and do not represent a production SLA or a paid customer verification.

1. Service and activation

Railbase Cloud is Company-managed hosting of the same Railbase Product for a named company. railbase.app provides Account sign-in, company verification, subscription management and installation status. Each hosted company receives a separate encrypted Vault with its own encryption key and company-scoped business records, attachments and access controls. Multiple companies share one Railbase process and its installed module code, background-worker capacity and hosting infrastructure. Installation identity, company registry, access authority and operational records are held in a shared system store. A person may use one sign-in identity for several companies, with separate membership and business permissions in each. The service does not provide a dedicated process, physical server or unrestricted virtual machine. Modules remain protected components running inside Railbase.

Activation requires approved company verification (including enhanced verification when enabled), a valid applicable entitlement, accepted current Cloud terms and DPA, and available hosting capacity. An installation request is not a ready service. The Account distinguishes verification, payment, capacity, installation, checking, ready and failure states. We notify the requesting user when installation checks and the initial backup have completed. An unsuccessful request does not create a second company or authorize an additional subscription charge.

2. Price and included capacity

The offered standard Railbase price remains USD 99 per named company per month, plus applicable taxes, as confirmed at checkout. Cloud hosting under this Schedule does not create a second Product subscription for a company that already has the applicable entitlement. Other Products or expressly accepted additional services are not included by implication. Existing accepted prices, Orders, invoices and billing periods remain unchanged.

Included customer storage is 1 GB (1,000,000,000 bytes) per company, covering stored business-record content, attachments and retained customer file versions. Platform binaries, protected module bundles, platform indexes, operational logs and provider-managed backups are not customer storage. Temporary processing headroom does not increase the included allowance. The Account or workspace shows usage; operations that increase customer storage beyond the allowance may be refused, while access to existing data, deletion and available export functions remain accessible subject to security and entitlement restrictions. No automatic storage-overage charge is authorized. Additional capacity requires an explicit offer and acceptance.

Compute and network resources are shared and bounded to protect other customers. We do not promise a dedicated CPU, independent disk IOPS, fixed throughput, unlimited workloads or a particular Contabo tariff. Workloads needing additional capacity require a separate agreement.

3. Responsibilities and security

We operate the hosting infrastructure, deploy supported signed releases, restrict administrative access and operate backups. You remain responsible for lawful content, users, business permissions, workflows, external integrations, applicable notices and the authority for business decisions. Account billing roles do not by themselves confer access to company records. Service notifications contain an Account link and never a password or persistent access token.

We may perform necessary maintenance and security updates and will give advance notice of planned material interruption where practicable. No uptime percentage, service credit or guaranteed recovery time is included unless an Order expressly states one. Internal recovery objectives are engineering targets, not contractual guarantees. Provider-managed recovery copies may cover the shared system store and multiple company Vaults; customers do not receive other companies’ records or shared recovery keys. Company data return is performed within that company’s authorized scope. Recovery rechecks current company access and hosting authority before service resumes. The on-premise default of disabled automatic backups does not disable provider-managed Cloud recovery. Backups are a recovery measure, not an indefinite archive; you should retain exports needed for your own legal or business requirements.

4. Processing and location

You control ordinary business data stored in your Cloud installation ("Hosted Data"); we process it on your documented instructions under the DPA. Account, verification, payment, licensing and service-security records remain independent-controller processing described in the Privacy Policy. The DPA's Cloud annex specifies the additional scope. A worker's deployment region is not a promise that all control-plane data, support access, backups or third-party integrations remain in that region. A special residency requirement must be accepted in an Order before upload; the standard offer makes no exclusive physical-residency representation.

5. Cancellation, suspension and data return

Subscription renewal is cancelled through the Account under the Subscription Agreement. Cancelling an installation request before a worker is assigned stops that request without deleting the company registration. Once assigned, stopping and deleting an installation requires controlled cleanup; request it through support@railbase.app. Cancelling installation alone does not cancel an existing Product subscription.

For ordinary service termination, request an export or return of Hosted Data through support within 30 days of the end of service. We retain recoverable Hosted Data during that period and delete the active copy afterward, unless an earlier authenticated deletion request or a documented legal hold applies. Access may be restricted for unpaid entitlement, security, legal or sanctions reasons; where legally permitted, support facilitates data return without restoring paid execution rights. Retained backups expire within 90 days after active deletion. A restore must reapply deletion and revocation records before access resumes. Deletion of customer content does not delete billing or other controller records that must be retained separately.

If we cannot complete the accepted initial Cloud installation, we will notify you and offer cancellation of the affected hosting request and a refund of any payment specifically collected for an undelivered Cloud service period. This does not automatically refund a separately used on-premise subscription. Mandatory rights and more favorable expressly accepted Order terms remain unaffected.

6. Acceptance and precedence

The requesting authorized user explicitly accepts this Schedule and the DPA before Cloud provisioning. We preserve the accepted document versions and hashes with the company and installation request. Material changes follow the notice and acceptance requirements of the Terms; publication does not retroactively change an accepted Order. This Schedule controls Cloud-specific service and return terms; the DPA controls processing of personal data; other agreements continue to apply to their respective subject matter.