A Project of Linux Foundation Networking

Intent-based network orchestration, built to close the loop.

Declarative configuration, YANG-modeled abstraction layers, and telemetry in one focused open-source platform.

StratoWeave is a platform for robust network orchestration systems based on model-driven declarative transforms. Build automation that makes sense for your network with reactive closed loops and observability powered by streaming telemetry.

Explore the live demo Understand the tech View the source
OSS/BSS Customer/CRM
NETCONF RESTCONF TMF640/641

Reactive from
the ground up.

StratoWeave is purely reactive. Configuration changes from northbound APIs and streaming telemetry from devices are input events that drive the platform. Desired state and observed state meet in the same orchestration system.

Its design draws on functional programming and a decade of experience automating large IP networks: compose small transformations, make intent explicit, and respond when inputs change.

Declare the whole lifecycle

A transform owns its configuration for as long as its intent exists. Describe the desired result; the platform handles updates and removal without separate create, update, and delete workflows.

Compose layers of abstraction

Turn a service order into network intent, then device configuration. Each layer hides implementation details, keeping service definitions stable across vendors and domains.

Close the loop at any layer

Transforms can subscribe to device or service state and expose their own operational view. Multi-stage transforms keep conditional procedures and migrations behind a declarative interface.

A complete ecosystem
for network orchestration.

Shared YANG models connect service intent, execution, collection, observability, and operator interfaces. Develop, test, and operate your orchestration logic within one consistent system throughout the service lifecycle.

Define your network in YANG

Choose the service layers, models, and device types in your system specification. Use IETF or vendor models, and add abstractions that match how you operate.

Catch errors before deployment

YANG models become Acton types, so the compiler can catch data and type errors in your transforms. Test orchestration end to end with simulated devices and networks.

Tools that understand your models

Get code completion and error checking in VS Code through Acton’s language server. Use netclics to convert existing CLI snippets into YANG-compliant Acton data for your transforms.

Any network, any device, any API.

Connect the systems above your network to the infrastructure below it. Adapters keep service logic declarative while handling the details of each device, cloud service, or external API.

Northbound to your OSS/BSS

Expose YANG-modeled services through NETCONF and RESTCONF. Map those models to TM Forum service catalogs, ordering, and activation interfaces.

  • NETCONF
  • RESTCONF
  • TMF633 / 640 / 641

Southbound to your network

Generate NETCONF adapters from device YANG modules. Extend the adapter framework for CLIs, REST APIs, and other interfaces, preserving a consistent contract for transforms. Adapters are developed and maintained in the open.

  • NETCONF
  • RESTCONF
  • gNMI
  • CLI
  • SNMP
  • REST APIs & more

Bring your existing
network along.

Decades of configuration do not disappear when you adopt automation. StratoWeave supports brownfield onboarding and gradual migration, alongside day-zero provisioning for new devices.

Start with a subset of services or devices. Keep existing scripts and OSS tools in use as you expand the platform’s ownership.

  • Discover existing intent

    Read the running configuration and reconstruct the services that would produce it, working from device-facing layers upward.

  • Validate in isolation

    Compare generated configuration with the existing network. Refine models and discovery logic before taking ownership.

  • Adopt at your own pace

    Configuration attribution distinguishes transform-owned elements from manually managed or externally managed ones, so StratoWeave manages the lifecycle of its own configuration.

One architecture, multiple domains, many use cases.

Build the models and transforms for your environment. The same layered, reactive architecture can support services that span technologies, vendors, and operational boundaries.

IP & optical transport

Model backbone routers, links, and optical resources as a connected service-provider network. Coordinate changes across transport layers.

L2 & L3 VPN services

Express customer connectivity as service intent. Decompose endpoints and policies into the configuration each participating device needs.

Datacenter automation

Bring fabric provisioning, tenant connectivity, and datacenter interconnect into one system, from device onboarding to service operations.

Your next network domain

Extend the ecosystem with models and adapters for cloud services, access networks, or your own APIs. Compose them with existing services.

Explore a working
service-provider orchestrator.

The Somewhat Realistic Service Provider Orchestrator is a complete, open-source reference implementation for IP transport and L3VPN orchestration.

Explore topology, service intent, configuration layers, and device changes. Then run the orchestrator against a Nokia SR Linux lab, modify its transforms, or fork it as the starting point for your own system.

Explore the demo View the source
  1. Service intentL3VPN service & customer sites
  2. Network abstractionRouters & backbone links
  3. Resource-facing servicesInterfaces, routing & VPN configuration
  4. Device configurationVendor YANG models & adapters

Help build the open
orchestration platform.

StratoWeave is a Linux Foundation Networking project, released under the BSD 3-Clause License. Contribute models, transforms, adapters, documentation, or experience from your network. Help shape the platform by putting it to work.

Join the community Contribute on GitHub