Release & Update Policy

BuildPod updates the service to improve security, reliability, performance, and functionality.

BuildPod may use standard production releases, beta or preview releases, staged rollouts, and future enterprise release windows. Beta or preview functionality may change more frequently than standard production functionality.

Standard updates may be deployed without customer pre-approval and may include bug fixes, performance work, reliability improvements, security updates, and UI improvements.

Material workflow changes may be communicated through release notes, admin notices, or support channels when practical. Customers should review material release notes and train users on workflow changes that affect their operations.

Customer owner/admin users may acknowledge update notices. Acknowledgment is not approval or decline. Standard SaaS updates cannot be declined by standard customers.

Security and data-integrity updates cannot be declined and may be deployed quickly or through expedited release paths. Older versions, outdated feature behavior, or deprecated workflows may be retired to protect reliability and maintainability.

Future enterprise release windows, version pinning, or staged upgrade commitments may be offered separately through written agreement.

BuildPod manages code rollback and data recovery under release safety processes. Customers should report issues promptly.