Equip an editing team, or explore integrating PatchRender’s processing technology into your own systems. Start with the work you need to do.
The right agreement depends on whether people will use the application or your infrastructure will use the underlying technology.
For studios, agencies, production teams and organizations revising finished video.
Commercial client work is also included in individual plans. Business licensing is for a coordinated team or a separately scoped deployment.
For businesses exploring PatchRender’s engine inside their own processing pipelines, services or internal tools.
A custom engagement, subject to technical validation. This is not a ready-to-deploy enterprise API or a promise of compatibility with every pipeline.
Every stage has a specific purpose. The aim is to understand your revision workload, test it and agree on a useful, supportable deployment.
Explain what changes after export, who makes those changes, the formats you use and how work moves through your systems.
Outcome: an agreed use case and success criteria.
Agree on a representative sample or pilot. Evaluate output, timing, playback and processing time on the workflow that matters to you.
Outcome: measured results, limits and a fit decision.
Specify annual license rights, users or processing scope, supported environments and support. Quote custom development separately.
Outcome: a clear commercial and technical scope.
Complete the agreed setup, validate the deployment and document the handoff. Review the scope as your workflow changes.
Outcome: an accepted deployment and agreed support path.
Your agreement defines the deliverables. Pilot terms, integration fees, service levels, security requirements and licensing rights are confirmed in writing. They are not included automatically with a desktop subscription.
Put together a short consultation brief. A few clear details make it easier to decide what needs testing and what an agreement should cover.
Your brief stays in your browser.
This form prepares a downloadable text file. It does not send a message, upload media or create a consultation booking. A verified contact route will be added before launch.
Team agreements are scoped around users, integrations, deployment and support. Technology agreements are scoped around the licensed use, environment, processing volume and service requirements. The annual license, any pilot and custom development are defined separately in the proposal. There is no published enterprise price or automatic company-wide license.
That is the purpose of the technology licensing path. We first need to establish whether the engine can support your actual pipeline and what integration work is required. Available interfaces, deployment rights and deliverables would be specified in the agreement.
No. Those capabilities and assurances are not offered by this website. Security, deployment, authentication and service requirements need individual review. Only explicitly agreed capabilities and commitments would form part of a contract.
Redistribution, resale, sublicensing, source access and exclusive rights require separate review and express written terms. They are not included with desktop licenses or a proposed internal-use integration.
Yes, both monthly and annual subscriptions include commercial client work for one named user. A business agreement is appropriate when you need multiple users, a coordinated deployment, a technology integration or separately negotiated terms.