A license gives your team the right to deploy BackgroundErase, but for many customers the more important long-term question is what happens after deployment. How do you get updates? What kind of support do you receive? What happens when your infrastructure changes, your mobile app evolves, or your team needs help staying compatible over time?
That is where the optional maintenance package comes in. Yearly and perpetual licenses can include maintenance for teams that want enterprise support, update access, deployment guidance, and a clearer long-term relationship around keeping the licensed technology healthy in production.
Simple summary: maintenance is the add-on that usually covers enterprise support, update access, deployment help, and compatibility guidance for self-hosted or on-device customers that want more than a one-time handoff.
What the maintenance package is for
Maintenance exists for customers who view BackgroundErase as an ongoing part of a product or workflow rather than as a static artifact they will install once and never think about again. If your team is running the model in production, shipping it inside an app, or relying on it for a real business process, long-term support often matters just as much as the original licensing structure.
The maintenance package is designed to reduce that long-term uncertainty. Instead of only owning a runtime artifact, your team gets a clearer path for staying current, asking technical questions, and adapting the deployment as your environment changes.
Available for yearly and perpetual licenses
Maintenance can be paired with both yearly and perpetual licenses.
With a yearly license, maintenance is often part of keeping the relationship active and operationally smooth over the contract term. With a perpetual license, maintenance is usually the mechanism that gives the customer continued access to help, updates, and deployment guidance after the initial purchase is complete.
In both cases, the idea is the same: the license defines the right to use the technology, while maintenance defines the quality of the ongoing support relationship around that technology.
What maintenance usually includes
The exact scope can vary by agreement, but the maintenance package is usually where customers get access to the things that matter after go-live:
- Enterprise support: a clearer support path for deployment questions, rollout issues, and ongoing technical needs
- Update access: access to supported model revisions, packaging changes, or licensed updates covered by the agreement
- Compatibility guidance: help understanding how the licensed package fits evolving infrastructure, runtime environments, and product changes
- Deployment assistance: help with rollout adjustments, environment questions, and production-readiness concerns
- Operational continuity: a more dependable support path for business-critical usage
Why update access matters
For many teams, maintenance is most valuable because it keeps the licensed deployment from becoming stale. Infrastructure evolves, app requirements change, and product teams often want access to newer model revisions or packaging improvements over time. Without a support and update path, even a strong initial deployment can become harder to manage as the surrounding environment changes.
Maintenance helps create a cleaner long-term story. Instead of treating the model as a frozen one-time delivery, your team has a framework for how updates and supported revisions are handled going forward.
Practical value: maintenance gives customers a much better answer to “what happens next year?” than a bare license by itself.
Compatibility guarantees in practice
“Compatibility guarantees” usually do not mean an infinite promise that every possible future environment will work automatically forever. In practice, they usually mean that customers with maintenance have a clearer, supported path for handling compatibility questions as their deployment evolves.
For a self-hosted deployment, that might mean help with supported runtime expectations, packaging guidance, or advice when infrastructure changes. For an on-device deployment, that might mean help navigating packaging revisions, supported mobile deployment paths, or guidance when the app team needs to update around platform changes.
The key point is that maintenance gives customers a structured way to manage compatibility over time instead of being left alone to solve every change from scratch.
Self-hosted maintenance considerations
For self-hosted customers, maintenance is often most useful when the model is part of a serious internal or server-side workflow. These customers usually care about deployment questions, upgrade planning, infrastructure fit, and having a support path when their environment changes.
If your team is running the model on private servers, your own cloud, or internal hardware, maintenance can help reduce the friction of keeping that deployment healthy over time.
On-device maintenance considerations
For on-device customers, maintenance is often even more important because mobile apps are constantly changing. Teams care about package revisions, app release cadence, supported runtime behavior, and how the model continues to fit the product as the app evolves.
On-device deployments are often tied closely to the end-user experience, so long-term support and compatibility guidance can have a direct effect on product quality. That is why many mobile teams treat maintenance as part of the real cost of operating the feature responsibly.
When maintenance is usually worth it
The maintenance package is usually worth considering when BackgroundErase is doing real work inside a business-critical environment. That is especially true if:
- The deployment is part of a live product
- Your team expects to need updates over time
- You want enterprise support access
- You need help with rollout or compatibility questions
- The model is important enough that downtime or drift would hurt the business
- You want a longer-term relationship rather than a one-time software delivery
Good rule of thumb: if the licensed deployment matters enough that your team will want help six months from now, maintenance is probably the right add-on.
When a bare license may be enough
Some customers may prefer a simpler licensing structure without maintenance. That can make sense when the deployment is narrow, the team is comfortable operating independently, and the model is not expected to be part of a fast-changing or heavily supported production path.
In those cases, the customer is usually prioritizing lower ongoing cost and is comfortable taking on more long-term ownership of the deployment experience internally.
Maintenance is about relationship, not just paperwork
The most important thing to understand is that maintenance is not just a contract line item. It is the part of the licensing structure that turns a one-time delivery into a continuing enterprise relationship. It is what gives your team a clearer answer when you need help with an update, a compatibility question, a rollout issue, or a future change in deployment strategy.
For some customers, that relationship is optional. For others, it is exactly what makes licensing usable in the first place.
Related licensing articles
This page fits naturally alongside the general licensing overview, self-hosted licensing, on-device licensing, and custom agreement discussions.
The simplest version
The optional maintenance package usually covers enterprise support, update access, deployment help, and compatibility guidance for yearly or perpetual self-hosted and on-device licenses. It is generally the right choice for teams that want a long-term supported deployment rather than a one-time handoff.
Contact sales
If your team is deciding whether to add maintenance to a self-hosted or on-device license, visit backgrounderase.com/enterprise and tell us what kind of deployment you expect to support over time.