Service and hosting policy

1. What the service includes

Each plan includes the initial build defined in your accepted scope, a baseline hosting profile, maintenance, and an allowance for ongoing improvements. Exact allowances, support response targets, and hosting resources are stated in your scope.

2. Requests and allowances

• Requests can be new features, content changes, bugs, maintenance, hosting changes, or integrations.
• Each request is estimated before work. Your allowance is only used after you approve the estimate.
• Chargeable overages require your explicit approval.
• Fixes for covered bugs do not reduce your feature allowance.

3. Maintenance versus new development

Maintenance covers keeping delivered software working: security updates, dependency upgrades, and fixes to delivered functionality. New features and significant changes are new development and use your feature allowance or are estimated separately.

4. Hosting

• Customer software is hosted separately from the Buildly website. Customer workloads never run inside it.
• Applications and data are isolated from other customers on shared infrastructure.
• Each plan references a hosting profile with defined compute, storage, bandwidth, backup, and region limits: Essential uses shared hosting, Growth a small VPS, and Business a medium VPS, each upgradeable. Included file storage is 5 GB on Essential, 25 GB on Growth, and 100 GB on Business; extra storage costs $5 a month per 50 GB. Scale hosting and storage are set in your agreement. The remaining limits and the list of supported regions are being finalised and will be published.
• Hosting upgrades are separate add-ons and never change your software plan.
• Moving to another region requires a migration procedure and your approval.
• Backups are encrypted and restoration is tested.

5. Integrations

A standard integration costs $20, one time, per approved integration, and covers the scope defined for that integration only. It excludes unlimited workflows, data mapping, and future changes. The third-party service and its usage charges are paid by you.

6. Access and credentials

We prefer OAuth or a secure secret-sharing method for access. Never send passwords in comments or messages. Stored integration credentials are encrypted.

7. Handover

Your data is yours at all times, and before the commitment is complete we export it on request in a convenient format suited to the data. Once your commitment is complete and required payments are made we deliver the agreed code and the database, build and deployment instructions, dependency manifest, schema and data export, configuration examples without secrets, architecture notes, and licence information. Credentials are transferred securely. Handover does not automatically cancel hosting or maintenance.