Questions

Getting started

What kind of software is ClavisAUH for? Software installed on your customers' machines: desktop applications, command line tools, games, plugins. There are SDKs for Node.js and Electron, Python, C#, C++, Go, Rust and Java; the C library for every language that can call a C function (Unity, Delphi and Lua included); and the command line tool for scripts and installers. Pick your guide in Get started by language.

Where do I get the SDK? Is it on npm, PyPI, NuGet? Not yet. Every SDK, the C library and the command line tool are on Downloads, each file with its SHA-256 to check before use.

Does it run on macOS? The SDKs written in their own language (JavaScript, Python, C#, Go, Rust, Java) have nothing specific to Windows or Linux, but ClavisAUH's CI does not run them on macOS yet. The C library and the command line tool have no macOS build yet.

How do I test without using my limits? Use test (TEST) keys: they do not count against your limits, expire after 24 hours and stop working when you turn on Publicly released. See Test before you sell.

Customers using your software

What if a customer has no network? The software keeps a signed offline token and checks it on the machine: 7 days on every plan, or the length you choose on Premium. A revoked license can keep working offline for that time, unless Online-Only Mode is on. See Offline licenses.

What if a customer changes machines? The new machine takes a seat on the key. When none is left you Reset devices, or the customer removes the old machine in the customer portal under the transfer rules. Reinstalling Windows or Linux changes the system's machine id, one of the few identifiers the SDKs send by default, so the reinstalled machine takes a new seat unless your software sends 4 to 6 stable hardware components, as the Devices guide shows. See Devices, HWID and transfers.

What about containers, virtual machines and CI runners? The SDKs recognize a machine from hashed identifiers: on Linux, /etc/machine-id and the network card's address. A fresh container gets new ones each time, so every run looks like a new machine and takes a new seat. Keep them stable (the same --mac-address and a fixed /etc/machine-id mounted read-only) and keep the state folder between runs for the offline token, or give such machines a key that allows enough devices.

What does ClavisAUH know about a customer's machine? Only hashes: the SDK hashes each hardware identifier on the machine before sending it, and raw values never leave the machine. Along with them come the device's public key, the machine name and operating system your software sends, and the IP address (with the country, when the server knows it) of each call, shown in the Activity log and Protect 24/7.

What error sentences do customers see? Each error code has a sentence for the user in English and Vietnamese, the same in every SDK. See Error codes.

Security

Can the software be cracked? No measure running on a customer's machine can fully stop someone with complete control of that machine. ClavisAUH keeps the decisions on the server and signs every answer, so a fake server or an altered answer does not get past the SDK; heartbeats, device keys and Protect 24/7 detect shared keys. See How the system works, The two protection modes and Protect 24/7.

Is it safe to embed the public key in my software? Yes: a public key only checks signatures and cannot sign anything. Your app's secret key never leaves the server. Change keys as Signing keys and rotation shows.

Selling

How do I sell automatically? Your store calls the Seller API on each order to make a key and send it to the customer. See Selling with the Seller API and Ship to your customers.

Can one key serve several products? No: each key belongs to one app. For several feature levels of one product, use license plans and entitlements in the same app.

How do Basic and Premium differ? See Basic, Premium and limits and the pricing.

Related

• Quickstart
• Core concepts
• Test before you sell
• Ship to your customers