Bring your code
Start with a single, already-built JavaScript file. Keep your original source somewhere safe.
BUILT FOR JAVASCRIPT/ 01
Your code works hard.
Keep it yours.
Protect the logic behind your JavaScript with virtual-machine based obfuscation. Built for the code you want to share, and the ideas you want to keep.
✳
A closer look at your next layer of protection.
Processing is not available in this preview.
JAVASCRIPT IN✳VIRTUAL MACHINE✳PROTECTED CODE OUT✳MADE FOR BUILDERS
THE WORKSPACE/ 02
A little more protection.
A lot more peace of mind.
Start with one built JavaScript file. Choose a mode and target, then review the result before putting it to work.
PROTECTION MODE
Designed for a balance of protection and runtime performance.
01Inputinput.js
0 bytes · single UTF-8 file
02Output
RESULT✳
Your protected code will appear here.Choose your settings and add a JavaScript file to get started.
No output yet↗
Processing is not connected in this preview. Your input stays in this page.
Supports a single built .js or .cjs file. ES modules, TypeScript and JSX need to be bundled first.
Planned Free limit: 30 KB per file.
THE APPROACH/ 03
The logic stays.
The view changes.
Obfuscation adds a layer of difficulty to understanding your code. It is one part of a broader security strategy, not a substitute for server-side controls.
Choose your mode
Select a VM mode and target environment that match your project and test requirements.
Test before shipping
Check the output in your actual runtime. Compatibility and performance depend on your code.
PLANS/ 04
Room to build.
Room to grow.
These are proposed plans for the service. Registration and billing are not yet available.
01 / FREE↗
Free
For getting to know the workspace.
$0 / month
- 20 successful tasks per UTC month
- 30 KB per file
- Web workspace access
- No external API access
02 / PROFOR MORE ROOM
Pro
For teams and projects doing more.
$19 / month
- 1,000 successful tasks per UTC month
- No plan-level file size cap
- Web workspace and external API
- $190 / year, billed annually
✳
The fine print matters.
Actual processing limits depend on available resources. Failed tasks are intended not to consume successful-task quota. Prices and limits are proposed and may change before launch.Read the details ↗GOOD TO KNOW/ 05
A little context
goes a long way.
Build with a clear understanding of what protection can and cannot do.
support@ldvmp.com ↗What does LDVMP do?
LDVMP is intended to transform a single built JavaScript file using a virtual machine-based obfuscation engine. The service is still being prepared and processing is not currently available.
Which files are supported?
The planned input is one UTF-8 .js or .cjs file. Bundle and transpile modules, TypeScript and JSX before uploading. Compatibility varies by syntax and runtime and must be tested.
Does obfuscation make code impossible to reverse?
No. Obfuscation can raise the effort needed to understand code; it cannot guarantee secrecy. Never put secrets in client-side code, and keep authorization and sensitive operations on the server.
How will my code be handled?
The intended service uses temporary private storage and deletes source files after processing. The actual retention and deletion behavior must be verified before launch. This preview does not submit your input.
When will the API and billing be ready?
The API, authentication and subscriptions are not connected yet. A complete API guide, service status and finalized policies will be provided when those services are ready.
Make your work
harder to unravel.
A more considered layer for the JavaScript you build.