Self-Hosted. Developer-Controlled.

Your Software.
Your Rules.

License your desktop apps and web domains from one private workspace. Bind devices, issue keys, and stay in control of who gets access.

Open Dashboard Contact Coder Zorc

Built By Coder Zorc·PHP + MySQLi·Your Infrastructure

One API. Every Integration.Example Flow

POST/api/v1/license/validate

{
  "application_id": "app_your_application",
  "session_token": "your_session_token",
  "hwid": "your_stable_device_fingerprint"
}

Access Is A Current Decision

Check. Enforce. Repeat.

Bind a license to a stable device fingerprint, then revalidate before protected work.

5s Default Check Interval3s Request Timeout

Read The API Docs

Control Without The Clutter

The License Controls
Your Software Needs.

Handle access from one workspace, with clear rules for your applications and the people using them.

Bind Devices With HWID

Tie desktop licenses to an application-scoped fingerprint. Set device limits and reset bindings when hardware changes.

Lock Exact Domains

Choose the exact hostnames a web license can use. Keep the private application key on your trusted server.

Manage Every License

Generate keys, pause access, resume remaining time, and revoke licenses. Existing sessions are checked against current state.

Recheck Access Automatically

Included loader examples check status every five seconds by default and stop protected work on denial or connection failure.

See What Changed

Review activations, resets, administrator actions, and API activity. Understand access decisions from the same panel.

Keep Your Own Infrastructure

Self-host the PHP and MySQLi backend, inspect the included clients, and integrate through a straightforward JSON API.

Built For Your Stack

Ten Languages.
One Licensing API.

Start with an included client or loader example. Desktop and trusted web integrations follow the same licensing lifecycle.

Rust

Python

VB.NET

Pascal

C++

PHP

Node.js

Electron

Dart

Browse Loader Examples

Choose your language. Keep the API contract.

From Setup To Access

A Clear Path To
Your First Integration.

Create An Application

Choose desktop HWID binding or web domain locking. Keep each product's rules in its own application.

Generate A License

Set the customer, expiry, device limit, or allowed domains. Save the full license key when it is shown.

Integrate And Recheck

Activate through a loader example, then validate regularly before allowing protected operations.

Know How It Works

A Few Useful Details.

When Do License Changes Take Effect?

At the next online check. The included examples use a five-second interval and a three-second request timeout. A denied or failed check blocks subsequent protected work; keep already-running work short or interruptible.

How Does HWID Locking Work?

Your application reports a stable, application-scoped device fingerprint. The service matches it to the license's device bindings. HWID is a client identifier, not hardware attestation; it can change after a reinstall or hardware migration.

How Are Web Domains Checked?

Your trusted server sends its configured hostname and private application key. The hostname must match the license's exact allowlist. Keep that key out of browser code, and do not treat an incoming Host or Origin header as proof of entitlement.

Where Can I Find The Documentation?

The admin panel includes the API reference and language examples. Open The Documentation, or Contact Coder Zorc on Telegram for project questions.

Built By Coder Zorc

Your Next Integration
Starts Here.

Open your workspace, or get in touch about Obsidian Auth.

Open Dashboard @ZorcTheDarkOne

Your Software.Your Rules.