Subscribe, download the desktop launcher, and launch verified game builds with one click.
This is a desktop game launcher distribution service. Users register an account, choose a subscription for the products they want, download the launcher binary, and run verified game clients on their own computers. Every launcher binary is signed, every payload is integrity-checked against a server-side manifest, and every active session is tied to the hardware that authorised it.
The platform is built for users who want a one-click way to manage multiple Minecraft modifications across several game versions without juggling JAR files, JVM installs, mod loaders, or launcher arguments by hand. The launcher handles the JVM, the Fabric loader, library and asset downloads, version pinning, file repair, and process supervision for you.
Each account is bound to a single hardware fingerprint on first launch. Account sharing is blocked at the launcher level — a stolen password can't be used from another machine without an admin-issued HWID reset.
Every launcher response is wrapped in an Ed25519-signed envelope. The launcher refuses to run a build whose signature doesn't match a known trust anchor — an attacker on the network can't substitute a tampered binary.
Your account can hold multiple active subscriptions simultaneously. The launcher reads the active list and exposes only the products you've actually paid for — no gating, no soft-locks, no "limited free version".
If an antivirus quarantines a launcher asset mid-play, the launcher re-downloads the missing file on next launch and verifies the MD5 against the server manifest. No manual reinstall required.
Time-based one-time passwords via any standard authenticator app (Google Authenticator, Authy, 1Password, Bitwarden). 2FA is mandatory for staff and optional for end-users.
Discount codes apply to specific products and tiers. A code can be capped at a number of uses, scoped to a single product, and expire on a fixed date. Apply the code at checkout, the discount surfaces immediately in the order summary.
The desktop launcher and the games it ships support modern Windows desktops. Older platforms aren't tested or supported.
No. Each product has tiered subscription pricing visible in the shop. You can browse the product catalogue without an account; an account is only required at checkout. The launcher binary itself is free to download once you have at least one active subscription.
Card payments through the integrated payment provider. The exact options depend on your region. Refunds follow the standard consumer-protection rules of the jurisdiction you bought from.
Open a support ticket from your profile page and describe the change. Staff can reset your HWID binding within minutes during European business hours. The reset is not automatic to make stolen-account hopping more expensive for attackers.
Only while the game is launching and while the game itself is running. The launcher exits cleanly when you close the game window. It does not install drivers, kernel modules, or background services.
The launcher binary is signed and submitted to mainstream AV vendors. Heuristic engines occasionally false-positive on a fresh release; if your AV blocks the binary, whitelist the folder where you installed it (typically ~/.lightning on Windows) and rerun the launcher.
No. A single account binds to a single hardware fingerprint at first launch. If you want a license on a second machine, either reset your HWID via support (one machine at a time) or purchase a second subscription.
The launcher refuses to start the game once your subscription ends. Your account remains active, your profile and history are preserved, and you can re-subscribe at any time. No data is deleted.
Yes. Within 14 days of purchase, if you haven't used the launcher more than a handful of times, you can request a refund via support. Full terms are on the Terms of Service page.
Email, hashed password, hardware fingerprint, subscription history, and the IP address used at login. We don't sell, share, or rent personal data. Full details on the Privacy Policy page.
Contact support from the email address registered on the account. Recovery requires proof of original purchase (order ID or last four digits of the card used). Reset usually completes within one business day.
Questions, account recovery, refund requests, or any other support need: open a ticket from your profile page once logged in. Pre-login enquiries can use the contact channels listed on the contact page. Average first response time during European business hours is under one hour; outside business hours, up to 24 hours.
This platform is operated by an independent software development team. We're not affiliated with the games we ship — we provide a desktop distribution channel for licensed users of the underlying titles. If you believe a product on the platform infringes your rights, contact us through the support channel and we'll respond within five business days.
The launcher is a Rust + Tauri 2 desktop application. The Rust core handles authentication, file synchronisation, hardware fingerprinting, JVM management and process supervision; a small embedded webview renders the UI you see on screen. The choice of Tauri over Electron is deliberate — the final binary weighs a few megabytes instead of hundreds, and the attack surface is significantly smaller.
The server side is a Node.js application backed by MySQL. Every state-changing request is logged in an immutable audit trail; staff actions (granting subscriptions, generating keys, banning users) leave a record that includes the actor, the target, the time, and the IP. Payment events are reconciled against the upstream payment provider every minute by a background poller so a missed webhook never costs a user a paid subscription.
For a longer technical write-up, including the file integrity model and the security architecture, see the about page.
Account security and binary integrity matter on a platform that handles real-money subscriptions and runs as a desktop process. Here is what is in place, in plain language:
The launcher logs in using your site credentials. The site validates the password against a bcrypt hash with a per-account salt; passwords are never stored in plain text. After successful login the launcher receives a short-lived signed envelope containing a JWT plus product manifest pointers. The JWT carries the user id, the role, the HWID it was bound to, and a server-side issue timestamp. Every later API call is signed so a man-in-the-middle can't replay or modify the envelope without invalidating the signature.
Most account-sharing fraud on a paid game distribution platform comes from people who buy one license and split it across several real users. HWID binding pins a license to the hardware that first redeemed it, so a leaked password can't be used from a second machine without an admin-issued reset. The reset path costs the attacker an extra round-trip through support, which is enough friction to kill the casual reseller market for our subscriptions.
The launcher pulls game files from a CDN-fronted endpoint. CDN edges occasionally cache stale objects, antiviruses silently strip files mid-stream, browser security middleboxes inject HTML challenges in front of binary downloads. Without integrity checks any of those would result in a corrupted install that the user would interpret as "the launcher is broken". The launcher refuses to launch unless every product file matches the server-side MD5, and re-downloads anything that doesn't.
2FA is mandatory for staff accounts because a stolen staff password is worth a lot more than a stolen user password — staff can grant subscriptions, ban users, generate licence keys. 2FA is optional for end-users; even so, anything that touches money (changing payout details, requesting a payout) re-prompts for a fresh TOTP code even on a 2FA-verified session.
Each product has three subscription tiers: a short trial-style 7-day tier, a 30-day standard tier, and a 90-day power-user tier. The 30-day tier is the value sweet spot — it covers most users' usage patterns without locking them into a quarter-long commitment. The 90-day tier is for people who already know the product and want a discount; per-day it works out 25-30% cheaper than the 30-day tier.
We deliberately do not run promotional sales beyond the published tier pricing. A user who buys today and a user who buys in three months pay the same price; that is fair to both. We do issue promo codes for partner programmes and for compensation when something goes wrong on our end (extended downtime, file integrity failure that took a long time to diagnose). Those codes never lower the headline price — they extend the duration of what you already paid for.
Refunds inside the 14-day cooling-off window are handled on a case-by-case basis through the support channel. We're not in the business of forcing money out of people who tried the product, decided it wasn't for them, and want their money back — that's a recipe for chargebacks and unhappy reviews, both of which cost more than the refund itself.
HWID — Hardware ID. A fingerprint computed by the launcher on first run from a small set of stable hardware identifiers (motherboard serial, primary disk serial, machine SID). The launcher reports the HWID at login and the server verifies it matches the value bound to the account.
JVM — Java Virtual Machine. The runtime that executes Minecraft and its mods. The launcher ships a pinned JVM build per game version so users don't have to install Java themselves and so we control the exact runtime used.
Fabric loader — A Minecraft mod loader for modern versions of the game (1.14+). The launcher downloads the Fabric runtime files for each game version once, shared across every Fabric-flavoured product on that version.
Manifest — The server-side list of files a product needs, each with an expected MD5. The launcher compares this list against what's actually on disk and downloads any mismatch.
Ed25519 envelope — A signed JSON wrapper around server responses. The signature uses the Ed25519 elliptic-curve signature scheme; the launcher carries a hard-baked public key and refuses anything that doesn't verify against it.
Sweep ban — When a user is banned for cheating in another product or for chargebacks, the system also bans the HWID. Any subsequent account that logs in from that HWID is automatically banned. This makes "buy a fresh account from a seller, run the launcher again" significantly less effective.
Cascade access — When an account has multiple active subscriptions, launching one product is allowed even if a different product was selected in the launcher UI, provided both are on the same game version. The system logs every cascade launch so admins can see how products overlap.
Idempotence key — A unique per-request identifier sent to the payment provider on payout requests. If the same request is retried (transient network error, our retry logic) the provider de-duplicates by key and doesn't pay out twice.
TOFU — Trust on first use. A pubkey distribution mode where the client trusts whatever public key the server returns on the first connection and pins it locally. Used in the launcher only on platforms where we can't ship the public key embedded in the binary; production users always use the embedded key.
Treasury drain — The operator-triggered batch transfer of the payment provider shop balance into our payout account. Operates manually instead of automatically because the provider API is rate-limited and slow.
The platform is under active development. Major changes from the last few months:
The full audit log of administrator actions is visible to anyone with admin role on the site. This is intentional — staff actions on a platform that handles paid subscriptions should be auditable, not opaque.