Documentation

Guides for protecting production JavaScript

Reference guides for release workflows, command-line usage, cross-file protections, and the desktop app.

Inside The Docs

Practical guides, not placeholder pages.

How-to guides Start with release sequencing and command-line usage, then move into feature-specific references.
Advanced protection Browse cross-file controls like Replace Globals and Protect Members when a build spans multiple scripts.

JSO AI

JSO AI helps customers choose and review JavaScript protection settings with clearer guidance. It does not replace JavaScript Obfuscator; it sits beside the online tool and desktop app so you can make better decisions before a protected release goes out.

Use it when you want plain-language help choosing a preset, checking whether a release needs extra testing, or understanding which setting to adjust after protected code behaves differently than expected.

Start here

What JSO AI helps with

Preset guidance. Describe what you are protecting in plain English. JSO AI suggests a starting profile you can review before applying.

Compatibility checks. Find areas that may need extra testing after protection, such as dynamic loading, framework hooks, public callbacks, or names that must stay stable.

Error explanations. Paste an error or stack trace and get a practical explanation of which protection setting is most likely involved.

Protected-output review. Higher tiers add more review capacity for important releases so your team can see where stronger settings are useful and where lighter settings are safer.

Targeted protection suggestions. AI Corporate and Enterprise focus attention on sensitive functions, such as license checks, paid-feature gates, fraud rules, or proprietary algorithms.

AI-resistance evidence review. The CLI evidence packet includes a source-free review assistant your team can use with a BYO AI key or an internal reviewer to check failed evidence, missing review tracks, VM scope, runtime evidence, compatibility proof, and planned Resistance Score wording before a buyer handoff.

Payment-page script review. Script inventory audits now include a source-free review assistant packet your team can use with a BYO AI key or an internal reviewer to turn unknown scripts, owner gaps, data-access notes, and approval-ticket gaps into action items.

Plans

Plan Price Monthly guided checks Best for
AI Basic 19ドル / month 50 Individuals choosing presets and checking compatibility before publishing.
AI Corporate 79ドル / month 500 Teams that need higher limits, release review, and targeted protection suggestions.
AI Enterprise 299ドル / month 5000 Organizations that need the largest AI capacity and support for security reviews.

JSO AI plans are separate from JavaScript protection plans. For example, you can use Basic protection with AI Basic, Corporate protection with AI Enterprise, or no AI add-on at all.

AI key and payment

  • Start from AI key settings and save an OpenAI or Claude key with Save and test.
  • BYO-key calls still count against JSO AI action limits, while provider billing stays with your OpenAI or Claude account.
  • The usage dashboard shows your current plan, monthly usage, remaining limits, provider-key status, and AI key health.
  • Test stored key every 30 days, and rotate or review provider access every 90 days or after team, provider, or billing-owner changes.
  • When managed JSO AI billing is active for an account, logged-in customers can use secure Stripe Checkout from the AI order page.
  • If managed checkout is not active, the order page sends you to AI key settings or support instead of failing silently.

Usage limits

JSO AI uses capped monthly limits. The dashboard shows guided checks used, review capacity used, and remaining capacity for the current billing month.

  • Guided checks are user-visible events such as a preset suggestion, compatibility check, or explanation request.
  • Review capacity covers larger review work where the amount of submitted code matters.
  • No surprise overages. When a limit is reached, JSO AI pauses the request and points you to the upgrade path instead of billing more automatically.

Data handling

  • Submitted snippets are used to complete the requested JSO AI action.
  • Preview tools run in limited mode when no live provider key is available.
  • Production AI processing follows the same practical boundary as protection requests: code is processed for the request and is not kept as a reusable training corpus.
  • Organizations that do not want AI assistance can leave the add-on disabled.

Roadmap

ReleaseTimingWhat customers get
Preview and BYO keys Available now Preview pages, encrypted BYO provider keys, live provider-backed answers for accounts with keys, AI key health, usage dashboard, and capped usage reporting.
Managed billing Account-gated Stripe Checkout and subscription management for accounts where managed JSO AI billing is enabled.
Release review Late 2026 Deeper protected-output review, targeted protection suggestions, and suspicious-code checks for higher tiers.
Enterprise evidence Early 2027 Larger customer-specific review reports for security and vendor evaluations.

Positioning

JSO AI is not sold as magic or as a promise that protected JavaScript can never be analyzed. It is a practical review layer: it helps customers choose settings, avoid common compatibility mistakes, and explain protection choices more clearly during internal review. The AI resistance evidence page is the public checklist for what can be reviewed today and what remains planned.

Next step: add your provider key on AI key settings, then open JSO AI usage to track limits. For security review, read AI resistance evidence.