Blog
Testing premium themes and licensed plugins before release
Your users run licensed themes and commercial plugins you cannot ship in a public repo. Here is how to test those combos safely before release.
Open-source test stacks rarely match what your paying users run. Premium themes and licensed plugins are where “we tested it” often means “we tested without them.”
Why public matrices are not enough
Default compatibility grids cover the most-installed plugins. They will not include:
- A client's custom licensed page builder bundle
- A niche WooCommerce extension with aggressive checkout hooks
- A theme your enterprise customer mandates
Those are the combos that generate urgent tickets after release.
Upload licensed zips to a private matrix
Team plans let you add custom combos — upload the licensed theme and plugin zips and include them in your private matrix. Each selected combination becomes an environment run within the scan. Your code runs in isolated test environments with zero egress and is destroyed after the scan.
Keep reports, not source
Folt stores the report — pass/fail matrix, stack traces, screenshots — not your proprietary zips after the run completes. Retention follows your plan (up to 90 days on Team).
Make it part of release QA
Before you tag a release for a client with a known stack:
- Add their licensed combo to the matrix
- Run the scan and diff against last release
- Attach the report to internal release notes
Review Team pricing, then use the compatibility report guide to plan how reviewers will evaluate the private-matrix results.