Version 1.0 Production Architecture

Self-hosted licensing & auth for your software.

License keys with duration-on-activation. Hardware binding with drift tolerance. Encrypted runtime payload delivery. Automated purchase fulfillment.

main.cpp — Client Integration
// Initialize runtime client & claim session
auto client = SvAuth::Client::Create({ "https://auth.yourdomain.com", "myapp" });
auto session = client->LoginPassword(username, password);

// Decrypt release payload directly into memory
auto binary = client->UnlockPayload(session.token);
binary.ExecuteInMemory();
your entire integration

Built for Software Protection

Engineered to defend native runtimes, stop license sharing, and automate fulfillment.

License Keys

One-time key activation. Subscriptions begin on redemption, supporting tiered access and lifetime grants.

HWID Binding

Machine slot governance. Built-in drift tolerance allows buyers to upgrade GPUs without locking out.

Encrypted Payloads

Release binaries are packaged using AES-256-GCM via svauth-packer. Decryption keys remain exclusively in server memory until authenticated—patching the check leaves attackers with an unexecutable locked box.

Seller Dashboard

Isolated tenant panel. Manage users, reset hardware slots, and enforce granular app-scoped IP bans.

Purchase Automation

Inbound webhooks automatically mint and dispatch license vouchers upon Gumroad, Stripe, or Whop sales.

Security Engine

Monotonic replay mitigation, honeypot traps, shadow bans, automated threat rules, and tamper auditing.

Real-time Sessions

Signed heartbeat authority with sequence validation and instantaneous remote session revocation.

Buyer Accounts

Integrated credential management. Buyers redeem once to link their key to a personal account, logging in on subsequent launches with simple credentials while protected by adaptive lockout safeguards.

How It Works

Deploy authentication and software distribution in three direct steps.

1

Register Application

Create your application record in the dashboard and configure hardware binding rules, allowed tiers, and version enforcement.

GET /admin/apps/:name
2

Pack Your Payload

Encrypt your compiled DLL or executable locally before release. Your plaintext files never leave your build environment.

npx svauth-packer pack --app myapp --secret $SECRET --in client.dll --out payload.bin
3

Sell & Distribute

Distribute the locked payload. Customers authenticate through your client, which decrypts the binary directly into memory.

POST /v1/auth/unlock

Transparent Tier Limits

Self-host freely for smaller releases, or scale up to dedicated multi-app quotas.

Free
For indie releases, testing, and private tool distributions.
$0 / forever
  • 1 Application
  • 20 Active Registered Users
  • 30 Active or Unclaimed Keys
  • Full Auth & HWID Stack
  • Community Support
Start Free
No credit card required
Pro
For high-volume distribution networks and commercial studios.
$49 / month
  • 10 Applications
  • 10,000 Active Users
  • 5,000 Keys
  • Storefront Automation Relays
  • Discord Bot Integration Soon
  • Dedicated Escalation Support
Contact to Upgrade
Enterprise & custom quotas available
Note: Commercial plan upgrades are currently provisioned manually by platform staff via direct contact.

Frequently Asked Questions

Technical operational details and architecture specifications.

SvAuth is deployed directly onto your own infrastructure (VPS, bare metal, or Docker container). You maintain 100% custody of your PostgreSQL database, Redis caches, buyer identities, and hardware telemetry without third-party vendor lock-in, random downtime, or external access to your customer base.
When a buyer changes physical machine components (such as upgrading a GPU or motherboard), their machine signature may exceed their license slot allowance. Sellers can reset a buyer's hardware binding with a single click in the dashboard, or configure automated component drift tolerances so routine hardware swaps do not interrupt access.
SvAuth provides a dedicated inbound webhook endpoint (POST /v1/seller/purchase/:appName). When an order completes on Gumroad, Stripe, Whop, or Sellix, your store webhook posts to SvAuth accompanied by your private purchase secret. SvAuth instantly mints the key and returns the license voucher directly to your store middleware for immediate delivery.
Conventional auth systems return a basic boolean response, which attackers easily bypass by patching a single jump instruction. SvAuth solves this using encrypted payloads via svauth-packer. Release binaries are encrypted with AES-256-GCM. The decryption key exists only in server memory and is released only upon valid cryptographic challenge verification. Patching the authentication check leaves the attacker with an unexecutable, encrypted binary.
No. Buyers redeem their license key once during account registration to bind the license to their username and password. On subsequent launches, they authenticate seamlessly using standard credentials while the server validates their active subscription status in the background.
Yes. All seller IP bans are strictly scoped to the seller's specific application. Unlike platform-wide IP bans, an app-scoped IP ban prevents connections to your application only. Other applications and sellers sharing the platform or customers on shared residential CGNAT pools remain entirely unaffected.
Yes. SvAuth includes production-tested C++20 and TypeScript SDKs. The C++ SDK supports MSVC, Clang, and GCC with zero external dependencies, featuring automated challenge-response handshakes, monotonic sequence heartbeats, and in-memory AES-256-GCM payload decryption.