Licensing
The platform is licensed per deployment. A licence is a key your installation presents to a validation endpoint; it carries a plan, an expiry and a deployment allowance. It is a software licence and nothing more — it conveys no account, no custody and no discretion.
How a key behaves
A key is issued once and shown once. We store only its SHA-256 digest, never the key itself, so a copy of our store cannot be used to produce a working licence — and neither can we recover yours. A lost key is revoked and replaced rather than looked up.
Validation answers one of four states, and they are reported distinctly rather than collapsed into “invalid”, so an outage can be diagnosed without a support round-trip: valid, expired, revoked, or unknown.
Deployment count is reported to you and to us, and is deliberately not enforced at the endpoint. Refusing a licence because a counter has drifted would take a running installation offline on the strength of bookkeeping — a redeploy, a container reschedule or a restart is not a licence breach. Where usage and allowance diverge, we talk to you.
The validation endpoint
One public, rate-limited endpoint. Your installation calls it; no session or operator credential is required, because a licence check has to work before anything else does.
POST /api/license/validate
Content-Type: application/json
{ "key": "lss_…", "instance_id": "prod-ams-1" }
A valid key answers:
{
"status": "valid",
"valid": true,
"license_id": "4f2a9c1b77e0",
"plan": "standard",
"customer": "Example Capital",
"expires_at": 1796150400.0,
"max_instances": 2
}
A key that is not valid answers with valid: false and the
reason in status. If our store cannot be read the endpoint
answers 503, never valid: false:
a disk fault on our side must not read as a revocation on yours, and
your installation should fail soft on a 503 rather than treat it as a
refusal.
What we log
The licence id, the outcome, and the calling address. Never the key. A key is a bearer credential, and a credential that appears in a log file appears in every backup and bug report of that log file.
Price
One licence, one deployment, billed annually.
Licence, monthly ZAR 5,000.00
Licence, annual ZAR 48,000.00 (12 x 5,000, less 20%)
Any tax that applies to you is shown on your invoice.
The live figure is served at /api/pricing; this table
and that endpoint are checked against each other so they cannot
disagree. Plans in full on the plans page.
Ways to pay
No automated checkout is live yet. Licensing is invoiced directly and settled by bank transfer: send the request form, we reply with an agreement and an invoice carrying our bank details and a payment reference, and the licence is issued once the transfer clears.
Card acquiring was tried and is closed to us. Three providers, three outcomes: one does not onboard South African businesses, one paused intake, and one reviewed the account and terminated it because execution infrastructure is a prohibited category for them. We would rather say that plainly than list payment logos for accounts that do not exist — a button that fails when you press it is worse than no button.
This paragraph is replaced automatically if a method is ever connected: the page reads the live list from the running configuration rather than from copy, so it cannot claim one that is not there.
Getting a licence
The full API documentation lives at /docs and opens once you are signed in with a licensed account.
Buying a plan on the checkout page issues the licence against the address you pay with, and these terms are the agreement. For a larger deployment allowance, a bespoke term or a negotiated contract, terms are agreed first and the key is issued afterwards. Enquiries: Kaizer.Makhubo@lucrum-superius-systems.com.
Important information
Trading leveraged derivatives carries a substantial risk of loss and is not suitable for everyone. This page is not financial advice, nor an offer, a solicitation or a recommendation to buy or sell any instrument, nor a recommendation of any trading strategy. No performance claim is made anywhere on this site, and a licence conveys no expectation of any result.
We license software and infrastructure. We do not manage client money, take custody of client assets, or exercise discretion over client accounts. Any prospective arrangement is subject to written agreement and to the licensing and suitability requirements of the relevant jurisdiction.