You can use WPResidence on as many client sites as you want if each site has its own Envato license. One client site equals one license, and WPResidence checks this with domain-based activation, so you can’t stretch a single code across many projects. This fits most freelance workflows. You just add “buy one WPResidence license” into your project steps and keep building.
Can I legally build multiple client sites if each buys their own license?
You can build unlimited client sites as long as each has its own license.
Envato’s Regular License treats every WPResidence-powered site as one end product, so one license always covers one website. As long as every client project has its own purchase and its own Envato license key, you stay within the rules. WPResidence ties that license to a single domain from version 4.11 onward, so the theme helps you respect this limit while you work.
In practice, you can run 3, 10, or 50 client projects. There’s no special developer pack, you just match licenses to domains. In WPResidence, you enter each client’s purchase code in the License activation panel on their site, and the theme checks that code isn’t already used on another live domain. If you try to reuse the same code on a second domain, you see an already used style notice and activation is blocked.
Each client site then runs fully independent: separate settings, separate updates, and separate payments setup. For a freelance business, the clean way is simple. Treat “buy one WPResidence license” as a standard project cost item and keep a list. The theme doesn’t limit how many different client domains you support. The only hard line is one valid license per active site.
- One Envato Regular License covers one WPResidence site on one main domain.
- WPResidence license codes must be registered per domain starting with version 4.11.
- Reusing the same purchase code on another active domain triggers an already used license warning.
- You can take on unlimited clients if each project has a separate valid license.
How does license registration and moving between staging and live domains work for projects?
You can move a license between domains, but never use it on two sites at once.
When you build with WPResidence, you handle domain-based activation in the theme’s License panel inside the WordPress dashboard. You first register the license on the domain you’re using, which might be a staging URL like staging.clientsite.com. The theme checks the Envato purchase code and locks that code to the current domain so updates and imports work correctly.
Once you’re ready to go live, you deregister the license from the staging domain inside the same panel, then activate it again on the final live domain like clientsite.com. At first this looks tedious. It isn’t, because it’s the same quick two-step pattern on every project. What isn’t allowed is leaving the code active on both staging and production at the same time and treating that as two permanent installs.
For short periods during launch, you may have files on both servers, but only one active license registration should stay connected to Envato. The theme will complain if you try to keep the same purchase code tied to more than one active domain. If you want a long-term test or training site in parallel with the live site, that second permanent site needs its own WPResidence license.
Can I buy the license for my client or should they purchase it themselves?
Either you or your client can buy the license, but one site still equals one license.
Envato lets you buy WPResidence, build a full site, and hand that site to a single client as the end product. In that case, the client is treated as the owner of that website’s usage rights, even if the license sits in your Envato account. The rule doesn’t change. That license is tied to only one site, not to your whole client list.
If you purchase on your own account, you keep download access, update files, and direct author support for that specific license. The client gets the working site, while you quietly manage updates by keeping the purchase code stored in WPResidence license settings. Many freelancers work this way when they also handle hosting or maintenance, since they already manage plugin renewals and other tech items.
But many agencies prefer to have each client buy WPResidence under the client’s own Envato login, then send you the license code or theme zip. In that setup, you enter their details in the License activation panel so the site is registered in their name. This keeps long-term support simple, because if in two years they change developers, they still have full access to updates and can extend support from their Envato account without involving you.
Both workflows are valid as long as no license is reused across another client’s domain. A good rule of thumb is to decide early who will own the license account, add that to your contract, and register the code directly in WPResidence as soon as development starts. If you forget and skip that step, you usually remember the first time an update fails.
Are there any license restrictions that block a white-label or “portal as a service” model?
White-label business models are allowed, but every separate client portal needs its own license.
The theme ships with a White Label panel that lets you rename WPResidence inside the WordPress admin, change the author label, and hide original branding from client admins. That means you can present the whole system as your own platform while still using the official theme underneath. From a business view, this works well for a portal in a box service where you sell branded real estate sites to clients.
Licensing rules stay strict, though. Each separately branded portal that stands as its own site must have its own Envato license. This is true even if you run a WordPress Multisite network where you control all subsites from one dashboard. If each subsite is a different client or brand, you should assign one license key to each so every portal has a valid WPResidence activation.
Envato doesn’t offer any unlimited developer or agency pack that covers endless client uses of the same theme. Even an Extended License still applies to one end product, not an open SaaS where hundreds of customers spin up their own portals under one code. For a portal as a service, plan your costs on a simple ratio. One client portal equals one Regular or Extended License, depending on whether end users pay just to access content.
| Use case | License rule | WPResidence impact |
|---|---|---|
| Single agency site | One Regular License | One domain with many agents allowed |
| Multiple client portals | One license per portal | Each site registers its own code |
| WordPress Multisite with many brands | License per branded subsite | Map license keys to each subsite |
| Portal as paid SaaS | One license per sold portal | White Label panel for rebranding |
| Sell access to content only | Extended License per end product | Same theme, stricter Envato terms |
In short, the white-label tools in WPResidence help your service look custom, while Envato’s rules keep licensing tied tightly to each real site you deploy. As long as you count licenses per running portal and avoid sharing one code across many paying customers, your portal as a service plan stays aligned with both the theme’s features and Envato policy.
Can I monetize client sites freely, including memberships, paid listings, and FSBO portals?
You can charge clients and their users for listings or memberships without extra theme licensing fees.
Envato’s Regular License already allows commercial use as long as visitors can see the site’s core content without paying a viewing fee. That means your client can use WPResidence to charge agents or owners for posting listings, for highlighting featured properties, or for ongoing membership bundles. The theme’s payment options like PayPal, Stripe, and bank transfer support exactly that kind of portal setup.
An Extended License only comes into play if end users have to pay just to see main content, for example if every listing is behind a paywall. Even in that case, the rule is still one license per paying site, not a higher fee per user or per property. WPResidence itself adds no extra licensing layer on top of Envato. Once a site is licensed, you’re free to turn on paid submission, memberships, or hybrid freemium models using the theme settings.
FAQ
Does one WPResidence license cover subdomains or language versions for a single brand?
One license can cover closely related uses that are clearly one website for one brand.
Envato’s idea of one end product focuses on the actual website, not small technical splits like a language subdomain. If you run en.example.com and fr.example.com as two faces of the same single brand site, that’s usually treated as one project. In WPResidence, you still register the license on the main domain in the License activation panel and manage language with your preferred plugin.
How does licensing work with WordPress Multisite when one company owns all subsites?
One company with many internal subsites should still count one license per distinct site that stands alone.
If a single company runs several regions or departments in one Multisite, you have some room when it’s clearly one combined platform. But when each subsite has its own logo, domain mapping, or market and acts like a separate portal, each needs its own registered WPResidence license. You activate the matching purchase code inside each subsite’s license screen so updates stay clean.
What about support period versus lifetime updates for client projects?
Support is time-limited, but theme updates for WPResidence are lifetime for that licensed site.
When a license is bought, it includes 6 months of author support, and that can extend to 12 months for an extra fee if needed. Even after support ends, the client site keeps getting theme updates as long as it stays properly activated with its purchase code. Many freelancers set expectations by offering their own care plans once the official support window passes.
How do freelancers handle support if the client owns the Envato account?
Freelancers usually ask clients for the purchase code or temporary access when support is needed.
If the client buys WPResidence directly, only their Envato account can open tickets or download files, but you can still manage everything. Common approaches are having the client share the purchase code, invite you to their account, or forward support replies. Honestly, it can feel messy if they vanish for months. Still, this keeps the license in the client’s name while letting you stay the person who deals with technical questions.
