Pricing
Straightforward licensing
Choose the Basic, Pro or Ultimate edition, as a developer or a company license. A developer license covers a single developer: an independent individual, or a company with just one software developer. Every purchase includes 12 months of updates and email support. Buy once, ship as many protected products as you like.
Developer
Company
Basic
Renews at €49€99/year for continued updates
The core virtualization engine for hardening your most sensitive code.
- Code virtualization (VM protection)
- Control complexity of virtualized code
- VM section renaming
- String encryption
- Protect any target, including the entry point
- Application packer suite
Most popular
€199 €149.25 developer license
€459 €344.25 company license
Pro
Renews at €69€139/year for continued updates
Everything in Basic plus the full application packer suite.
- Everything in Basic
- Application packer with compression
- Anti-debugging & import protection
- Anti-VM, anti-monitor & anti-sandbox
- Anti-tamper & anti-dump
Ultimate
Coming soon
Pricing announced at release
Everything in Pro plus an integrated licensing system.
- Everything in Pro
- Licensing system
All prices exclude applicable taxes: VAT or sales tax is calculated and added at checkout by our merchant of record, Paddle. Every purchase includes 12 months of updates and email support, and is covered by a 14-day money-back guarantee. After the first year, Dhaedalida and everything you have protected keep working. Renew at the rates shown to keep receiving new versions.
Compare
What's in each edition
| Feature | Basic | Pro | Ultimate (coming soon) |
|---|---|---|---|
| Code virtualization (VM protection) | ✓ | ✓ | ✓ |
| Complexity of virtual machine obfuscation | ✓ | ✓ | ✓ |
| VM section renaming | ✓ | ✓ | ✓ |
| String encryption | ✓ | ✓ | ✓ |
| Application packer (compression) | — | ✓ | ✓ |
| Import protection | — | ✓ | ✓ |
| Anti-debugging | — | ✓ | ✓ |
| Anti-VM | — | ✓ | ✓ |
| Anti-monitor | — | ✓ | ✓ |
| Anti-sandbox | — | ✓ | ✓ |
| Anti-tamper | — | ✓ | ✓ |
| Anti-dump | — | ✓ | ✓ |
| Licensing system | — | — | ✓ |
| Developer license | — | ||
| Company license | — | ||
| Renewal / year (developer) | €49 | €69 | — |
| Renewal / year (company) | €99 | €139 | — |
| Updates included | 12 months | 12 months | 12 months |
FAQ
Licensing questions
What's the difference between a developer and a company license?
A developer license is registered to a single developer: an independent individual, or a company with just one software developer. A company license is registered to your organization and can be used by your whole team. Either way there is no limit on how many products you protect or how many copies you distribute.
What happens after the first year?
Your license, the software and everything you have already protected keep working: nothing expires. To keep receiving new versions after 12 months, renew at the reduced annual rate: €49 (developer) or €99 (company) for Basic, and €69 (developer) or €139 (company) for Pro.
Can I upgrade between editions?
Yes. Upgrade from Basic to Pro at any time and pay only the difference for the remainder of your update period. Ultimate upgrades will be available when it is released. Use the Get Notified button above to hear about it first.
Is there a launch discount?
Yes, a founding launch offer is running: the first 25 licenses are 25% off, and the prices above show both the regular and the discounted amount. The discount (code FOUNDER25) is applied automatically when the checkout opens. Nothing to type. Once those licenses are gone, the offer ends.
How does purchasing work?
The Buy buttons open Paddle's secure checkout (Paddle is our merchant of record). Paddle accepts major cards and popular payment methods (availability varies by region), calculates and adds any applicable VAT or sales tax, and emails your receipt and invoice. VAT-registered businesses can enter their VAT ID at checkout.
When do I get my license?
Paddle emails your receipt right away, and we deliver your license by email from info@dhaedalida.com within 24 hours of purchase. Nothing after 24 hours? Check your spam folder, then contact us and choose "Order & billing".
Do you offer refunds?
Yes. Every purchase is covered by a voluntary 14-day money-back guarantee: if Dhaedalida does not fit your workflow, email billing@dhaedalida.com within 14 days of purchase and we will refund you in full. Refunds are processed by Paddle, our merchant of record. The free demo lets you evaluate the core protection before buying, so we hope you never need it. Statutory rights of EU consumers remain unaffected. See our Terms.
Why should I trust a new protector?
Don't take our word for it: test it. The free demo protects your own binaries, so you can put the protected result under a disassembler and judge it before paying a cent. The documentation describes exactly what each protection layer does instead of promising magic, and every protected build gets its own per-build VM architecture, so your output shares no static signature with anyone else's. And nothing is held hostage: your license and everything you have already protected keep working even if you never renew.
Which platforms are supported?
Dhaedalida protects Windows 32-bit and 64-bit executables and DLLs (PE32 and PE32+
.exe and .dll). The marker SDK ships bindings for C, C++, Rust, Go, Delphi/Object Pascal, D, Zig, Nim and assembly. Any native x86/x64 language works. See the features page for the full capability list.My application is getting flagged by lots of antivirus products
Software protectors rely on techniques that malware crypters also use (encrypted sections, dynamic API resolution and code obfuscation, among others), so some antivirus engines may wrongly flag a protected application as malicious. We recommend code-signing every application with a certificate after protecting it, which tends to reduce false positives. Most antivirus vendors also offer a channel to report false positives so their detection improves.
Can I digitally sign my protected files?
Yes, code signing is fully supported. The only requirement is the order: sign your files after protecting them, not before. A digital signature embeds a cryptographic hash of the file, and protection necessarily rewrites the file (adding new sections among other changes), so a signature applied before protection would no longer match and become invalid. Protect first, sign last: that way your signature covers exactly the bytes your users receive.