SCENIC: Stream Computation-Enhanced SmartNIC
An open-source SmartNIC design hits 200Gbps with full Linux compatibility — but commercial adoption remains unproven.

The Thesis
SmartNICs — network cards with onboard processors that offload work from the main CPU — sit at the center of modern AI datacenter infrastructure. Today's commercial options (from vendors like Nvidia's BlueField or Marvell's Octeon) offer high bandwidth and software compatibility but are difficult to customize. Research alternatives are usually the opposite: highly programmable but too slow or too incompatible to deploy. SCENIC proposes a third path: treat the NIC's data pipeline as a programmable computing substrate, co-designed with software from the ground up, at full commercial speeds. The catch is that SCENIC is an FPGA-based research prototype, not a shipping product, and the gap between an academic demonstration and a production datacenter deployment is substantial.
Catalyst
AI workloads — particularly distributed training and inference — have made in-network computing a priority, creating demand that neither pure software stacks nor inflexible commercial ASICs fully satisfy. The maturation of high-density FPGAs capable of 200G line-rate processing, combined with standardized RDMA (Remote Direct Memory Access, a method for one machine to read or write another's memory without CPU involvement) interfaces, makes a research prototype at this bandwidth tier feasible today. Open-source hardware toolchains such as Corundum (an open FPGA NIC framework) also lowered the barrier to building a full, OS-integrated network stack.
What's New
Prior research SmartNICs — systems like ClickNP, iPipe, and StRoM — demonstrated programmable in-network processing but typically operated at 10–40G speeds and required custom, non-standard driver interfaces that broke compatibility with ordinary Linux applications. Commercial SmartNICs such as Nvidia's BlueField-3 offer full OS integration and 200G bandwidth but expose only a fixed processing pipeline with limited user customization. SCENIC's claimed advance is delivering both: 200G throughput with offloaded TCP/IP and RDMA, full native Linux and RDMA verb compatibility, and a programmable stream compute layer that sits directly on the data path without requiring application changes.
The Counter
The paper's central claim — that a single open design can match commercial SmartNICs on bandwidth while also being freely customizable — is exactly what every research SmartNIC paper has claimed for a decade. The 200G numbers are real, but they come from an FPGA running at a fraction of the clock speed and a fraction of the density of a production ASIC; the comparison to commercial platforms is therefore somewhat misleading. Nvidia's BlueField and Marvell's Octeon are not just network chips — they are bundled with years of driver hardening, vendor support contracts, and deep integration with hyperscaler software stacks that a fresh open-source project cannot replicate. The use cases demonstrated (collective communication offload, network-to-GPU partitioning) are compelling AI-datacenter scenarios, but they are also exactly the scenarios Nvidia already addresses with its SHARP in-network computing technology on InfiniBand. Perhaps most importantly, the SmartNIC market has repeatedly shown that hyperscalers — the only buyers at scale — prefer to design their own silicon (Google's custom NICs, Microsoft's Catapult/Azure FPGA program) rather than adopt external open designs, which limits the realistic deployment surface for a project like SCENIC.
Longs
None listed.
Shorts
- Nvidia BlueField SmartNIC division: if open, customizable alternatives reach comparable bandwidth and software compatibility, the proprietary lock-in argument weakens.
- Marvell OCTEON SmartNIC line: similarly positioned as a closed, high-performance offload platform whose differentiation rests on integration complexity that SCENIC aims to reduce.
- Incumbent CPU-only server vendors: wider SmartNIC adoption of the SCENIC model accelerates the trend of moving network and storage processing off the main CPU, reducing per-socket value.
Enablers (Picks & Shovels)
- Corundum open-source FPGA NIC framework
- Xilinx/AMD Alveo FPGA platform used as the hardware substrate
- RoCE (RDMA over Converged Ethernet) ecosystem and its driver stack
- Open-source P4 and HLS toolchains for programmable packet processing
Private Watchlist
- Pensando Systems (now part of AMD, but spin-out activity possible)
- Fungible (acquired by Microsoft, but the architectural ideas are live in competitors)
- Enfabrica
- xsight labs
The Paper
Although modern, AI-centric datacenters heavily rely on SmartNICs, existing devices impose a hard trade-off. Commercial SmartNICs provide high bandwidth and easy software integration, but offer limited support for customization and data processing offload. In contrast, research SmartNICs often suffer from low bandwidth, limited functionality, and poor software compatibility -- to the point that many are not actual NICs in a technical sense. This gap can be closed by treating the NIC datapath as a first-class stream computation substrate with shared hardware/software abstractions for a tight co-design of infrastructure and applications. To demonstrate this, we introduce SCENIC, an open-source datacenter SmartNIC. SCENIC implements a 200G network datapath over offloaded TCP/IP and RDMA stacks, as well as a fallback path for processing arbitrary network traffic. On top of the network logic, SCENIC combines on-datapath Stream Compute Units (SCUs) for data processing and embedded ARM cores for flexible control path manipulation with direct access to GPUs and SSDs. SCENIC is fully integrated with the OS, exposing native Linux network and RDMA verb interfaces, making the programmable datapath transparent to existing applications while enabling control of, e.g., user-defined offloads and programmable congestion control. SCENIC's performance matches commercial platforms, and we show its versatility through several use cases such as offloaded collective communication and network-to-GPU hash-based data partitioning.