Why Licensing + Payments Matter

When you’re ready to sell a plugin/add-in (e.g. Autodesk/Rhino/Revit/SketchUp), you need two things:

‍

1. a way to process payments, and
   ‍
2. a licensing system that ensures only paying users can run your compiled add-in under the terms you set (duration, features, per-seat/per-device, etc.) - including offline use.
   ‍

Options: Platform Stores vs. Devolens

Platform stores (e.g., Autodesk App Store, Food4Rhino, Extension Warehouse)

‍

• Great for discovery and distribution.
  ‍
• Purchase verification exists, but per-seat, per-device, or feature-gated enforcement typically requires extra work.
  ‍
• Payments and policies are platform-defined.

‍

Devolens (third-party licensing)

‍

• Use any payment flow (or invoice B2B) and keep store listings for reach.
  ‍
• Built-in models: per-seat/device, floating/concurrent, per-feature/edition, usage-based, subscriptions, trials.
  ‍
• Offline capable (signed tokens) and friendly to secure environments - no server you need to run.
  ‍
• Works across Autodesk, Rhino/Grasshopper, SketchUp, and companion tools with one approach.
  ‍

Tip: Many teams publish a free/trial listing for exposure, then unlock paid features in-app with Devolens.

‍

Implementation: License Verification

Devolens supports all major programming languages, such as C#/.NET (Revit/AutoCAD/Rhino), Python (Maya/Fusion), and C++.

C# example (simplified):

‍

var licenseKey = "GEBNC-WZZJD-VJIHG-GCMVD"; // <--  remember to change this to your license key
var RSAPubKey = "enter the RSA Public key here";

var auth = "access token with permission to access the activate method";
var result = Key.Activate(token: auth, parameters: new ActivateModel()
{
    Key = licenseKey,
    ProductId = 3349,  // <--  remember to change this to your Product Id
    Sign = true,
    MachineCode = Helpers.GetMachineCodePI(v: 2)
});

if (result == null || result.Result == ResultType.Error ||
    !result.LicenseKey.HasValidSignature(RSAPubKey).IsValid())
{
    // an error occurred or the key is invalid or it cannot be activated
    // (eg. the limit of activated devices was achieved)
    Console.WriteLine("The license does not work.");
}
else
{
    // everything went fine if we are here!
    Console.WriteLine("The license is valid!");
}

Console.ReadLine();

Protecting Plugin Files

‍

• Defense-in-depth: signature verification + occasional online checks + lightweight integrity/obfuscation.
  ‍
• Feature flags: ship one build; unlock commands/components per license.
  ‍
• Grace & swaps: allow device moves with limits to keep admins happy.
  ‍

Benefits You Get With Devolens

‍

1. Per-seat/per-device control; floating pools for labs and shared machines.
   ‍
2. Offline flows with signed, time-limited tokens for secure sites.
   ‍
3. No custom server: hosted verification or fully offline - your choice.
   ‍
4. Cross-ecosystem: one licensing approach across Autodesk, Rhino/Grasshopper, SketchUp, and sidecar tools.
   ‍
5. Analytics & control: activations, versions, adoption; automate renewals and policy.
   ‍
6. Payment-agnostic: plug in your processor or invoice enterprise customers.
   ‍

FAQ - Add-ins & Plugins

Can I keep listing on the store and still use Devolens?
Yes. Keep the store for discovery and run licensing/payments in-app.

Do you support per-seat and per-device?
Both. Bind to users or machines, or mix them. Set limits and grace rules for swaps.

What about floating/concurrent seats for labs?
Supported. Define seat pools with check-out/check-in and idle timeouts; scope per site or customer.

Will it work offline (gov/lab/air-gapped)?
Yes. Issue signed offline tokens with expiries; renew on your schedule.

How do I prevent copying of the plugin file?
Use signed license checks plus light integrity measures. Even if a file is copied, features stay locked without valid entitlements.

Do I need multiple builds for editions (Standard/Pro/Studio)?
No. Ship once and toggle commands/components via entitlements.

How long does first integration take?
Teams commonly report gating one feature in about an hour (varies by codebase).

Can we migrate from an existing licensing setup?
Yes. Import keys/customers, run in parallel, and cut over by cohort with rollback options.