Add modules as the site grows.
Know when to order the next one.

Modular data centers add capacity one module at a time. Aravolta monitoring grows the same way, from a single pilot module to hundreds of production units. The load it measures tells you when to order the next module.

Live demo
Sample data. At onboarding we build the plan from your module ratings, lead times, and metered IT load.
Site 14 / Capacity plan
IT load 196.0 kW · updated --:--:--
Modules1 live · 0 planned · 2 open · 250 kW rated each
  • 40 ftReporting
    196.0 kW78%
  • 40 ftWaiting
    -- kW--
  • 40 ftWaiting
    -- kW--
  • 40 ftWaiting
    -- kW--
  • Monthly peak IT load
  • Forecast
  • Forecast range
  • Usable capacity, 80% of rated
  • Short of capacity

Hover or tap the chart for any month. Change an input or add a module, and both dates move with it.

Capacity planning

Plan the next module from measured data

Each module reports its own load, so the forecast starts from what the site draws today. Here is how the two dates are set.

Worked exampleSite 14
Usable
Modules × rated kW × your planning threshold4 × 250 kW × 80% = 800 kW
Growth
The measured trend of the monthly peak, or a rate you set25 kW a month
Runs out
The first month the forecast peak reaches usable capacityJul 2027
Order by
The run-out month, minus the module lead timeJul 2027 minus 6 months = Jan 2027
Utilization
  • Live utilization for every module
  • Growth trends and seasonality
  • Power, cooling, and space capacity
  • IT equipment density and efficiency
Forecasting
  • ML-based demand forecasts
  • Estimated date capacity runs out
  • What-if scenarios
  • When to order the next module
Financial planning
  • Cost per kW and cost per rack
  • ROI on each capacity addition
  • TCO models for different growth plans
  • Budget and capital forecasts
Adding capacity

One module at a time

Start with one module. Add the rest without rebuilding the monitoring. You pay for what you use, and there is no per-point charge.

Phased rolloutSmall steps, small risk
  1. Phase 1

    Pilot on one module

    The node finds the module's equipment on the network and starts reporting.

  2. Template saved
    Phase 2

    Refine on the pilot before scaling

    Tune the dashboards and alert thresholds, then save them as the template.

  3. Phase 3

    Add modules once the pilot shows ROI

    Each new node ships pre-configured and reports when its module powers on.

Module by module
  • Add modules as demand grows
  • Mix module types (compute, storage, networking)
  • Upgrade modules independently, without downtime
  • Retire modules that sit idle
One management layer
  • One dashboard for every module
  • Site-wide capacity totals and forecasts
  • Workload balancing across modules
  • Same policies and configuration on every module
Multi-tenant

Lease modules to tenants

Give a tenant its own module or a share of one. Each tenant's power is metered, space and cooling costs are split by tenant, and the totals export to your billing system.

Site 14 / Tenant usage
Month to date
TenantPeak / contract
Tenant 03Near limit
Dedicated · MOD-01 · 12 racks
203.4 / 220 kW
Tenant 07Within
Dedicated · MOD-02 · 12 racks
194.0 / 220 kW
Tenant 11Within
Shared · MOD-03 · 5 racks
61.8 / 70 kW
Tenant 14Over
Shared · MOD-03 · 4 racks
63.1 / 60 kW
Tenant 18Within
Shared · MOD-03 · 3 racks
21.4 / 40 kW
Tenant 21Within
Shared · MOD-04 · 4 racks
55.9 / 100 kW
Metered power per tenant, with space and coolingExport to your billing system
Tenant models
  • A dedicated module per tenant
  • Shared modules with logical isolation
  • Per-tenant quotas and limits
  • SLAs and billing terms per tenant
Tenant self-service
  • A portal for each tenant
  • Live usage visible to the tenant
  • Alerts the tenant sets up
  • Reports the tenant defines
Usage-based billing
  • Automatic metering per tenant
  • Billing on metered power
  • Space and cooling costs per tenant
  • Export to your billing system
Customer portal
Refresh and upgrades

Replace modules in stages, not all at once

Old and new generations run side by side while each module is swapped. Every module's age and end of life stay in view.

Site 3 / Fleet age
Sample data
  • Gen 1 in service
  • Gen 2 in service
  • Design life left
  • Planned
  • End of life within 12 months
Module
2018202220262030
MOD-01
Gen 1 · 200 kW
Retired
In service Dec 2016 to Aug 2026, replaced by MOD-06.
MOD-02
Gen 1 · 200 kW
EOL Mar 2027
In service since Jun 2017, end of life Mar 2027, swap to MOD-07 planned.
MOD-03
Gen 1 · 200 kW
EOL May 2028
In service since May 2018, end of life May 2028.
MOD-04
Gen 1 · 200 kW
EOL Nov 2028
In service since Nov 2018, end of life Nov 2028.
MOD-05
Gen 2 · 250 kW
EOL Dec 2033
In service since Dec 2023, end of life Dec 2033.
MOD-06
Gen 2 · 250 kW
EOL May 2036
In service since May 2026, end of life May 2036, replaced MOD-01.
MOD-07
Gen 2 · 250 kW
EOL Jan 2037
Planned, live Jan 2027, end of life Jan 2037, replaces MOD-02.
Gen 1 · 200 kW rated
3 in service · PUE 1.46
Gen 2 · 250 kW rated
2 in service + 1 planned · PUE 1.27
Rolling upgrades
  • Replace older modules one at a time
  • Service stays up during the swap
  • Old and new generations run side by side
  • A staged refresh plan
Fleet age tracking
  • Age and end-of-life status per module
  • Which generation each module runs
  • Performance compared across generations
  • ROI on each replacement
New regions

The same setup in the next region

Repeat a proven design in a new market. The template brings its dashboards and alert thresholds, and every site joins the same fleet view.

Sites
100+
Countries
8

Aravolta runs at more than 100 sites in 8 countries, on premises, air-gapped, or in the cloud.

Multi-site rollout
  • Repeat a proven design in a new market
  • One standard configuration across regions
  • Local compliance requirements per region
  • Capacity balancing between regions
Global view
  • Every site on one dashboard
  • Region-to-region performance comparison
  • Workload migration between regions
  • Disaster recovery across regions
Automation
  • API for automation and orchestration
  • Infrastructure as Code (IaC) support
  • CI/CD for configuration management
  • Auto-scaling and dynamic resource allocation
  • Kubernetes and container orchestration support

Start with one module

Put Aravolta on the pilot module. When the next ones arrive, they join the same platform.