An OpenDaylight feature set for programmers & solution architects—without the Karaf overhead. Faster boot, lower memory, full modularity.
lighty.io is a Software Development Kit powered by OpenDaylight to support, ease & accelerate the development of Software-Defined Networking (SDN) solutions in Java. Developed by PANTHEON.tech.
It utilizes core OpenDaylight components, available as a set of libraries adapted to run in a plain Java SE environment—no OSGi, no Karaf, no container overhead.
The result: faster startup, lower memory footprint, and the freedom to use any Java framework you choose alongside your SDN controller logic.
View on GitHub ↗Six component categories cover the full lifecycle—from device simulation and southbound connectivity to UI visibility and Docker deployments.
The core controller assembly layer. Includes MD-SAL, YANG Tools, and the OpenDaylight Controller—everything needed to build a fully functioning SDN controller.
For Controller AssemblyClient libraries for Java, Python, and Go that let external applications talk to your lighty.io controller with minimal effort.
For Easy IntegrationPre-built UI and visualization tools that make your network topology and data observable. Faster path from data to insight for your operations team.
For Faster VisualizationsSimulate NETCONF and other devices for integration testing without physical hardware. All OpenDaylight services run in the JUnit runtime too.
For Better Integration TestingReady-to-run reference applications covering common SDN patterns. Clone, explore, and adapt them as a jump-start for your own controller development.
For Development JumpstartOfficial container images for every major lighty.io module. Deploy instantly to any container orchestration platform with a single pull command.
For Faster Deploymentslighty.io ships a core module and a rich set of optional plugins. Your application code starts, stops & restarts modules as required — mix and match exactly what you need.
The foundational module that boots OpenDaylight services in a plain Java SE environment. Provides the shared service registry all other modules depend on.
Expose your controller's data and operations to management applications via standard northbound APIs.
Connect your controller to real or simulated network devices using industry-standard southbound protocols.
Full application modules that run on top of lighty-core, migrated from their original OpenDaylight Karaf deployments.
Interact with a running lighty.io controller from any external application, regardless of language.
Build your own NETCONF devices using your own YANG models. Ideal for simulators, test harnesses, and custom southbound stubs.
Drop the heavy runtime. lighty.io boots faster and consumes less memory than a standard OpenDaylight distribution.
Plain Java SE means Spring Boot, Quarkus, Micronaut—whatever fits your team's stack. No lock-in.
Start, stop, and restart individual modules at runtime. Ship only what you need; add more as requirements grow.
All OpenDaylight services are available inside the JUnit runtime, making full unit testing of your SDN logic straightforward.
Deploy to lighty.io and standard OpenDaylight simultaneously. Migrate at your own pace, risk-free.
// Bootstrap a lighty controller in plain Java var config = LightyControllerBuilder .from(configJson) .build(); var controller = new LightyController(config); controller.start().get(); // Add RESTCONF northbound var restconf = new RestConfServer( controller.getServices() ); restconf.start().get(); // Add NETCONF southbound var netconf = new NetconfTopologyPlugin( controller.getServices() ); netconf.start().get(); // Done — your SDN controller is running.
See full examples in the GitHub repository ↗
Explore how lighty.io integrates with modern networking stacks, open-source platforms, and protocols.
Automate SONiC switch configuration using lighty.io's gNMI southbound plugin. Includes RESTCONF vs gNMI benchmark data with up to 92 ACL/s throughput.
Read more → Integration · OpenFlowStep-by-step guide to integrating any OpenDaylight project into lighty.io, using the OpenFlow southbound plugin as a worked example.
Read more → Security · AAAAdd password-protected users, roles, domains and fine-grained REST path policies to your lighty.io SDN controller with the AAA module.
Read more → Migration · ONAPMigration of ONAP's SDN-C from vanilla OpenDaylight to lighty.io cut initialization time from 388s to 147s and RAM usage by more than half.
Read more → Southbound · OpenFlowConnect OpenFlow-capable switches to a lighty.io controller, post flows via RESTCONF, and verify device state — complete with Mininet walkthrough.
Read more → Migration · TransportPCEHow to migrate an OpenDaylight application to lighty.io by removing OSGi/Karaf hard dependencies — using TransportPCE as a practical guide.
Read more → Development · YANGModel an RPC in YANG, generate Java classes with Maven, and expose it over HTTP using lighty.io's Codecs component for JSON serialization.
Read more → Migration · ONAPThe technical deep-dive into migrating ONAP SDN-C: blueprint analysis, initProcedure implementation, and shutdown handling in lighty.io.
Read more →No. lighty.io repackages OpenDaylight components to run without Karaf. We are proud OpenDaylight supporters and among the project's largest contributors.
Karaf starts OpenDaylight features inside an OSGi runtime. lighty.io does this faster with better memory efficiency, and frees you to use any Java SE framework alongside it.
Yes. Since 7.x: YANG Codecs for JSON/XML serialization, NETCONF Device Library for custom devices, and client libs for Java, Python & Go.
Yes. lighty.io provides OpenDaylight services at runtime and your application code does not depend on Karaf—so both can coexist during migration.
Prepared migration guides are available for OpenDaylight TransportPCE and ONAP SDN-C. Custom migration scenarios available through our commercial offering.
Yes. One core module, plus optional Southbound & Northbound plugins. Your application starts, stops, and restarts modules as required at runtime.
Much easier than with standard ODL—all OpenDaylight services are available in the JUnit runtime, so you write regular unit tests against the real services.
Explore release notes, clone the samples, or reach out for a commercial solution with professional support from PANTHEON.tech.