Skip to content

Licensing & Usage

Last updated: 2026-05-12

LOPs is proprietary software for TouchDesigner. This page summarizes the current usage rules for LOPs tools, downloads, documentation, bundled assets, and related materials.

If the full LOPs Operators License, a direct agreement, or another written agreement says something different, that document controls.

  • Your outputs are yours. LOPs does not claim ownership of media, renders, recordings, control signals, interactive experiences, or other work you create with the tools.
  • Commercial use depends on the license tier or agreement you have.
  • You may inspect the code and modify LOPs for your own internal use inside your projects.
  • You may build original components, tools, extensions, or workflows around LOPs, as long as you are not redistributing LOPs itself or presenting your work as an official LOPs release.
  • Do not redistribute LOPs files, private downloads, premium files, or access credentials.
  • Third-party APIs, model providers, and external services used with LOPs have their own terms, policies, and costs.

LOPs access is organized around these paths:

A solo tier for the Stable Diffusion / StreamDiffusionTD / ComfyTD side of the toolset. One artist or developer can use the Starter toolset for commercial or non-commercial work. Studio or multi-seat use is not included at this tier.

For individual commercial use of the broader LOPs operator family in paid client work, installations, and other revenue-generating work.

This tier is primarily about closer access, earlier testing, and higher-priority support. Commercial rights follow the published tier terms or any direct agreement in place.

For individuals, small partnerships, or small studios that want license coverage for up to 4 people, faster support, and a one-time consultation call. This tier suits both solo creators who want the support and consultation lane and small teams that want ongoing access together.

If you need broader studio rights, more seats, or a custom arrangement, a direct agreement may be the better fit.

You can deliver finished outputs freely.

If you deliver a TouchDesigner project that includes the actual LOPs tools, your client needs their own valid LOPs license if they will:

  • edit the project using LOPs;
  • reuse the project as an ongoing tool;
  • extract or install LOPs separately;
  • continue development with the tools beyond the original engagement.

A client does not need a LOPs license just to receive rendered media, recordings, exports, or other finished outputs.

LOPs does not rely on hard file locking as the main commercial boundary.

If your paid access ends in good standing:

  • you keep the right to use the specific versions you lawfully obtained during the active paid term;
  • you do not keep access to new releases, new downloads, updates, hosted entitlements, or support unless you renew or make a separate agreement;
  • commercial rights continue to follow the tier or direct agreement under which you obtained those versions.

Inspecting, Learning, And Building Around LOPs

Section titled “Inspecting, Learning, And Building Around LOPs”

LOPs code is inspectable inside TouchDesigner, and learning from tools is part of how many people work.

You may use AI assistants while working with LOPs in otherwise permitted work.

What is not allowed is using LOPs files, documentation, bundled assets, or other licensed or non-public LOPs materials to recreate a substitute version of LOPs, redistribute a competing replacement, or avoid the need for the correct license. That includes using LLMs, machine-learning systems, scraping tools, indexing systems, or retrieval corpora to materially assist that kind of substitute or license evasion.

Unless you have explicit written permission, do not:

  • redistribute, repost, mirror, resell, sublicense, rent, lease, or publicly share LOPs files;
  • share private download links, premium files, or access credentials;
  • package LOPs into a template, asset pack, marketplace listing, starter project, or repository in a way that gives third parties access to the tools themselves;
  • use LOPs materials to create a substitute or competing version of LOPs for redistribution or license evasion;
  • remove or falsify copyright, attribution, or licensing notices;
  • use LOPs in violation of applicable law or the binding terms of third-party services used with it.

Third-Party Services And Operator-Specific Notes

Section titled “Third-Party Services And Operator-Specific Notes”

Many LOPs tools connect to third-party services such as model providers, API platforms, or other software components.

That means:

  • you are responsible for your own accounts, API keys, permissions, and usage costs;
  • your use of those services may be governed by separate third-party terms and privacy policies;
  • some LOPs operators may carry additional notices, restrictions, or third-party licensing requirements that apply specifically to that operator.

Where an operator-specific notice or override is published, it should be read alongside the main LOPs license.

If you need:

  • broader studio rights;
  • more seats;
  • a custom commercial arrangement;
  • a direct client or enterprise agreement;
  • clarification on whether your use case fits a specific tier;

get in touch before assuming.

Licensing, studio, or permissions questions:

licensing@dotsimulate.com