Introduction

Server-authoritative license and auth for Windows desktop software. Ships as three drop-in SDKs (C#, C++, Python) and a plain HTTPS API for anything else that can send a signed request.

Get started

Ship your first license flow in under ten minutes.

Applications

Create, configure, and manage the products you protect.

Manage keys

Generate keys, bulk-edit, extend, and ban them.

Users

Track end users, IPs, HWIDs, and login history.

HWID lock

Bind a license to one machine, reset it when hardware changes.

Security practices

What we protect versus what you need to protect yourself.

C# SDK

.NET Framework 4.7.2+ on Windows.

C++ SDK

Native x64 and x86 with heartbeat support.

Python SDK

CPython 3.12 x64 on Windows.

HTTP API

Build your own client. Every endpoint documented.

Heartbeats

Kill a live session on injection or drift.

FAQ

The common questions customers ask.

What Obsidian is

A licensing service. Every app you register gets its own API key pair, license pool, end-user table, and set of security toggles. Every register, login, license check, and heartbeat lands in the dashboard in real time and stays queryable from the logs afterwards.

Obsidian is not an obfuscation service. It authenticates your build and proves the server said what the client thinks it said. Whether your .exe survives IDA is a separate problem, solved by VMProtect, Themida, or whichever protector you already run on release builds.

What people use it for

License-gated Windows software. That covers reseller platforms, game trainers and utilities, trading bots, private automation, internal tools, and the long tail of paid desktop apps that need an "activate with a key" screen. If your product can send an HTTPS POST, Obsidian can gate it.