Commercial License
This document explains the usage boundaries of Dino-GSP in public distribution, product embedding, and commercial cooperation scenarios.
If you are mainly evaluating direct link embedding, PPT/courseware usage, and other free-use scenarios, see Free Use first.
This document focuses on scenarios that require further licensing review. For deeper integration scenarios such as programmatic control and branding customization, we generally use commercial licensing.
This document describes the current open policy and does not constitute a formal legal agreement. The final scope of authorization, pricing, term, traffic quota, and service commitments are subject to the commercial contract or written authorization signed by both parties.
1. Scenarios That Require a Commercial License
Any of the following scenarios will generally require a commercial license:
- Calling embedded capabilities through the SDK
- Programmatically controlling the embedded page through protocol calls, scripts, message passing, or any similar mechanism
- Dynamically loading shared content, switching slides, or remotely driving canvas behavior
- Batch generation of geometry content, batch rendering, or batch task processing
- Calling geometry capabilities in AI products, agent workflows, automated problem solving, or automated tutoring scenarios
- Requiring white-labeling, de-branding, custom branding, or UI customization
- Requiring enterprise support, service guarantees, traffic quota, or other commercial rights
2. Exception for Free Products
If your product itself is free and you want to use open capabilities or integrate through the SDK, contact us to apply for a Free Non-Commercial License. Applicability, available capabilities, and authorization conditions are subject to confirmation between both parties.
3. A Simple Rule of Thumb
If your usage is limited to branded content embedding, you should generally refer to Free Use.
If your system needs to control the canvas through code, access deeper integration capabilities, or obtain private access, branding customization, automation, or enterprise guarantees, the usage will generally require a commercial license.
4. Typical Examples
The following scenarios usually require a commercial license:
- A teaching system dynamically loads geometry canvases for different questions through the SDK
- A question bank platform controls slide switching, file import, or REPL commands through code
- An AI product automatically calls geometry capabilities to generate figures, verify steps, or produce explanations
- A commercial product wants to hide Dino-GSP branding or present the canvas under its own brand
- An enterprise customer needs private content access control, quota guarantees, and service support
If one of the above products is itself free to use, you can still contact us first so we can evaluate whether the relevant open capabilities may be covered by a Free Non-Commercial License.
5. Rights Typically Covered by a Commercial License
Depending on the cooperation plan, a commercial license may cover one or more of the following rights:
- SDK and programmatic control capabilities
- Protocol-level integration capabilities
- Private content access
- White-labeling or de-branding
- Brand and UI customization
- Traffic quota and invocation limits
- Enterprise support and commercial services
6. Contact
If you are unsure whether your scenario falls within free use, or if you want to integrate deeper capabilities, please contact us. We can provide licensing guidance based on your product form, invocation pattern, traffic scale, and service requirements.
Contact: business@dajiaoai.com