Kaspevo Labs is open for engagements
Mumbai, India
An engineering studio founded by engineers with experience in robotics startups, embedded Linux, custom hardware, AI and open-source systems.
Six domains, one system
Work our engineers did before this studio existed, each backed by a source.
Before Kaspevo Labs existed, our engineers were already contributing to open-source infrastructure, designing production electronics, bringing up embedded Linux platforms, and helping early-stage robotics and systems companies turn prototypes into products.
Kaspevo Labs is the natural next step — bringing those capabilities together into one engineering studio.
Four engineers who met while building robots.
Robotics control systems for an assistive-mobility platform.NishCorp Technologies
Ultra-wideband localization for autonomous vehicles operating where GPS is unreliable.Krishna Defence
Robotics and electronics on an early-stage robot.Eyecandy Robotics
Patches merged into the mainline Linux kernel.Linux Kernel
Board support upstreamed into Apache NuttX.Apache NuttX
Embedded Linux board bring-up on NXP i.MX95.Mecha
Formally verified, safety-critical RTOS across ARM64 and RISC-V.RedKill OS
LiDAR perception for Automotive Grade Linux, through Google Summer of Code.Google Summer of Code
Kaspevo Labs founded.
Every domain below is backed by work that shipped, was measured, or was merged upstream. Nothing here is a tool we have read about.
Robotics platforms carried from prototype toward production.
Board bring-up, BSP work, kernel debugging and upstream patches — what decides whether a board becomes a product.
Production boards: multilayer layout, power, battery management and mixed-signal design.
Bare-metal and RTOS firmware for products that ship, including certified ones.
Patches merged into the Linux kernel, Apache NuttX and the Linux Foundation ecosystem, under our own names.
Perception, control and navigation for machines that work outside a demo, including where GPS does not reach.
Work in progress, photographed where it happened — faults on screen and probes still attached.
Two of us were on the early team, both working across robotics and electronics — custom boards, power, autonomy and control, through to a robot people could walk up to.
Nine of them: upstream projects, mentorship programmes and the companies our engineers have worked inside.
Linux Kernel Mentorship Program
Our engineers have contributed to these organizations and open-source communities. Kaspevo Labs is a new studio; these are not client engagements.
Anyone can look up what we have merged, and our names are on it. It is the part of our record you do not have to take our word for.
Kaspevo Labs is a young studio and we would rather say so than imply otherwise. The experience behind it comes from production electronics, open-source infrastructure, embedded Linux platforms and robotics systems — places where failure has consequences.
Hardware, firmware, Linux and autonomy fail at their boundaries. That is where we are useful.
And the kernel log. And the schematic. Most integration bugs are already documented somewhere nobody looked.
Where a fix belongs in the project rather than in your tree, we send it there. It survives the engagement that paid for it.
Every number on this site has a source behind it. Where we don't have a figure, we don't invent one.
Four engineers, laid out as components.
Describe the failure, not the job spec. If we're the wrong team for it we'll tell you, and say who might be right.