Skip to main content

AerFlex - FAQ

Frequently asked questions

Team Celona avatar
Written by Team Celona
Updated this week

What is Celona AerFlex?

Celona AerFlex is the industry’s first cloud-controlled, access point-only (AP-only) private 5G architecture. It eliminates the need for on-site servers and complex network infrastructure, making private 5G as easy to deploy as Wi-Fi. Purpose-built for distributed enterprises and industrial environments, AerFlex combines the simplicity of cloud with the performance and security of cellular.

How is AerFlex different from traditional private 5G solutions?

Most private 5G solutions require complex, on-premises infrastructure—including servers, network appliances, and specialized cabling. Celona AerFlex simplifies this model with:

  • AP-only deployments: No servers or racks required on site

  • Cloud-native orchestration: Control-plane functions managed centrally in the cloud

  • Local data breakout: Ensures low latency, privacy, and data sovereignty

  • Zero-touch provisioning: New sites can be live in hours, not weeks

What problems does AerFlex solve?

AerFlex addresses key challenges for enterprise wireless networks:

  • Lack of IT staff at remote or space-constrained sites

  • High deployment and operational costs of traditional private 5G

  • Limited scalability and complexity of telco-style solutions

  • Inadequate performance of Wi-Fi for industrial AI and automation

What is the "Smart Split" architecture?

AerFlex uses a "Smart Split" model:

  • Data path services run on the AP: Critical functions like packet forwarding and segmentation are handled locally for optimal performance.

  • Control path services run in the cloud: Mobility, policy, and configuration management are handled centrally via Celona Cloud.

This architecture ensures high performance, compliance, and resiliency across distributed sites.

What hardware is required to deploy AerFlex?

Only Celona AP2x Series access points (e.g., AP20, AP21, AP22) are needed at the site. No servers, appliances, or special IT closets are required. These APs handle local breakout and integrate directly with enterprise IT and OT systems.

Note: Access points must be time-synchronized for proper operation. This can be achieved via an external GPS antenna or a PTP grandmaster clock on the local network.

What kind of environments is AerFlex designed for?

AerFlex is ideal for:

  • Retail chains and branch offices

  • Warehouses and distribution centers

  • Remote manufacturing sites

  • Food and beverage plants

  • Offshore oil rigs

  • Space-constrained or unmanned locations

Is AerFlex secure?

Yes. AerFlex combines:

  • Local data breakout to ensure that data never leaves the site unnecessarily

  • Cloud-based policy control for centralized visibility and configuration

  • End-to-end encryption for all management and user data traffic

How is AerFlex managed?

Celona AerFlex is managed through Celona Orchestrator, a cloud-based platform that:

  • Provides real-time network and device visibility

  • Enables centralized configuration and updates

  • Supports integration with enterprise tools via APIs

How is AerFlex licensed and priced?

AerFlex is offered as an add-on to Celona’s existing private 5G subscription model:

  • Priced per Access Point

  • Available in 3- or 5-year terms

  • Indoor and outdoor APs supported under the same model
    Existing Celona customers can easily upgrade to AerFlex via a simple software configuration.

Are Edge appliance-based deployments still supported with AerFlex?

Yes. Celona continues to fully support Edge appliance-based deployments alongside AerFlex.

AerFlex introduces a new, AP-only option designed for distributed and space-constrained sites, but it does not replace other deployment models. Enterprises can select the best-fit architecture for each site, while maintaining centralized management through Celona Orchestrator.

Deployment Model

Description

Ideal Use Case

AerFlex

AP-only, cloud-controlled with local data breakout

Remote, space-constrained, or IT-light sites

Virtualized Edge

Celona Edge software on VMware infrastructure

Campuses, headquarters, or sites with existing virtualization

Edge Appliance

Rack-mounted 1U Edge appliance deployed on-prem

Campuses & deployments with mobility-intensive environments

All models work together seamlessly, allowing hybrid deployments across your enterprise.

Are there any use cases where AerFlex should not be used?

Yes. While AerFlex is ideal for many distributed or remote enterprise sites, there are specific scenarios where a Celona Edge-based deployment is better suited.

Use Case

Reason

High-speed mobility (e.g., AGVs, robotics)

Cloud-based control plane may introduce latency that impacts seamless handovers

Air-gapped or isolated environments

Requires a fully local packet core; AerFlex depends on cloud connectivity

Complex legacy LAN/OT integrations

On-site Edge deployments offer greater control for deep integration

Sites with unstable or non-redundant WAN

AerFlex’s cloud-managed control plane requires a stable, redundant WAN for optimal performance

For these scenarios, Celona’s Appliance or Virtualized Edge deployment models offer greater control, local autonomy, and integration flexibility.

Is handover supported on AerFlex?

Yes. AerFlex supports intra-site mobility and handovers between Celona APs, maintaining session continuity for typical enterprise use (handhelds, scanners, tablets, low-speed vehicles).

What to expect

  • Designed for pedestrian/low-speed mobility. Because AerFlex’s control plane runs in the cloud, handover performance depends on WAN latency and stability.

  • High-speed mobility: For fast, latency-sensitive handovers (e.g., AGVs/AMRs, robotics in motion), choose a Celona Edge deployment (appliance or virtualized) where the control plane is local.

Deployment

Mobility/Handover

Notes

AerFlex (AP-only)

Supported for pedestrian/low-speed mobility

Requires stable, redundant WAN since the control plane is cloud-based

Edge (appliance/virtualized)

Optimized for high-speed mobility

Local control plane minimizes handover latency

Is there an upper limit on the number of APs supported in an AerFlex deployment?

AerFlex does not impose a hard limit on the number of access points, and its cloud-controlled architecture is designed to scale across distributed enterprise sites. However, there are important design considerations to ensure reliable operation at scale:

Factor

Guidance

Architecture

AerFlex scales horizontally—add more APs as needed across sites

Subnet Requirement

All APs within a site must reside on the same Layer 2 subnet

Time Synchronization

APs require accurate time sync via GPS antenna or PTP grandmaster

WAN Dependency

A stable and redundant WAN connection is critical for control plane access

RF Design

Ensure proper channel planning and AP overlap to support seamless mobility

Why is AerFlex unique, and how is it different from other cloud-based private 5G solutions?

Celona AerFlex is the industry’s first true AP-only, cloud-controlled private 5G architecture, purpose-built for enterprise use—not retrofitted from telco infrastructure.

Here’s how it stands out from other so-called “cloud-based” private 5G solutions:

Feature

AerFlex

Other Cloud-Based Solutions

Architecture

AP-only, no on-site appliances or servers

Often require on-prem cores, edge gateways, or hybrid setups

Cloud Control Plane

True cloud-native control with dynamic scaling via Celona Cloud

Often “lift-and-shift” legacy core moved to the cloud

Local Data Breakout

Handled directly at the AP for low latency and compliance

Traffic often hairpinned through centralized cloud core

Time to Deploy

Hours—zero-touch AP provisioning

Days/weeks due to more complex integration

Vertical Integration

Single software stack (CelonaOS, Orchestrator, Cloud)

Multi-vendor systems with fragmented components

Enterprise-First Design

Native support for enterprise IT/OT systems

Often requires telco expertise and additional integration layers

Management & Orchestration

Centralized via Celona Orchestrator with API & policy control

Disjointed interfaces across RAN/core/gateway components

Did this answer your question?