Software Release Cycle

At Surfly, we are committed to developing and releasing new updates quickly to keep up with the ever-changing web landscape and maintain a secure platform. Our releases go through a user-acceptance cycle, which means that our Enterprise clients and Partners can test future releases in a special environment (https://uat.surfly.com/) that is two weeks ahead of our production environment.

This allows our clients and partners to preview upcoming features and provide feedback before the updates are rolled out to the wider user base. By implementing this cycle, we can ensure that our updates are stable and meet the needs of our users.

Pinning to an Older Version

We understand that testing upcoming versions may not always be feasible for all users, and unforeseen regressions could occur with new releases. To address this concern, we have implemented a safety net for such scenarios. After completing the user-acceptance cycle and releasing a new version to production, we also deploy the outgoing version to a dedicated set of legacy servers in each region, currently AMER & EU.

This safety measure allows users to switch back to the legacy version instantly if they encounter any issues with the newly released version. You can do this easily through the "selected_regions" option available at https://app.surfly.com/profile/options/session_functionality/.

It is crucial to keep the IP address(es) of the legacy servers whitelisted, if your network has restrictions in place for using Surfly. By maintaining these IP addresses on the whitelist, you ensure uninterrupted access to Surfly even if you need to revert to the previous version due to unforeseen issues with the latest release.

If you ever encounter a problem with the latest release, simply inform us about the issue, and we will begin working on a fix promptly while you stay on legacy version. Our priority is to ensure a seamless experience for our users, and your feedback plays a crucial role in helping us achieve that goal.