RUCKUS ONE LICENSING GUIDE v5.8

Learn the RUCKUS One licensing model and process.

RUCKUS One Licensing Model

Decision 1Who owns it?
Decision 2What level do they need?
Decision 3How long should they commit?

Step 1: Work through the License Decision Model

Work through the key decisions that shape the licensing model so ownership, tier, and term come together clearly.

0 of 3 sections completed0%

Who owns and manages the environment?

This determines whether the opportunity aligns to a customer-owned or partner-owned motion.

What operating need is most true?

This helps determine whether the fit is Essentials or Professional.

What is the deployment and buying posture?

This guides term length and whether grace-period positioning should be used.

Step 2: How the Model Shows Up

This shows how the ownership model, tier, and term come together in the licensing structure.

Make selections to see how the model comes together.

Licensing Motion

—
Ownership determines whether the motion maps to REC or MSP SKUs.

Tier

—
Capability need determines Essentials vs Professional.

Term

—
Buying posture and timeline guide term length and grace-period positioning.

How the SKU Comes Together

—
The SKU pattern will populate once the ownership model, tier, and term are determined.
CLDCloud license family
—Tier code
APSWAP / Switch device family
—Ownership code
—Term code

RUCKUS One Licensing Model

  • Ownership determines whether the SKU maps to REC or MSP.
  • Capability determines whether the tier is Essentials or Professional.
  • Timing determines whether the term is 1, 3, or 5 years.
  • SKU structure follows CLD + tier code + APSW + ownership code + term code.

How license quantity works

  • RUCKUS One licensing is based on device count, not user count.
  • The primary count is how many supported devices need to be licensed, such as access points and switches.
  • In practice, the sizing question is usually: How many devices will consume a RUCKUS One license?
  • User count may matter for other solutions, but the core RUCKUS One model is centered on the number of licensed devices.

Step 3: How to Relay the Value

A Simple Talk Track

No talk track yet.

Why this works

    How to Think About It

    These prompts help connect the capability need to the right licensing direction.

    • Essentials: Use this when the need is core connectivity and a simpler management motion without a strong requirement for advanced operations.
    • Professional: Move here when the environment signals multi-site visibility, AI, automation, assurance, or a lean IT team.
    • MSP: Treat this as a partner-owned motion that maps to Professional capabilities rather than as a separate lower or higher feature tier.

    Quick guidance

    Simple shorthand
    Essentials = run the network.
    Professional / MSP = run the business on the network.
    • If the need is mostly connectivity, start with Essentials.
    • If the need is broader visibility, scale, AI, assurance, or operational efficiency, move to Professional.
    • If the partner owns and manages the service, map it to MSP SKUs and Professional capabilities.

    Tier Capabilities

    Use this to understand the practical difference between Essentials and Professional / MSP. MSP aligns to the Professional capability set, with a partner-owned operating model layered on top.

    This comparison is a summary by functionality meant to help position the tiers clearly. It is not intended to replace detailed product documentation or quoting validation.
    Area Essentials Professional / MSP
    Best Fit Core connectivity and simpler operating needs. Broader operations, scale, visibility, and managed-service use cases.
    Management model Run the network with a streamlined cloud management experience. Run the business on the network with a richer operations and management model.
    AI / automation Limited positioning for environments that do not need advanced assurance or automation. Stronger fit when AI, automation, assurance, and reduced firefighting are part of the value story.
    Scale / multi-site Works when the environment is more straightforward and the customer is not emphasizing broad operational complexity. Better fit for multi-site, distributed visibility, and more advanced operational requirements.
    Lean IT teams Good when the ask is primarily reliable networking without broader platform expectations. Better when the environment has limited staff and needs the platform to do more of the work.
    MSP alignment Not the default for MSP-led motions. MSP uses the Professional capability tier plus partner-owned licensing and management.

    Activation & Management

    This section explains what happens after the license is sold. The flow is simple: activate the license, it enters the account pool, and it is monitored over time.

    This section is intentionally lightweight and focuses on the core operational flow.

    How license quantity is typically measured

    • RUCKUS One licenses are generally consumed based on device count.
    • Think in terms of how many supported devices need a license, such as APs and switches.
    • This is different from models that are based on user count or named users.

    Simple lifecycle

    What’s happening What the customer / partner does What you should care about
    Activation Use the activation code from the SPA email or activate from the portal / RUCKUS One interface. Licenses must be activated before they are valid and usable.
    Start Date Select region and subscription start date during activation. Standard licenses have a 180-day activation grace period.
    Management View subscriptions, pending activations, and utilization in the portal. Watch licenses used, available or gap, and expiration timing.
    Compliance Review whether the account has enough active licenses for configured devices. A positive available count is healthy; a negative gap indicates shortage.
    Renewal Renew before or during the courtesy window to keep the experience intact. Renewal timing matters for continuity and retained configuration.

    Operational View

    This provides a clear view of the operational model without unnecessary detail.

    Where to look

    • Pending Activations → what has been purchased but not activated yet.
    • My Subscriptions / MSP Subscriptions → what is active and in use.
    • Compliance → whether configured devices are covered by available licenses.

    What happens if a subscription lapses

    • Devices may be removed from RUCKUS One but continue to operate with last-known or local behavior depending on device type supported by the subscription.
    • There is a courtesy period before the full lapse state matters operationally.
    • Configuration retention exists for a limited period, which supports recovery if renewal happens in time.