Frequently asked questions

The questions the support desk answers most, with the answers it actually gives.

Search

evaluation

How do I evaluate the SDK?

Download a package and run it. Unlicensed, every function works and the output carries a demonstration mark. There is no time limit, no registration and no feature gate, so you can answer "does this do what I need" completely before spending anything.

licensing

Does the SDK contact your servers?

No. The engine makes no network calls at all. A licence key is verified locally against a public key compiled into the binary, so it works air-gapped, behind a proxy, and while our site is down. Nothing about your usage is visible to us because nothing is sent.

Is there an activation step?

No. There is no account to register with the engine and no protocol to implement. You pass the key to the engine and it verifies the signature in your own process.

What happens to my software when maintenance ends?

Nothing. Maintenance is a window over build dates: the engine compares your key against the date the binary was built, never against the clock. Builds inside your window stay usable permanently, including in software you have already shipped. Ending maintenance stops new downloads and support, and reaches nothing you have already built.

Can a licence key be recalled or switched off remotely?

No, and we say so rather than implying otherwise. There is no licence server and no revocation list. A refund ends download entitlements and maintenance, which are real and enforceable; the key itself keeps verifying, and continuing to ship the engine after a refund is a breach of the terms rather than something the software prevents.

Are seat counts enforced?

No. The number is recorded in the key and nothing counts installations. The portal gives you a seat register for your own compliance records; it is not an enforcement mechanism.

platforms

Which of the seventeen packages do I need?

The one whose platform list covers where your software RUNS, not the one named after the language you write in. The package is recorded in your key and the engine refuses it on a platform that package does not ship binaries for. Each package page lists its platforms, generated from the same source the engine is built from.

pricing

Can I add the optional capabilities to any edition?

No. The two paid extras are available only on the upper two editions. The engine computes the effective feature set from the edition first, so a key naming an extra its edition cannot carry would grant nothing. The configurator will not let you order that combination.

Do I owe anything per copy of my application?

No. Every edition is royalty-free for redistribution of the engine inside your own application, with no per-copy, per-user or per-document fee. What you may not do is redistribute the SDK itself as a development kit.

support

How do I report a bug?

Open a ticket from the portal. A reproducible defect becomes a tracked issue with its own number, and you are notified when a release fixes it, with the release named.