High-load terms
Hosting your project on a separate node: BOTBuild acquires the resources and the customer covers the cost.
The node is a worker, not the project’s data store
The separate node processes tasks as a worker. The project’s primary database is in BOTBuild’s central system, not on this node. Suspending the worker stops its operation, but does not by itself delete data from the primary database. These terms do not set a retention period for the project’s primary data.
When to discuss capacity
Planning audience growth, large broadcasts or many simultaneous orders? Contact the administrator in advance. If your project is already running, describe its current workload and any delays.
What to include in your request
- The number of bots and approximate number of active users.
- Expected concurrent users or orders and peak demand periods.
- Broadcast volume and frequency, and connected external services.
- Your planned launch or growth date; for a running project, examples of delays and errors.
Resource selection and acquisition
After reviewing the workload, BOTBuild independently selects the hosting provider, hosting location and separate node configuration within the agreed resources and cost. BOTBuild acquires the resources from the selected provider and arranges project hosting. BOTBuild decides where the resources are acquired.
The customer pays for hosting and renewal
The customer covers the cost of resources for the separate node and its subsequent renewals. The cost, billing period, renewal deadlines and payment procedure are agreed with the administrator before resources are acquired. Payment for resources does not transfer ownership of server hardware to the customer.
Advance payment and overdue renewal
Node renewal is prepaid: the full amount must be received by the agreed payment deadline, before the paid period expires. There is no grace period or renewal funded by BOTBuild. If payment is not received, BOTBuild may suspend the separate worker when the paid period ends, subject to mandatory requirements of applicable law. Any payment extension requires a separate agreement with the administrator.
Resuming operation
Operation can resume after payment is received and resource availability is confirmed. Immediate restoration, retention of the previous node and transfer to other capacity during non-payment are not guaranteed. Automatic processing of messages and requests missed during downtime is not guaranteed either. If resources must be acquired again or the cost changes, the new terms are agreed with the customer before acquisition.
Node access and management
BOTBuild manages the node infrastructure. The customer is not given access to the node itself, SSH/root access, server credentials or the hosting provider account. The customer continues to manage their project through the BOTBuild dashboard.
Changes to resources and terms
If the workload changes, contact the administrator for a new assessment. Changes to resource capacity and the associated cost are agreed before additional resources are acquired. BOTBuild makes infrastructure configuration changes.
No promise of unlimited capacity
Purchasing a plan or submitting a request does not guarantee support for any workload or additional resources by your preferred date. We confirm capacity increases after a technical review that takes the platform’s reliability into account.