Three license tiers. One private-deployment platform.
NiuX TMS is delivered through three license tiers — Enterprise, Flagship, and Source Code — all deployed in your own infrastructure. This is deliberate: data residency, compliance, and long-term TCO predictability are the reasons enterprises and channel partners choose us over SaaS-only incumbents.
A Managed Service is available on request for qualified use cases.
Enterprise License
Private deployment for mid-sized operators
Compiled product, standard functional modules, and 1 year of upgrade + maintenance. Deployed in your VPC or data center. The entry point into a private-deployment TMS without the complexity of full engineering ownership.
Mid-sized logistics operators, regional shippers, new business units within larger groups. Operations that want data sovereignty but don't need source-level customization.
- Private deployment is required by compliance, finance, or IT policy.
- Your operating model is close to the platform's standard — configuration over customization.
- You want predictable CapEx economics, not escalating SaaS renewals.
- Your integration needs can be met through the standard API surface.
- — Large enterprises needing deep custom workflows or rule-engine authoring access.
- — Partners planning to resell the platform under their own brand — go to Source Code License.
Flagship License
Full platform + rule / form / process authoring
Compiled product, the complete functional surface, plus configuration rights over the rule engine, form engine, and process engine. 1 year of upgrade + maintenance. The most common path for mid-to-large enterprises with distinctive operating models.
Mid-to-large enterprises with complex multi-role operations, industry-specific compliance (dangerous goods, bonded, pharmaceutical cold chain), and deep ERP / MES / WMS / financial integration needs.
- Private deployment is mandatory — not a preference.
- You need to encode business rules, forms, and workflows your own IT team owns.
- You have group-level consolidation, multi-currency, or multi-tax-jurisdiction reporting.
- You want to integrate deeply inside your security perimeter, not via public API.
- — Operations that will never outgrow standard industry workflows — Enterprise License is simpler.
- — Partners or system integrators looking for source-level extension rights and resale rights.
Source Code License
For regional partners and group-level buyers
Full source code, build tooling, and engineering training. Region-exclusive terms available for qualified partners. The strategic partnership tier — you own the product in your market.
Regional system integrators and IT service firms wanting to offer enterprise TMS in their market under their own brand; large corporate groups standardizing a shared platform across many subsidiaries.
- You're an IT services firm or SI with 10+ Java engineers, ready to localize and extend.
- You want territory-protected resale rights in one or more countries.
- You need the ability to modify the core — not just configure or extend.
- You're a group with many subsidiaries and want one engineering-owned platform standard.
- — Single-enterprise end customers — Flagship License fits better.
- — Buyers without the engineering bench to own a full enterprise-grade codebase.
Compare
Side-by-side, on the decisions that matter
The dimensions below are what actually drives tier selection in enterprise and channel conversations — not marketing axes.
| Dimension | Enterprise | Flagship | Source Code |
|---|---|---|---|
| Commercial structure | One-time license + annual maintenance | One-time license + annual maintenance | One-time license + co-development + regional resale agreement |
| Deployment topology | Your VPC, private cloud, or on-premises | Your VPC, private cloud, or on-premises | Your infrastructure — and your customers' infrastructure |
| Functional surface | Standard modules (dispatch, settlement, portal) | Full platform, all modules | Full platform + source code |
| Engine authoring access | Preconfigured rules / forms / processes | Rule engine + form engine + process engine (authoring rights) | Full engine authoring + source-level extension |
| Admin & customization | Configuration within provided surfaces | Configuration + custom extensions via engines | Configuration + extensions + core modifications |
| Data sovereignty | Your infrastructure, your decision | Your infrastructure, your decision | Your infrastructure — across your subsidiaries or customers |
| Integration posture | Standard API surface | Deep integration inside your VPC | Deepest integration (including source-level customization) |
| Territorial rights | End-customer use only | End-customer use only | Region-exclusive resale rights available for qualified partners |
| Typical time to production | 4–12 weeks | 12–18 weeks | 20–24 weeks (includes partner engineering enablement) |
| Upgrade path across models | → upgrade to Flagship License when the engines are needed | → upgrade to Source Code License for source-level freedom or resale | Most flexible position; no upgrade needed |
Questions buyers actually ask
FAQ — the honest version
Do you offer a managed SaaS service?
Not as a default. Running SaaS across multiple countries brings data-residency, compliance, payment-channel, and 24×7 multi-timezone support obligations that we deliberately route into our channel partners' local operations instead. For qualified use cases — for example, a shorter proof-of-value engagement, or a small operation where private deployment isn't yet justified — we can arrange a Managed Service on request. It is not the main commercial path for this phase of our overseas program.
Why don't you list specific prices?
Because meaningful pricing depends on your operating scale (number of users, shipments per year, integrations, customizations, deployment topology) and — for Source Code License — on the territory and engineering scope. Any number published here would be misleading for 80% of buyers. We'd rather spend 30 minutes understanding your context and give you a defensible number than publish a headline figure that doesn't match your reality.
Can we start with Enterprise License and move up later?
Yes. The platform runs the same core across all three tiers. Migration paths are built into our commercial templates — many customers start with Enterprise or Flagship to prove the model, then move to Source Code License when they need source-level freedom or when they build channel capabilities of their own.
What's included in annual maintenance?
Core platform updates, security patches, bug fixes, new feature releases, and standard technical support. Professional services (integration work, custom development, process consulting) are scoped separately — typically delivered by us directly for Enterprise / Flagship customers and jointly with a certified partner for Source Code License deployments in their territory.
How is the Source Code License protected against misuse?
Let's be precise first: the licensee receives the <strong>complete</strong> source tree — nothing withheld, nothing swapped for an encrypted binary, no 'core engine as a service' carve-out. The dispatch / VRP optimization, rule engine, form engine, process engine, billing, and integration services are all delivered at source level to the named licensee. The protection is against <em>external</em> misuse, not against the licensee: (1) Legal — the Source Code License Agreement (drafted with international counsel) defines a named licensee, a territorial scope, and prohibits resale, open-sourcing, or transfer to any third party, with meaningful damage clauses. (2) Delivery — source is handed over to a designated build environment with an audit trail of who accessed what. (3) Commercial — annual maintenance plus upgrade alignment keep the licensee connected to the mainline roadmap, so forking into obsolescence becomes an unattractive option compared to staying on the upgrade line.
How do we know NiuInfo will still be around in 10 years?
Fair question for a platform investment. NiuInfo has been operating since 2015, carries national high-tech enterprise credentials, holds multiple patents in digital freight, and publishes the "Digital Freight" textbook used in Chinese university logistics programs. We serve Fortune Global 500 customers, publicly listed enterprises, and strategic state-owned operators. And for Perpetual / Source Code License customers, the commercial structure ensures that your platform operation does not depend on our cloud availability or our corporate calendar.
Not sure which tier fits? That's exactly the conversation we want.
15 minutes with our global team. Tell us about your operating scale, integration landscape, territory, and risk posture — we'll recommend a tier and give you a defensible number.