Skip to main content
Version: 1.27 (Current)

Licensing

Audience: Plant an App Admins

Skill Prerequisites: General Understanding of SaaS Licensing

Overview of Licensing in Plant an App

Licensing in Plant an App controls how your organization accesses and builds on the platform. Understanding your license type is essential for compliance and to ensure you unlock all needed capabilities.

Licensing Types in Plant an App​

Plant an App offers a flexible and modular licensing model, suitable for organizations and agencies of all sizes, as well as independent developers.

Main Licensing Components​

  • Runtime Licensing: Allows your application to run for end-users, and supports development based on the number of developer seats you have.
  • Developer Seat Licensing: Controls the number of individual developers that can access building/configuring features at the same time. Seats are personal and tied to both the user and their device/browser. Learn more about developer seats.
  • Legacy Licensing: A traditional model, still available, which may grant unlimited users, unlimited developer seats, or other features not offered in typical Runtime licenses.
  • MultiPortal Licensing: An add-on for Enterprise that lets you use Plant an App modules across secondary portals/tenants within a hosting environment. MultiPortal details.

Plant an App Plans: Feature Summary​

Below is a summary of core plans. Full feature lists and latest pricing are available here.

Starter Plan (Runtime)​

  • 1 Developer Seat Included
  • Free Training Academy
  • Cloud Deployment (Plant an App’s cloud)
  • Community Support
  • Core Data & UI features

Harvest Plan (Legacy or Runtime)​

  • Everything in Starter
  • Single Application
  • AI features
  • 100 Users included
  • Free Cloud
  • Custom Branding
  • Agent-Based Support
  • Single Environment + Dedicated Cloud Resources
  • API Builder
  • Automated Backups

Enterprise Plan (Legacy or Runtime)​

  • Everything in Harvest
  • Unlimited Users
  • Single & Multi-Application Options
  • Dedicated Technical Success Manager
  • Dedicated Server Setup
  • Self-Hosting Option
  • Multiple Environments
  • SSO Integration
  • SLA Support
  • Shared Source Code (full platform)
  • Premium Add-ons and Connectors

MultiPortal Licensing Overview​

MultiPortal Licensing enables Plant an App components (Forms, Listings, Search, Nav, etc.) to be licensed on additional/secondary portals inside a multi-tenant (multi-portal) environment. Typically, this capability is essential in large organizations or agencies managing several web properties on a single DNN (DotNetNuke) installation.

Key Points:

  • Requires Plant an App Enterprise plan and Plant an App v1.24+ (on-premises).
  • Requires available site licenses.
  • Install the MultiPortal Licensing add-on and activate each secondary portal you wish to license.
  • Once activated, you can build with Forms, Listings, and more on licensed portals.
  • Read the MultiPortal Licensing documentation.

How Developer Seats and Activation Work​

  • Each seat is assigned to an individual and their device/browser (for concurrency limits and compliance).
  • Accessing admin/configuration features prompts for seat activation.
  • Seats may be transferred between devices, but only one device/browser combination per seat is active at a time.
  • All plans except Legacy require at least one developer seat (Harvest/Enterprise plans allow more by purchase).
  • Learn more about how developer seats work and best practices for management.

Best Practices & Considerations​

  • Match your plan to your business scenarios (e.g., use MultiPortal for multi-tenant SaaS/agency scenarios).
  • Assign unique logins/seats to each developer—no shared accounts or devices.
  • Manage activations actively—deactivate unused seats before onboarding or device changes.
  • Review plan levels for your needed features (backup, support, premium add-ons, user limits, etc.).

Additional Resources​