Pay for what your binary is worth.
For developers selling paid Java plugins: protect the JAR, issue license keys, revoke abuse, and trace leaks without writing license code. Four tiers, one engine. Start free, upgrade when your plugin starts paying for itself, scale up to Studio when you have real customers, and unlock the crown-jewel transforms when the cost of a leak gets serious.
Hobbyist
Real protection, no card needed. Try the engine on side projects and small mods. Every transform that doesn't require a paid license is on by default.
- 5 builds per day · 2 active projects
- Symbol distortion, string concealment, control-flow flattening
- Decoy classes · per-build polymorphic encoding
- Mapping & build report
Paid plans
Switch billing interval. Pay yearly to get two months free.
Pro
Everything that actually moves the needle on a paid plugin.
Billed monthly. Cancel anytime.
- 20 builds per day · 10 projects
- Everything in Hobbyist
- Custom JavaObf virtualization on hot methods
- Native Entry Bridge for entry + dispatchers
- Real runtime validation against Paper
- White-label output (no JavaObf attribution)
- Product Licensing 5 products · 100 active licenses
Cancel anytime in the billing dashboard.
Studio
For studios with paying customers. 5× the licenses, priority support, native key stub.
Billed monthly. Cancel anytime.
- 60 builds per day · 30 projects
- Everything in Pro
- Native key stub (Linux + Windows)
- Priority build queue
- Direct support channel
- Programmatic Licensing API tokens
- Product Licensing 25 products · 500 active licenses
Cancel anytime. Upgrade prorates from Pro.
Enterprise
For binaries you cannot afford to lose.
Billed monthly. Cancel anytime.
- Unlimited builds per day · 100 projects
- Everything in Studio
- Highest hardening tier on every transform
- Priority queue with reserved capacity
- Direct line to engineering
- Custom invoicing & net terms on request
- NDA & security review available
- Product Licensing Unlimited products & unlimited active licenses
Need an invoice or NDA? Reach out on Discord.
Side by side, no fluff.
The engine ships the same transforms on every plan. Paid tiers unlock the heavy hitters: VM, native stub, runtime validation, and white-label output.
Common questions, honest answers.
Is JavaObf safe to use on paid plugins I sell on a marketplace?
Yes. The transforms are descriptor-aware. Plugin entrypoints, paper-plugin.yml, fabric.mod.json, mods.toml, mixins, and access wideners are all auto-locked. The protected JAR ships with the same loader contract the platform expects.
Why pick Studio over Pro?
Studio is built for teams with real customers. You get 5× the active licenses (500 vs 100), the native key stub on the engine side, priority build queue, direct support, and the programmatic Licensing API for automating issuance and revocation. If you ship to more than ~100 customers and want to remove the Stripe ceiling, Studio is the right shape.
Do I need the Pro plan to ship something for money?
No. The Hobbyist plan is real protection, just without the heavy transforms (VM, anti-tamper interlocks). It is fine for low-stakes plugins and personal commercial work. Pro is where the math against a motivated reverser starts to actually shift.
What is the difference between Custom JavaObf virtualization and the native key stub?
Custom JavaObf virtualization rewrites your Java methods into a private, per-build opcode set executed by an embedded interpreter shipped inside the JAR. Decompilers see dispatcher noise instead of source code. The native key stub goes one level further: critical key derivation is compiled into a heavily hardened native runtime layer shipped for the supported desktop platforms. The Java side becomes a thin shell. The actual code is not Java anymore.
How does the yearly discount work?
Yearly billing is 10× the monthly price. You pay for ten months and get two months free. Pro is $290/yr, Studio is $780/yr, Enterprise is $1,490/yr. Switching mid-cycle prorates automatically through Stripe. You can flip back to monthly at the next renewal from the billing dashboard.
What happens if I cancel?
Obfuscation-only builds keep running forever. Nothing in the protected JAR phones home for your subscription. License-gated builds (Product Licensing module) are different: new activations, key issuance and revocation, dashboard access, and gateway validation all require an active JavaObf licensing plan, because the patched runtime continuously revalidates against our gateway. To avoid sudden disruption, cancelled accounts enter a 30-day read-only grace period during which existing license-gated products keep validating. After that window new activations stop and existing sessions fail closed on next revalidation.
Can I get a discount as an open-source maintainer?
Yes. Drop a link to the project in our Discord. We grant Pro for free to maintainers of widely used open-source Java tools.
What is included in runtime validation?
Pro, Studio and Enterprise subscriptions can have the protected JAR booted against a real Paper server during the build. The build report tells you whether the plugin loads and whether your descriptor locks survived the transforms. Catches reflection, mixin, and access-widener issues before you ship.
Get a feel for it before you spend a thing.
The free tier is generous on purpose. If your plugin is worth protecting, you'll know after the first build report.