Knowledge base

How-to articles, platform notes and troubleshooting, written against the packages we actually ship.

Search

Getting started

Installing a package and getting output from it.

• Choosing the right package The package you buy decides which platforms your key will run on. Pick it from how you build, not from what you write in.

Licensing

Keys, editions, packages, seats and maintenance.

• How licensing works, and why there is no activation step The engine verifies a key locally. There is no server, no activation, and nothing to go down.
• What maintenance covers Maintenance is a window over build dates. It never affects software you have already shipped.
• Seats are recorded, not enforced The seat count rides in the key. No code counts installations, and the portal register is yours to keep.

Platforms

Notes specific to one platform or one package.

• PHP: what the FFI binding needs The PHP package calls the engine through FFI, which has two hard requirements and one platform exclusion.
• Bitness has to match the interpreter A 64-bit interpreter cannot load a 32-bit engine. This is the most common first-run failure in the script packages.

Troubleshooting

Things that go wrong, and what they mean.

• Why the output has a demonstration mark Two causes, easy to tell apart: no key reached the engine, or the key does not cover this platform.
• Reading the build stamp in the changelog Each release prints the date its binary was cut. That is the number your licence window is compared against.