Trust
Security
How the platform is built, what protects license traffic, and how to report a vulnerability.
Architecture
- The website and validation endpoint run on Cloudflare Workers at the edge.
- Turso (libSQL) is the system of record for accounts, products, licenses, teams, tickets, and OAuth grants.
- New JARs and watermark uploads are stored in Backblaze B2 through a scoped application key.
- Dashboard sign-in uses Discord OAuth. Third-party applications use our OAuth 2.0 provider with explicit, per-application scopes.
- Payments run through PayPal. Card details never reach our servers. Transactional email runs through Resend.
- Short-lived validation and page caches use Upstash Redis. License enforcement is always read from Turso, never from a cache.
Controls
- HTTPS with HSTS preload, a restrictive Content Security Policy, frame denial, MIME sniffing protection, and a strict referrer policy.
- Per-product API keys authenticate validation requests. Keys are never issued to buyers and never embedded in a public download.
- Every successful validation returns an ES256 JWS. The private key stays on our infrastructure, and the public key set is published at /.well-known/jwks.json.
- Nonces make responses single use, tokens expire after four hours, and verification rejects unknown key ids and mismatched product or hardware claims.
- Rate limits apply per API key, per license, and per source IP. The Free plan includes 4,000 requests per day on a rolling window.
- HWID binding, IP limits, and per-license watermarks trace sharing and leaked builds to the license that produced them.
- Admin accounts sign in with Discord OAuth, require two-factor authentication on Discord, and leave an audit trail for administrative actions.
Change notice
We give at least three days notice before a change that would break a correctly implemented integration. That covers the UlisesLib API, the validation endpoint contracts, and any cryptographic format change. Security fixes may go out sooner if delay would increase risk.
Scope
- uliseslicenses.xyz, including the web platform, dashboard, and public API.
- The license validation endpoint and its API key authentication.
- UlisesLib, the license verification library.
- The OAuth 2.0 provider and its consent flow.
Rules
- Test only against accounts and licenses you own.
- No denial of service, spam, or automated scraping.
- No accessing other users' data. Stop and report if you can.
- Give us reasonable time to fix before any disclosure.
How to report
Email hello@uliseslicenses.xyz with steps to reproduce, impact, and your contact. We acknowledge within 3 business days and keep you updated until resolution. Good-faith research following these rules will not face legal action from us.
A machine-readable contact is published at /.well-known/security.txt.
Found a crack?
If you built a license bypass, patched UlisesLib, or found a way to make a validation call return a valid license without one, we want it. Send the artifact and the version it targets to hello@uliseslicenses.xyz. We confirm receipt, work out whether the weakness is ours, and ship a fix where we can.
Two things we ask in return. Tell us before you publish, and handle anything we send like it is designed to compromise you: open it in a disposable environment, never on a machine holding real license or account data. There is no fee, no credit requirement, and no minimum-effort bar. Finding nothing is a perfectly good outcome too.
We also want to hear about cracks in customer plugins built with UlisesLib, even when the defect is not ours. Send whatever you have and we will look at it.
For administrators
Platform admins sign in with Discord OAuth. Admin accounts must have two-factor authentication enabled on Discord. Admin actions are logged.