Quick start

Go to Applications → New application. You need three things:

• Name — anything, shown to clients during init.
• Client version — the version string your loader will report, for example 1.0.0.
• Key mask — the shape of your keys. Leave SIMP-XXXX-XXXX-XXXX if unsure.

Decide the hardware policy now, because changing it later invalidates every device already bound. One device per key with CPU plus MachineGuid is a sensible default. See hardware locking.

On save you get a public application id and a 32 byte secret. The secret is never displayed; it only ever leaves the server inside an SDK download.

Open the Releases tab. Create a release, give it a version such as 1.0.0, then upload each file with a JSON key: core for your main module, driver for a helper, and so on.

That key is the name your client asks for, so keep it stable. Publishing an update means putting a new binary behind the same key.

Finally press Make active. Only the active release is delivered, and a release with no enabled file cannot be activated.

Go to the Keys tab and press Generate. For a first test, one key, 30 days, level 1 is enough.

Keys are stored as an HMAC lookup plus ciphertext, so the table shows only a masked preview. Use the eye icon to reveal one, or Export CSV for a whole batch. Every reveal is written to the audit trail.

Open the SDK tab and press Download SDK archive. The archive is generated for this application, with the endpoint, application id, version, hardware policy and masked secret already written into keyauth_config.h. You do not paste any credentials by hand.

Unpack it and build:

build.bat

Or with CMake:

cmake -B build -S . -A x64
cmake --build build --config Release

Run keyauth_example.exe, paste the key, and you should see the license details followed by the active release and its files. The example writes each payload next to the executable.

The whole integration is this short:

#include "include/keyauth.h"
#include "keyauth_config.h"

int main()
{
    keyauth::Client client(keyauth_config::make());

    if (!client.initialize()) return 1;   // version check, opens a session
    if (!client.login(userKey)) return 1; // key check, binds the device

    for (const keyauth::FileInfo& info : client.files()) {
        std::vector<std::uint8_t> payload;

        if (client.download(info.key, payload)) {
            // payload is plaintext, decompressed, SHA-256 verified
            // info.key is the JSON key you chose in step 2
        }
    }

    client.validate();   // heartbeat, call every few minutes
    client.logout();
}

Watch the Activity tab while you do this. You should see init, login.success and release.deliver appear live.