At Burst Statistics, we understand that building and maintaining a website is a process. Before you launch new features or designs on your live site, you likely test them thoroughly in a staging, testing, or development environment. Our goal is to make this process as seamless as possible for our Burst Pro users.
To support your development workflow, we’ve expanded our list of recognized subdomains for testing environments. This allows you to activate your Burst Pro license on your staging site to test all the premium features without it affecting your license limit for your live site.
A smoother workflow for developers
Managing licenses across different environments can be a hassle. This update is designed to remove that friction. By automatically identifying a wide range of development-related subdomains, Burst Pro enables you to:
- Test with confidence: Use all Pro features in a safe testing environment before deploying to your live audience.
- Preserve your license: Activating your license on a recognized staging site will not count against your site activation limit.
- Focus on what matters: Spend less time on license administration and more time building and analyzing your website.
Approved Staging & Development subdomains
When you activate your Burst Pro license, our system automatically checks if the website URL matches one of the patterns in our allowlist. We have now updated this list to include a comprehensive range of common naming conventions used for development and staging.
Your Burst Pro license can be activated on any site using the following subdomain prefixes and patterns:
staging.and*.staging.stg.*and*.stg.dev.*and*.dev.development.*test.*and*.test.local.and*.local.demo.and*.demo.qa.and*.qa.uat.preprod.and*.preprod.beta.*acceptatie.*(for our Dutch users.)
Note: The asterisk (*) acts as a wildcard, matching any string. For example, a URL like client-project.staging.yourdomain.com will be correctly identified as a staging site.
Is your pattern missing?
We know that development setups can be unique. We’ve tried to cover the most common patterns, but if you use a subdomain for testing that isn’t on this list, we want to hear about it. Our commitment to simplicity and transparency means we are always looking for ways to improve your experience.
Please reach out to our support team with your suggestion, and we will consider adding it to our list in a future update.