1
Create account
Use email and password to create the customer workspace. Passwords are stored as Argon2id hashes.
Start here
Create an account or sign in before purchase
The commercial flow is account based. A customer creates an account, opens a manual payment request, then receives the license key in the customer portal after operator approval.
2
Open manual payment
Checkout creates a 48-hour manual payment request for exactly one 30-day license.
3
Receive license key
After approval, the customer portal exposes a one-time license key delivery for installation.
Product
Built for controlled self-hosted deployments
The commercial package is distributed as an installer-driven, source-free deployment with central license checks, signed release metadata and a customer-facing portal experience.
One active installation
A license key activates one active lease. Moving to a new server supersedes the old installation on the next check.
Signed downloads
The client verifies release metadata, package size and SHA-256 checksum before installation or update.
Operator visibility
Admin screens cover licenses, billing, suspicious usage, release state, support and pre-sale readiness.
Pricing
Simple 30-day commercial license
No plus/pro/ultra split at launch. Every customer starts with the same 30-day self-hosted license model.
EUR 9
per 30-day license period
Plan splitNone
License period30 days
ActivationFirst use starts period
CheckoutReady flow
Commercial package
The sales surface includes checkout, help and status
Customers can reach the purchase flow, signed downloads, help center, customer portal and service status from the public experience.
Checkout flow
The manual payment contract creates exactly one 30-day license after operator approval.
Help center
Install, update, troubleshooting and support intake are presented as a customer-facing support entry point.
Status page
License API, download page, backup and abuse controls have a visible operations surface.
Security
Source-free delivery with server-driven licensing
The customer receives installer and compiled artifacts, not readable team-authored source. License policy is enforced by the license server and checked by the self-hosted gateway.
