From checkout to lights out
A kit is a folder of plain files: Python and shell code, systemd units, configuration templates, prompts for your model and runbooks. Here is the whole path.
1. Checkout
You pay through Whop. A licence key is created the moment the payment clears and sent to the email you used at checkout, together with a link to your downloads page.
2. Download
Your downloads page lists every kit your licence covers, with release notes. Each release is checked before it is published: it is built from a clean copy, scanned so that no key, password, account id or personal detail from our own fleet can reach you, and installed on a fresh machine by the release job.
3. Setup
Every kit has one setup script and one configuration file. The script checks your system, installs what is missing in an isolated environment, asks for nothing it does not need, and finishes with a dry run that shows exactly what would happen, without touching your accounts.
4. Lights out
Switch the timers on. From then on the work happens on schedule: your local model writes and translates, the pipelines build and render, the watchdogs restart what fails, and one email reaches you when a human decision is needed.
Your accounts stay yours
- Kits use the official APIs of each platform wherever one exists, with keys you create and can revoke.
- Browser robots reuse a session you signed in to yourself; they never type passwords or solve captchas.
- Guards are on by default: daily caps, duplicate checks and policy pre-checks keep your accounts away from the patterns platforms punish.
Updates
Every purchase includes twelve months of updates. New releases appear on your downloads page with notes on what changed and whether your configuration needs a new value.
Updated: