One of the most common licensing questions is not just can we use this commercially? but also what exactly are we allowed to distribute? Those are related questions, but they are not the same. In most cases, commercial usage is straightforward. Redistribution is where teams usually need to look more closely at how the product is being embedded, shipped, or exposed to others.
The simplest way to think about it is this: a license gives your organization permission to use BackgroundErase in a commercial workflow, but it does not automatically mean you can resell, repackage, sublicense, or redistribute the underlying model artifacts in any way you want. The exact answer depends on whether you are using a self-hosted deployment, an on-device package, or a more customized enterprise agreement.
Simple summary: licensed customers can generally use BackgroundErase in commercial products and internal business workflows, but redistribution of the underlying model architecture or weights is generally prohibited.
Commercial use is the normal use case
BackgroundErase licensing is designed for real commercial deployment. That includes internal company workflows, customer-facing applications, ecommerce pipelines, marketplaces, SaaS products, creator tools, and mobile apps. In other words, commercial usage is not some unusual edge case. It is one of the main reasons customers buy a license in the first place.
A licensed deployment typically allows your organization to use the model in revenue-generating products, internal business operations, and professional workflows, as long as the usage fits the structure of the license you purchased.
- Internal business workflows
- Customer-facing commercial products
- SaaS and marketplace integrations
- Ecommerce and listing pipelines
- Mobile and desktop applications
- Creative and media-production tools
Usage rights are not the same as redistribution rights
This is the key distinction: using the model inside your business is not the same thing as redistributing the model itself. A company may be fully allowed to operate BackgroundErase inside its own product or workflow while still not being allowed to resell the raw model files, expose the packaged runtime to third parties as a standalone asset, or sublicense it outside the scope of the agreement.
That distinction matters most when a team wants to embed the model in a commercial product, provide it to downstream customers, or structure its business in a way that looks more like platform distribution than simple internal use.
Important distinction: commercial usage generally means you are allowed to use the licensed technology in business. Redistribution means you are passing along the underlying model, runtime, or packaged technology itself in some form.
How this usually works for self-hosted licensing
With self-hosted licensing, your organization typically runs the model on infrastructure you control. That means the main right you are buying is the right to operate the model inside your own servers, cloud environment, workstation fleet, or internal deployment path.
In that structure, commercial use usually means using the model to support your own product or internal operations. What it usually does not mean by default is that you can hand the raw self-hosted package to another company, redistribute model files as a separate deliverable, or resell the runtime as if it were your own standalone software product unless the agreement specifically allows that.
Self-hosted is generally about internal deployment rights, not open-ended third-party redistribution rights.
How this usually works for on-device licensing
With on-device licensing, redistribution questions become more central because the whole point is often to ship the model inside a customer-facing application. In this case, the commercial value of the license often includes the right to embed the packaged model into your iOS or Android app and distribute that app to end users as part of your product.
That is a different kind of redistribution than handing over raw model files or sublicensing the package as a standalone developer asset. The intended model is usually: ship the product experience, not resell the core package as an independent licensing asset.
In practice, on-device licensing is often the path where a company is explicitly buying the right to distribute the app with the model embedded inside it, which is why the terms and pricing are usually different from the self-hosted path.
Outputs versus model artifacts
Another useful distinction is the difference between outputs and model artifacts. In most business conversations, customers care about the output images, the processed cutouts, or the user-facing app experience. Those are not the same thing as the model weights, runtime bundle, or packaged inference stack.
Commercial usage is usually centered on your right to use the technology to create business value through your product or workflow. Redistribution is usually centered on whether you are passing along the underlying technology itself, rather than simply using it to generate outputs.
Common examples that are usually fine
These are the kinds of commercial usage patterns that usually fit the spirit of a licensed deployment:
- Running the model on your own server to support your product
- Using a self-hosted deployment in an internal company workflow
- Embedding an on-device package into your own mobile app
- Charging users for a product feature powered by BackgroundErase
- Using the model in a client-serving workflow operated by your business
- Using outputs commercially in listings, catalogs, marketing, or software features
White-label and embedded products
Some of the most important redistribution questions come up in white-label and embedded-product use cases. For example, a SaaS company may want to integrate BackgroundErase into its own platform, or a mobile company may want to ship the model inside a customer-facing app. Those use cases are usually valid enterprise conversations, but they should be treated as part of the licensing structure rather than assumed automatically from a generic internal-use license.
That is why licensing conversations often depend on how the product is being delivered, not just where the model runs. Two companies can both be “using the model commercially” and still need very different license terms because one is using it internally while the other is embedding it into something distributed to the public.
Yearly, perpetual, and maintenance do not automatically change redistribution scope
Whether a license is yearly or perpetual does not by itself answer redistribution questions. Those choices mainly affect contract duration and commercial structure. Likewise, an optional maintenance package usually affects support, upgrades, and the ongoing enterprise relationship, not the fundamental scope of redistribution rights by itself.
In other words, pricing structure and redistribution scope are related, but they are not identical. The deployment model and the actual business use case are what usually drive the licensing discussion.
Best fit for a custom licensing conversation
You should usually reach out directly if your organization is asking questions like:
- Can we embed this into a commercial app we distribute publicly?
- Can we use this inside a product our customers pay for?
- Can we redistribute the model as part of a larger software package?
- Can multiple subsidiaries or business units share one licensed deployment?
- Can we package this into a platform or SDK for downstream clients?
These are exactly the kinds of questions that are better answered in an enterprise licensing conversation than by making assumptions from a general overview page.
Related licensing articles
This page works best alongside the broader licensing overview and the deployment-specific pages for self-hosted and on-device use.
The simplest version
BackgroundErase licensing is intended for commercial use, but redistribution of the underlying model, package, or runtime depends on the specific license structure. Using the technology inside your own business is usually different from reselling, sublicensing, or separately redistributing the model itself.
Contact sales
If your deployment involves embedding, redistribution, white-labeling, or third-party product delivery, the best next step is to visit backgrounderase.com/enterprise and describe exactly how you plan to use and distribute the technology.