One major problem Sandboxes solves for us is incorporating the billing system in preview environments. Every new PR we create gets a feature environment, and using test mode so far every PR shares the same environment, so we stub our billing system to have every customer created in a given PR share the same Stripe customer ID, which causes issues when we want to test changes to our billing system. We were super excited to replace this with a one-sandbox-per-PR system that would allow us to fully test our billing system end-to-end with every PR, but alas, we usually have more than 5 PRs in flight at a time. We’d love to create a new sandbox for every PR, then tear it down after it’s merged in, but it seems sandboxes can’t be created and destroyed via API, and we’d need a limit around 50 instead of 5 to account for all in-flight PRs.
This would be such a massive improvement to our engineering process, being able to incorporate sandboxes directly into our CI/CD process, but for now it’s blocked by the limit of 5 and the lack of API-driven management.