On a course or membership site, testing changes and updates on staging isn’t optional. TangibleXP gives you two full-power WordPress staging environments with every application plan, built specifically for sites where the platform is the product.
Two full-power environments, included.
Most hosts either charge $20 per month extra for each “premium” resource-matched staging if they offer them at all, or give you underpowered environments that can’t reliably run your LMS stack. We give you two, and both run at the same resource allocation as your live site.
That matters because course and membership sites aren’t simple. LearnDash, LifterLMS, MemberPress, every LMS and membership plugin is resource-intensive under realistic load. A staging environment that’s too slow to navigate and can’t be used for load testing is next to useless.
When you buy a TangibleXP application plan, you’re effectively getting three fully-resourced WordPress installations for the price of one: your live site, and two staging environments ready to run whatever you throw at them.
Two slots, two workflows running in parallel
Having two staging environments solves a real coordination problem. We suggest using one environment for your developers to build and test new features and the second for you to validate plugin updates, theme changes, or infrastructure changes independently or as a longer-lived sandbox to test a complex integration over days or weeks without it interfering with day-to-day maintenance testing on the first.
Isolated by design
Your staging environments run on physically separate servers from your live site. They share nothing.
This isn’t just an implementation detail, though, it’s a deliberate architectural choice. A staging environment that shares infrastructure with production creates a risk that heavy testing activity degrades your live site’s performance.
With TangibleXP staging, what happens on staging stays on staging. Your live site is unaffected, regardless of what you’re running or how hard you’re pushing the test environment.
No staging-to-live push
Most hosting platforms offer a one-click button to push your staging database to your live site. We intentionally don’t.
For a brochure site, overwriting the live database from staging is a reasonable workflow. For a course or membership site, it’s catastrophic. Your live database holds student progress, enrollment records, membership status, subscription history, and purchase data. A staging database holds none of that. One wrong click from a team member who doesn’t fully understand the implications, and that data is gone. We removed the button to remove the risk.
If you need to manually migrate specific data or run a wp db import, you can. But we decided not to put a one-click option in front of people that could silently destroy years of customer records on a busy platform.
What you get
- 2 staging environments per application, included in every plan
- Full resource allocation: same specs as your live site
- Physical server isolation: staging activity never affects live performance
- Snapshot-based creation: spin up from any backup, not just the latest
- PHP version selection: test on a different PHP version before upgrading live
- Separate phpMyAdmin access for each environment
- Independent SMTP/mail settings per environment, and automatic disabling of emails on new staging sites when you configure SMTP via our panel
FAQ
Can I push my staging site to live?
You can manually migrate files or run database imports via WP-CLI. What we’ve removed is the one-click staging-to-live database overwrite, because for membership and course sites, that operation carries serious risk of overwriting live user data. The manual path exists for those who know what they’re doing.
Do staging environments count against my resource limits?
Staging environments have their own resource allocation. They don’t share or borrow from your live site’s resources.
What’s the domain for a staging environment?
You choose a subdomain when you create the environment, which becomes yourname.tangiblelaunchpad.com. You can optionally include “staging” or “dev” in the name (this matters because some plugins use domain patterns to determine whether to enforce license key validation).
Can I create a staging environment from an older backup?
Yes. When creating an environment, you can select any available backup snapshot, not just the most recent one.
How many staging environments can I run at once?
Two, per application. If you need to spin up a third for a specific project, you can destroy an existing environment and recreate it and the process takes only a few minutes. We do have extra staging environments as an add-on option in our backlog, so let us know if you’re interested!
Is staging available on all plans?
Yes. Two staging environments with matching resource allocation are included with every TangibleXP application plan.