Today we're launching OAK 4 FFC, the first OAK Modular device built on OAK 4. OAK Modular is our lineup of board-level OAK devices that let you choose and place your own camera modules. OAK 4 FFC is a small vision computer with five FFC (flexible flat cable) camera ports. You choose the cameras, put them where your machine needs them, and run synchronized streams, stereo depth, and AI on the board itself.
Orders open today for the OAK 4 FFC Developer Kit and Barebone. Developer Kits begin shipping in November, and Barebone deliveries are scheduled for Q1 2027.
Why we built it
For years, some of our most interesting customers have bought our cameras and then taken them apart.
Drone teams strip the housings off OAK cameras to save grams. Humanoid companies build heads around our RVC2 FFC boards, then carry a separate computer to run them. Surgical robotics teams need cameras at a fixed working distance and spacing that no off-the-shelf depth camera ships with. The request behind all of it is the same: let us choose the sensors and decide where they go, and you handle everything underneath.
Until now, saying yes meant pointing them at a long list of parts. Building a custom perception system usually means a compute module, a carrier board, a capture card or deserializer, cameras from another vendor, and drivers pinned to a particular OS release. Then you write your own synchronization and calibration tooling. Only after all of that do you start on the application you actually care about.
OAK 4 FFC is our answer. The camera modules, compute, firmware, DepthAI, and setup tools come from one platform and are designed to work together. You still design the machine, but you no longer have to build the vision stack underneath it.
What it is
OAK 4 FFC is the OAK 4 SoM on a 70 x 53 mm carrier board. It's the same OAK 4 platform that runs every OAK 4 camera: a 6-core RVC4 processor with 52 total TOPS of compute, hardware stereo depth, Neural Depth, video encoding, and a Linux system you can deploy your own applications to. What's new is that the cameras are yours to arrange.
- Five camera ports. Every connected camera shares one RVC4 processor.
- Built to go into a robot. 2.5 Gigabit Ethernet, PoE+ through the module included in the Developer Kit, 6-32 V DC input straight from a battery, USB-C, CAN, an M8 aux connector with UART and frame sync, and an onboard IMU and magnetometer.
- Wide operating range. -20 to 50 °C.
- The same software as every OAK 4. DepthAI v3, OAK Viewer, and the model zoo work the same way they do on an OAK 4 D.
If you're on an RVC2 board like the OAK-FFC 4P today, this is its OAK 4 successor, and your robot no longer needs a separate host just to run the cameras. One note: OAK 4 FFC uses our V2 camera modules, so RVC2-era modules aren't supported.
Pick your cameras
At launch there are nine modules across three sensors:
- Sony IMX586: 48 MP color, rolling shutter. Autofocus, fixed focus, and wide versions. Good for high-resolution RGB and high-resolution stereo.
- OmniVision OV9282: 1 MP mono, global shutter. Standard and wide versions. Good for classic stereo depth.
- OmniVision OG05: 5 MP global shutter, in color and mono. Standard and wide versions of each. Good for sharp stereo and color on fast-moving machines.
Every module ships factory calibrated, with its lens parameters stored on the module itself. When you plug one in, the board reads that calibration directly.
Because the cameras share one processor, you're working with a total pixel budget rather than five independent cameras, so plan resolution and frame rate across the whole rig.
A build, start to finish
Here's what a first afternoon looks like for a humanoid head.
Choose and place the cameras. Two OG05 modules face forward as the eyes, about 6.5 cm apart, close to human spacing. A wide IMX586 sits on each side of the head and one faces the rear. That's five cameras on one board.
Measure and enter the geometry. Open OAK Viewer, and it detects each module and reads its factory calibration. You enter where each camera sits relative to the others: the baseline between the eyes, and the position and rough angle of the side and rear cameras. A 3D view shows the rig as you build it, so you can see that the cameras point where you meant them to.
Calibrate the cameras that overlap. Point the head at an ordinary textured scene and move it slowly. Dynamic Calibration uses what the overlapping cameras see in common to refine their alignment, with no ChArUco board involved. Viewer works out which cameras overlap and calibrates those groups. Any camera that shares no view with another keeps the position you entered.
Check the output. You now have five synchronized streams and stereo depth from the front pair, ready to view and record in Viewer or to use from a DepthAI pipeline.
To be clear about what that rig is: it gives your robot all-around awareness, with depth in front where the stereo pair is. It is not 360-degree depth, and it is not a single fused point cloud. Those need overlapping stereo coverage and fusion work that is outside this launch.
The same flow covers other layouts:
- a forward stereo pair with a color camera
- a vertical baseline
- two stereo pairs facing front and back, calibrated one pair at a time
- a ring of wide cameras for panoramic coverage
If the mount moves, run Dynamic Calibration again from OAK Viewer.
The main computer, or the perception system
OAK 4 FFC can play one of two roles on a machine.
It can be the main computer. On a stationary system or a simpler robot, such as an inspection station, a pick cell, or a small mobile platform, OAK 4 FFC can run the whole application. It's a full Linux computer, so the camera pipeline, your models, your logic, and the CAN or Ethernet link to the rest of the machine all live on one board.
Or it can be the perception system. On a complex robot with a Jetson or another central computer, OAK 4 FFC takes over vision. Stereo, encoding, neural networks, and classical computer vision all run on the board, and the main computer receives results: depth, detections, and tracked objects. That computer keeps its capacity for planning, manipulation, and the VLA and VLM models that get heavier every quarter.
The second role has a benefit beyond compute: your vision system becomes its own subsystem. You can add perception to an existing machine without rebuilding its compute architecture, upgrade the cameras and the host on separate schedules, and reuse the same vision setup across robots that run on different main computers.
Several views, one board
Building a five-view robot from standalone OAK cameras puts a processor at every viewpoint. Most robots don't need a full computer at every viewpoint. They need cameras at every viewpoint and enough compute for all of them. OAK 4 FFC gives you exactly that.
Developer Kit today, Barebone for production
The two versions share the same vision core and run the same application, so moving from one to the other changes the mechanics, not the software.
- OAK 4 FFC Developer Kit. The board and SoM come with a heatsink, an L-bracket, a PoE+ module, and panel-mount connectors, so it works on a desk the day it arrives. Ships starting in November.
- OAK 4 FFC Barebone. The board and SoM come with thermal interface material only, at 36 g. You provide the cooling, power, cabling, and enclosure for your own design. Orders open today, with deliveries scheduled for Q1 2027.
We're also releasing the OAK 4 FFC reference design as open source in our oak-hardware repository. If you outgrow our carrier, you can design your own around the OAK 4 SoM, starting from the one we ship.
What's next
Thermal, time-of-flight (ToF), and additional global shutter modules are coming soon. If you'd like details or prototype access, contact us at sales@luxonis.com
Over the coming weeks, we'll share full builds: an underwater camera, a humanoid robot head, and a drone, each with video, a parts list, and step-by-step instructions. We'll also post a closer look at multi-camera calibration.
Get started
Orders open today for the OAK 4 FFC Developer Kit at $849 and the Barebone at $729. Both prices include a temporary $200 surcharge for memory and storage. Camera modules are sold separately, starting at $39.99, and can be added to the same order.
If you're designing OAK 4 FFC into a product, talk to us. We'd like to hear what you're building and help you get from a Developer Kit on the bench to a fleet. Email cj.mann@luxonis.com.
Tell us what you build. We can't wait to see what goes on the front of it.
Links
