Now in private beta

Build rApps without writing code.

RAN Flow is a visual, no-code platform for building O-RAN rApps. Drag functional blocks onto a canvas to create automated workflows that monitor KPMs, evaluate conditions, and push A1 policies — in minutes, not months.

Works with the O-RAN ecosystem

O-RAN Alliance
BubbleRAN
Ericsson EIAP
Nokia MantaRay
THE PROBLEM

Two worlds that don't speak the same language.

Telecom engineers understand the RAN. Software engineers understand code. Building an rApp today requires both — and neither has the right tools.

The RAN Engineer

I know exactly what policy to push, but I can't write the code to do it.

Strengths

  • Understands KPM thresholds
  • Knows A1 policy parameters
  • Can design optimization logic

Friction

  • No Python/Go experience
  • Can't navigate SDK docs
  • Blocked by dev team backlog

RAN Flow

bridges the gap

The Software Engineer

I can build the pipeline, but I don't know what values to set.

Strengths

  • Can write production code
  • Understands API integration
  • Can deploy to Kubernetes

Friction

  • No telecom domain knowledge
  • Guesses at KPI thresholds
  • Weeks of back-and-forth with RAN team
HOW IT WORKS

From idea to running rApp in three steps.

01

Drag & connect blocks

Choose from triggers, data readers, logic gates, and actions. Connect them on a visual canvas to define your workflow — no syntax to learn.

02

Configure with domain terms

Set thresholds in terms you already know: PRB utilization, throughput targets, cell IDs. RAN Flow translates these into the right API calls.

03

Test, then deploy

Dry-run your workflow against mock data to verify logic. When ready, deploy it as a persistent rApp on your Non-RT RIC with one click.

CAPABILITIES

Everything you need to ship rApps faster.

Visual Canvas Editor

Drag-and-drop workflow builder with 9 node types across 4 categories. See your rApp logic at a glance.

Real-Time KPM Monitoring

Connect to live metrics — throughput, PRB usage, latency — and trigger actions when thresholds are crossed.

A1 Policy Automation

Push SLA and load-balancing policies to the Near-RT RIC via the A1 interface. Guard rails built in.

Condition Logic & Branching

If/else branching with true and false output paths. Build complex decision trees without code.

One-Click Deploy

Deploy workflows as persistent background rApps. Full lifecycle management: start, pause, stop.

Dry Run & Validation

Test workflows against mock RAN data before touching production. Catch misconfigurations early.

ARCHITECTURE

Where RAN Flow fits.

RAN Flow sits above the Non-RT RIC. It translates visual workflows into rApp logic, pushes A1 policies down the stack, and collects KPM metrics flowing up from the gNB.

RAN Flow (Your Platform)
R1 Interface
Non-RT RIC (EIAP / MantaRay)
A1 Interface
Near-RT RIC
E2 Interface
gNB (5G Base Station)
COMPARISON

A better way to build rApps.

Legacy Approach

  • Time to first rAppDays to weeks
  • Required skillsPython, K8s, SDK
  • ValidationManual + trial/error
  • Multi-vendorVendor-locked
  • MaintenanceRe-code per platform
  • Dry Run / TestingNo simulation

RAN Flow

  • Time to first rAppUnder 1 hour
  • Required skillsRAN domain knowledge only
  • ValidationAutomated, 8-rule validator
  • Multi-vendorEIAP + MantaRay + O-RAN SC
  • MaintenanceUpdate once, deploy anywhere
  • Dry Run / TestingFull dry-run before deploy

Ready to build your first rApp?

Join the private beta. We onboard new teams every two weeks.