Digital Rebar Pricing
Pricing for the RackN Digital Rebar is primarily based on four factors:
- Virtual infrastructure units track the maximum number of machines managed at one time.
- Physical infrastructure units track per unique instances managed during the billing cycle.
- Support Tier, Retail or Enterprise, allow users to choose the level of RackN availability needed
- Feature Tiers, Pro to Enterprise, provide discounts for users who do not need advanced feature
For most tiers, users may also choose activity-based (monthly) or pre-allocated (annual) pricing.
For trial, RackN offers a free 20 machine 30-day self-trial using the Business license. Additional time and feature access during a trial is available on request.
We have partner programs for service providers, systems integrators (SIs), independent software vendors (ISVs) and consulting partners. Find what best fits you in the charts below, and contact us for more details.
|For serving just a single site managed by a single user||For team with multiple sites that is capable of self-support.||For teams with production support requirements.||For advanced production workloads with Enterprise integration requirements|
|Retail Support||Retail Support
with Paid Escalation
M-F 8-6 CT
M-F 8-6 CT
24×7 Support (50% premium)
|Pro Entitlements plus:
Named User Accounts
|Team Entitlements plus:
|Business Entitlements plus:
Isolated mode (airgap)
|Professional Services||Professional Services|
|Not Available||Daily Rates||Daily and Annual Rates|
|Per Physical Entity||Per Physical Entity|
|Per Virtual Entity||Per Virtual Entity|
|Maximum Combined Entitles||Maximum Combined Entities|
|Minimum Fee||Minimum Fee|
No Monthly Option
|Scale Discounts||Scale Discounts|
|Not Available||Scale pricing starts at 100 and extends to 100,000 units|
RackN licenses Physical Entities as unique systems that are persistent over time. Virtual Entities are not tracked as unique or persistent systems; instead, the total number of possible Virtual Entities is licensed to allow for the ephemeral nature of these systems. This distinction reflects the anticipated use of each resource type. Contact RackN for additional details.