Why we license the source code of our TMS — and who should actually buy it

In international enterprise software, "we'll license you the source code" is normally a negotiation tactic — something a vendor concedes after fifteen months of procurement friction. We treat it differently. A NiuX TMS Source Code License is a standard product tier with a published shape and a clear rationale. This post explains that shape, and — more importantly — who should and should not buy it.

The three-tier structure, briefly

NiuX TMS is sold, internationally, in three licensing tiers. All three deploy into the customer’s own VPC or data center — we do not run a public SaaS as our primary commercial path.

• Enterprise License. Private-deployment entry tier. Standard modules, configurable rules. One-time license + annual maintenance. Suited to mid-sized operators and regional shippers.
• Flagship License. Full platform on private deployment, with rule / form / process engine authoring rights. Most common path for mid-to-large enterprises with distinctive operating models.
• Source Code License. Full source code plus build tooling, engineering training, co-development, and — for qualified partners — region-exclusive resale rights.

This article is about the third tier. For the first two, see the pricing page.

What “source code” actually means in a NiuX TMS license

Let’s be precise, because the phrase “source-code license” is used very loosely in the market — and in enterprise software it is often used dishonestly. Vendors sign the paperwork, deliver a partial tree, and keep the VRP engine, the pricing engine, or some other “core IP module” behind an encrypted binary the licensee can only call over an API. That is not a source-code license; it is a source-reading arrangement.

We do not do that. Our stance is simple:

Concretely, under a NiuX TMS Source Code License the named licensee receives:

1. The full Java source tree of the TMS platform — all of it: domain services, the rule engine, the form engine, the process engine, the dispatch / VRP optimization engine, the billing and settlement engines, and the integration services. No module is delivered as an encrypted library. No module is held back as a “vendor-hosted API service.” The optimization core that competitors typically keep closed is, in our licenses, simply part of the codebase you receive.
2. Build and release tooling — the exact toolchain we use to produce the binaries you would otherwise buy under Flagship License.
3. Engineering knowledge transfer — a bounded set of days with our architects walking your engineers through the module boundaries, the plug-in points, the data model, and the upgrade path.
4. Continuous upgrade alignment — we ship you our main-line releases, not a frozen snapshot; you keep the right to integrate or skip each release.
5. Region-exclusive resale rights for qualified partners, under a defined territorial scope.
6. A legally-binding protection envelope — around the codebase (IP, non-compete terms, redistribution rules) that protects both sides against third-party misuse.

What you do not receive:

• A public open-source license. This is a commercial source license with enforceable boundaries. The code is not redistributable outside the contract — the licensee is named, the territory is named, and transfer to any third party is prohibited. That is what keeps the arrangement commercially workable for everyone else in our partner network.
• A blank check on support. Source-licensed customers get our engineering alignment, but they are expected to carry Tier-1/2 support for their own clients — that is the whole point of the tier.

In other words: the license is narrow in who can use it (one named licensee, one named territory), and wide-open in what they receive (the whole platform, at source). That asymmetry is deliberate. It is also, in our experience, the only honest way to offer this product tier — and the reason customers choose NiuX TMS over vendors whose “source-code license” turns out to be a misleading brochure.

Why we even offer this tier

Three reasons, in honest order:

First, because some customers are structurally unable to depend on a vendor binary. Regulated industries (defense logistics, state-owned enterprises, certain pharma cold chains), sovereign-cloud deployments, and multi-subsidiary groups with 10–20 year planning horizons cannot accept a platform where a vendor’s continued existence is a single point of failure. For them, escrow is not enough; they need an operational copy of the source.

Second, because the serious overseas channel model requires it. A regional IT firm in Vietnam, the UAE, or Mexico cannot build a credible local TMS business on top of a SaaS they don’t control. They need to integrate deeply with local ERPs, local tax systems, local carriers — and they need to offer their own support SLA to local customers. The only commercial structure that lets a partner do that honestly is a source-licensed, territorially-scoped relationship.

Third, because it forces discipline on our own architecture. Vendors who know their source will be read by outside engineers write better code, draw cleaner module boundaries, and resist the temptation to bury integration contracts in undocumented internals. Source licensing has made NiuX TMS a better platform — not only for source-license customers, but for every Enterprise and Flagship License customer as well.

Who should not buy a Source Code License

It is more useful to tell you when this tier is the wrong answer than to pitch it.

• If your constraint is “we want SaaS pricing.” Source licensing carries a one-time license commitment substantially larger than an annual SaaS subscription. If you’re optimizing for a low monthly spend with no upfront, the Enterprise License — or even a Managed Service arrangement — is closer to what you actually want.
• If you do not have an engineering team. Source licensing assumes you can read, build, and responsibly modify the platform. If you have no in-house Java engineers and no intention of hiring any, a Flagship License gives you the same functional surface with far less operational risk.
• If you want to resell globally. Our Source Code License is territorially scoped. A partner in Ho Chi Minh City gets exclusivity in Vietnam, not in Germany. This is by design — global exclusivity would eliminate the economic reason for other regional partners to ever invest in NiuX TMS.
• If you want to fork the platform and never speak to us again. We won’t stop you contractually (within the license terms), but you will lose the mainline upgrade path, the rule-engine changes, the tax-zone updates, and the new integrations we ship every quarter. Most enterprises who thought they wanted this end up regretting it within 24 months.

If any of those describe you — stop reading and talk to us about Enterprise or Flagship License instead. You will get to outcome faster and at lower total cost.

Who should buy it

Three archetypes, in descending order of how common they are:

1. Regional channel partners (system integrators, IT service firms)

Most commonly, a 100–500 person local IT firm with an established base of enterprise customers in transportation, manufacturing, or retail, looking to add a TMS offering to a portfolio that already includes ERP implementation or WMS work.

Their economic logic is straightforward: they want the license margin, the services margin, and the durable territorial right. A SaaS reseller margin is thin and time-limited; a source-licensed territorial partnership produces a business that compounds.

What we look for in this kind of partner: a real engineering team that can support Tier-1/2 without our intervention, a committed go-to-market motion (not “we’ll see if a customer asks”), and a realistic 3-year sales and services plan. In exchange, we align on territory, provide training, share marketing assets, and — in some cases — co-sell into named accounts.

The Partner Program page and the printable one-pager describe this in more structured form.

2. Large groups standardizing across subsidiaries

The second archetype: a multi-business-line group (30+ entities, several countries) that wants one transportation platform across the group, while letting each subsidiary configure its own operating model.

For this buyer, the Flagship License is often enough on functional grounds. The reason they still upgrade to Source Code is control: twenty-year planning horizons, internal-audit requirements around platform risk, and the wish to have group-internal engineering able to extend the platform without vendor involvement. At this scale, the license cost is rounded off by a rounding error in the corresponding IT risk line-item.

3. Sovereign / regulated deployments

Smaller in number but strategically important: state-owned operators, defense logistics, certain cross-border pharma cold-chain operations, where the platform’s continued availability must be independent of the vendor. A Source Code License plus a signed co-development agreement is, in practice, the only acceptable contractual shape.

How we structure the first conversation

If one of those descriptions fits, the first conversation with NiuInfo typically covers — in this order:

1. Your current transportation footprint. Number of loads per day, carrier mix, geography, integration surface.
2. Your business model. Are you a partner reselling into your territory, an enterprise standardizing across subsidiaries, or a regulated operator.
3. Your internal engineering capacity. A source license only makes sense if you can responsibly operate it.
4. Scope, territory, and term. A 3-year minimum commitment is typical for the partner archetype; longer for group and sovereign archetypes.
5. Commercial shape. Upfront license + annual maintenance + services. Specific figures depend on scope, territory, and support expectations — we do not publish numerical price lists because the shape of the deal is bespoke per archetype.

We do not sign a Source Code License in under eight weeks. The due diligence — in both directions — is worth it.

A closing note on control

In most international TMS RFPs we’ve seen over the past two years, the single word that appears more than any other is “control.” Control over data. Control over deployment. Control over upgrade timing. Control over integration surface. Control over who — and when — touches production.

We cannot promise that a Source Code License is the right answer for every enterprise that writes the word “control” into an RFP. We can promise that it is the single cleanest way we know to transfer operational control of a non-trivial TMS platform to a customer or partner, without giving up the ability to upgrade, evolve, and keep learning from the rest of our deployment base.

If you think that fits — or you’re not sure and want an adult 45-minute conversation to find out — talk to our team. Bring the real decision you’re trying to make; we’ll tell you honestly which tier fits.