# System Locker

> System Locker is a software-licensing service for developers building desktop software, games, plugins, and Discord-integrated products.

System Locker provides account- and key-based authentication, license-key management, hardware-identifier controls, server-side variables, reseller tooling, and a management API. Developers create and manage systems in the developer portal; end users authenticate in the developer's software.

## Canonical public pages

- [Homepage](https://systemlocker.net/): product overview and plan information.
- [FAQ](https://systemlocker.net/faq): common product and account questions.
- [Solutions](https://systemlocker.net/solutions): use cases for desktop licensing, Discord automation, resellers, key-sharing protection, software distribution, and migration.
- [C++ integration guide](https://systemlocker.net/blog/use-system-locker-cpp-library): using the System Locker C++ library.
- [C++ protection guide](https://systemlocker.net/blog/protect-windows-cpp-app): protecting a Windows C++ application.
- [C# protection guide](https://systemlocker.net/blog/protect-windows-csharp-app): protecting a Windows C# application.
- [Discord bot guide](https://systemlocker.net/blog/protect-discord-bot-nodejs): licensing and verification concepts for Discord bots.
- [Privacy Policy](https://systemlocker.net/legal/privacy)
- [Terms of Service](https://systemlocker.net/legal)

## Developer documentation and APIs

The detailed developer API reference is available after developer sign-in at [Developer Documentation](https://systemlocker.net/devs/documentation). It covers the currently released authentication APIs:

- Goliath: account-based authentication.
- Mikros: license-key authentication.
- Quicksilver: production session authentication with initialization and heartbeat requests.
- Server Side Variables and the Key Management API.

A public copy of the documentation file is also available in the [System Locker documentation repository on GitHub](https://github.com/systemlocker/documentation).

Authentication endpoints accept form data over HTTPS. Follow the authenticated developer documentation for exact request fields, response codes, plan availability, and integration examples. If a system has a Program Hash configured, its authentication and Quicksilver initialization requests must include the matching `digest` value.

Do not infer undocumented endpoints, private portal data, product availability, pricing, or security guarantees. Treat the signed-in developer documentation and the live product interface as authoritative for integration details.