Node Supply Chain System

Supply chain software, delivered to your infrastructure

Your supply chain, on your own servers.

Plan, source, make, deliver and return — one system, deployed to hardware your company owns and your team operates. Your operational data stays there. There is no shared database holding several customers’ records, because there is no copy of yours to hold.

Create an account

One account per person, one company per subscription.

At least 15 characters. No required symbols or capitals — length is what makes a password strong.
Accounts are not open yet. The form works; the service behind it is the next thing being built.

Already have an account? Sign in.

Where it runs
Your server, your cluster, your network boundary.
What we see
Whether an instance is healthy and which version it runs.
Licence
Annual subscription, covering releases and support.
Provenance
Every release signed; the key is published for you to check.

What it covers

Seven areas, one model, and the assumptions written down.

Plan

Demand forecasting with stated uncertainty, inventory policy, lot sizing.

Source

Supplier selection, award optimisation, and supplier risk beyond the first tier.

Transform

Production planning, scheduling, and the quality loop around them.

Fulfill

Warehousing, picking, routing and the last mile.

Return

Reverse logistics, disposition and recovery.

Order

Order promising and pricing, against what the network can actually do.

Orchestrate

Network design and the risk work that constrains everything above.

Every model

States what it assumes and what data it needs. A model that hides either is not usable knowledge.

How it is delivered

Installed where you are, not rented where we are.

The system is deployed to infrastructure you contract. Your team installs it, your team holds the credentials, and the data it works on never leaves your boundary.

What we maintain is the software: releases, security fixes and the adjustments your deployment needs. One outbound channel reports health and version so we know an instance needs attention. It carries nothing of your business.

Being a version behind is not a fault. Under this model you run the release your own IT team installed.

Verifiable, not just claimed

You do not have to take our word for any of this.

Every release is signed and the public key is published, so you can verify an artefact before it ever reaches your cluster. Your instance refuses to admit an unsigned image — not as a setting that can be forgotten, but as a policy that fails closed.

The public key, the exact command to run and what a verified signature does not prove are all on one page, because a claim you cannot check is just a sentence.

How to verify a release

Subscription

One instance, one year, one fee.

The licence covers maintenance, releases and support for your deployment. An active subscription is what entitles an instance to run.

Nothing about how much you use it enters the price, so nothing about how much you use it needs to leave your server. Your bill is a number you can count on your own side.

The amount is not published yet. What is settled is what it is charged on, which is the half that decides whether an invoice can be predicted — a figure without that would have been a number nobody could check.