Project License
Project License is an authorization scheme for specific business systems or single products. It strictly binds the usage rights of TechUI to a designated Project Name.
This license is very suitable for scenarios with limited budgets where usage is required only in a single system, or when purchased by Independent Software Vendors (ISVs) along with the delivery of a specific project to a client (Party A).
Core Benefits
Holding a Project License grants you the following benefits:
- Perpetual Usage: One-time buyout, valid forever. No annual renewal is required to continue using it in the authorized system.
- High Cost-Effectiveness: Compared to the Company License, the price of the Project License is usually more affordable, making it the lowest-cost legalization solution for single applications.
- Compliant Delivery: For ISVs, this is the most economical way to comply when handing over source code to clients (one project, one license).
Applicable Scenarios
- Outsourcing Delivery: A specific system developed and delivered by a software outsourcer for a client (the client holds the authorization after delivery).
- Single Application: An independent internal tool platform or a single business system deployed independently within an enterprise.
- MVP Verification: Innovative projects in early stages where it is not yet determined whether they will be promoted company-wide.
Pricing Description
The Project License adopts a differential pricing method based on scale.
Please Note: The prices displayed in the [Start - Pricing] chapter are only the "starting prices" applicable to small and medium-sized enterprises.
To ensure fairness and sustainable service capabilities, TechUI adopts a differential pricing strategy based on the scale of the licensed enterprise. For large enterprises, due to their massive internal system clusters, higher concurrent usage, and complex compliance support requirements, the licensing fee will be higher than the standard price.
Scale Grading & Fees
- Standard Enterprise (Standard Price)
- Target Audience: Small and Medium-sized Enterprises (SMEs), startups, sole proprietorships, etc.
- Fee Standard: Applies to the standard starting price published on the official website.
- Large Enterprise (Enterprise Price)
- Target Audience: Large enterprises, group companies, joint-stock companies, Central/State-Owned Enterprises (SOEs), listed companies.
- Fee Standard: Calculated based on the enterprise scale coefficient (usually 2x the standard price); please contact sales for a custom quote.
- Reason: Such enterprises usually possess larger internal system clusters (TechUI might be used in dozens or even hundreds of internal sub-systems) and have more complex requirements for legal compliance, financial processes, and technical support.
Strict Restrictions
To allow for a lower price threshold, the Project License has the strictest restrictions in the TechUI system during runtime.
⚠️ Title Integrity Check
This is the core technical constraint of the Project License. The Wasm guard monitors in real-time whether the browser's tab title (document.title) is consistent with the authorized project name.
- Tampering Prohibited:
- It is strictly prohibited to use any code in the project that modifies the browser title
document.title. - Guards or plugins in routing libraries (such as Vue Router / React Router) used to dynamically change page titles must be disabled.
- It is strictly prohibited to use any code in the project that modifies the browser title
- Response Mechanism - Denial of Service:
- Unlike automatic rollback, once Wasm detects that the title has been modified (does not equal the authorized project name), it will judge this as a violation.
- The system will immediately trigger Denial of Service (DoS): stopping all component rendering, clearing DOM nodes, or popping up a blocking warning until the page is refreshed.
- Purpose: To ensure the system is not "reskinned" for other uses, and also serves as a brand publicity cost for the low-cost authorization.
Warning: Please be sure to remove all logic related to
document.title = ...during the development phase.
Single Use
- Non-reusable: Authorization is only valid for a specific project name. You cannot split this license for use in other projects within the company, even if they belong to the same company.
Runtime Feedback
In addition to title verification, the console will also display the corresponding authorization information.
Console Badge
Displayed in the Console panel of Developer Tools (DevTools):
TechUI Prime v0.1
Licensed to [Your Company Name] Limited to [Your Project Name]
Permanently Valid | Project License | Contact InfoProject Naming Constraints
To ensure clear boundaries for "single project authorization" and prevent license abuse (e.g., reusing an authorization named "Certain Company Backend" for all internal systems of that company), TechUI has strict semantic requirements for the bound Project Title.
The binding name you submit must be the final delivery name that is concrete, specific, and points to a single business scenario.
Prohibited Generalized (Abstract) Naming
The account manager background audit mechanism will reject binding the following categories of broad names:
Generalized Function Combination: Strictly prohibits combinations using only "Company Name/Place Name + General Function".
❌ Error Examples:
Certain Company Admin System,Certain Group Data Screen,Certain Enterprise ERP,Certain Company Dashboard.Reason: An enterprise usually possesses dozens of management systems or large screens; such names cannot anchor a single project and carry reuse risks.
Broad Industry/Region Name: Strictly prohibits combinations using only "Company Name + Industry/Region".
❌ Error Examples:
Certain Company Financial System,Certain Company Beijing Project,Certain Company Medical Platform.
✅ Compliant Naming Standard
Compliant names usually need to be unique and must adopt a three-part subdivision structure of [Company/Entity] + [Specific Business Domain] + [System Type]:
- ✅ Correct Examples:
Certain Company+Traffic Brain+Management SystemCertain Group+Water Treatment+Smart Monitoring ScreenCertain Bank+Supply Chain Finance+Risk Control Middle Platform
⚠️ Audit and Interpretation Rights
- Manual Audit: Whether a specific business name is compliant must be submitted to the TechUI administrator or your exclusive business manager for manual audit and judgment. TechUI reserves the final right of interpretation regarding project name compliance.
- Rejection Mechanism: If the submitted name is judged to be too broad, the application will be rejected, and you will need to resubmit more specific business qualifiers.
- Upgrade Channel: If you truly need to use a broader, more general system name (such as "Enterprise Unified Portal", "Group Master Control Screen"), please purchase the [Company License] directly. The Company License has no restrictions on project names and allows unlimited use under the enterprise entity.
Operational Mechanism
- Prime Edition (@techui/prime):
- Mechanism: Heavy License.
- Configuration: Pass in the exclusive Client Key and Keychain. The Client Key encrypts the bound project name.
- Base Edition (@techui/scifi / base / admin):
- Mechanism: Lite License.
- Configuration: Pass in an encrypted License String.
Selection Suggestion
If you want the browser title to change dynamically with routing (e.g., displaying "Home", "User Center"), or if you have multiple projects needing TechUI, please consider upgrading to the [Company License], which has no title locking restrictions and supports unlimited projects.