Case Study

Avocado OS

Designing a Production-Ready Operating System for Secure, Scalable Edge Devices

Hero Image

01. Overview

An operating system built for modern device fleets

Before Avocado OS existed, the OS layer was an internal engineering artifact—functional but invisible, with no product identity, no brand, and no narrative that non-engineers could rally around. I helped transform it into a named, positioned, and market-ready product that became central to the company’s story.

Avocado OS is a purpose-built operating system designed to solve a critical gap in the embedded and edge-AI ecosystem: the lack of a

production-grade, secure, and reproducible OS foundation

for managing large, heterogeneous device fleets.

As AI workloads move from the cloud to physical devices, teams face increasing pressure to secure devices from first boot, customize the OS to specific hardware capabilities, and deploy updates safely at scale. Existing embedded Linux approaches are often fragmented, hand-rolled, and difficult to scale. Avocado OS was created to replace that fragility with intentional infrastructure.

Avocado OS serves as the foundation layer beneath Peridio, our firmware management platform—forming a cohesive ecosystem where the OS handles secure boot, monitoring, and lifecycle control, while Peridio manages deployment, versioning, and fleet operations.

Secure devices from first boot

Customize OS to specific hardware capabilities

Maintain long-term lifecycle control

Deploy updates safely at scale

Avocado OS Architecture Overview

02. My Role

Designing the OS as a product, not just a technical artifact

As Head of Design, my role went far beyond UI—I helped shape Avocado OS from an internal engineering layer into a branded, market-positioned product with a clear identity and narrative.

Product & Engineering

  • Embedded with engineering to understand kernel-level and boot-chain constraints

  • Defined how OS capabilities surface through tooling, workflows, and documentation

  • Designed system architecture diagrams and mental models for technical and non-technical audiences

  • Contributed to front-end tooling that interfaces with OS-level operations

Brand & Marketing

  • Named, branded, and positioned Avocado OS as a standalone product

  • Built automated asset-generation workflows so marketing could self-serve branded materials without design bottlenecks

  • Created curated JSON prompt libraries for AI image generation—enabling consistent, on-brand visuals at speed

  • Designed the full brand experience for in-person events: booth UI, live demo interfaces for robotics and computer vision, and presentation decks

  • Translated deeply technical OS capabilities into narratives for executives and investors

Leadership & Strategy

  • Aligned OS capabilities with real customer needs and long-term company strategy

  • Shaped investor materials that featured Avocado OS as a key differentiator

  • Supported the NVIDIA Partner Program application with OS-focused narrative and documentation

  • Operated as the bridge between engineering depth and business storytelling

03. Key Challenges

Turning embedded Linux into a scalable foundation

Challenge 1

Embedded Linux is powerful—but brittle

Most embedded systems rely on custom Yocto builds, ad-hoc security configurations, and one-off scripts maintained by a handful of engineers.

This creates long-term risk: upgrades are painful, knowledge doesn’t scale, and failures are hard to recover from.

Embedded Linux Complexity

Design Approach

  • Treat the OS as a lifecycle product, not a static image
  • Prioritize reproducibility, determinism, and security from day one

  • Design for ongoing control, not just initial deployment
Hardware Diversity

Challenge 2

Hardware diversity without fragmentation

Device fleets often include different SoCs, different peripherals, and different performance and security requirements.

Without careful abstraction, this leads to OS sprawl.

Design Approach

  • Enable custom OS builds per hardware profile
  • Maintain a consistent mental model across devices
  • Allow teams to exploit hardware capabilities without rewriting everything

Challenge 3

OS decisions are hard to communicate

OS-level work is often invisible to non-engineers, yet it has massive business implications—security posture, update reliability, hardware compatibility, and long-term maintenance costs all depend on it.

Without a clear way to explain what the OS does and why it matters, sales conversations stall, investors undervalue the technology, and internal alignment breaks down.

Communication Challenge

Design Approach

  • Translate OS capabilities into clear, outcome-driven language for every audience

  • Build automated workflows and curated AI prompt libraries so marketing could generate on-brand assets without design bottlenecks

  • Design live demo UIs for robotics and computer vision that made the OS tangible at industry events

  • Position Avocado OS as an enabler of reliability, security, and speed—not just “Linux underneath”

04. Process

Lightweight structure, deep collaboration

Avocado OS was developed alongside the broader platform using the same flexible, fast-moving startup process: quarterly strategic goals, weekly execution cycles, and continuous alignment with real customer requirements.

Design Perspective

  • Early concepts focused on what the OS enables, not how it’s implemented

  • Frequent collaboration with engineers ensured conceptual clarity

  • Iteration happened through conversation, diagrams, and prototypes—not heavy documentation

Feedback Sources

  • Internal engineering discussions
  • Direct customer conversations
  • Open-source and community signals
  • Partner feedback (including hardware vendors)

Tooling

Figma
Figjam
Linear
Cursor
Claude Code
Notion
Google Analytics

Events, Live Streams & Brand Experience

I owned the full live experience for Avocado OS and Peridio—from in-person conference booths to live-streamed demos—designing every touchpoint to tell a cohesive brand story across physical and digital channels.

Embedded World Summit — Germany & North America
Embedded Vision Summit
Open Source Summit
CES
Robotics & computer vision live demos
Live-streamed demos & webinars
Custom OBS scenes & transitions
Avocado OS website & brand system
And many more

For each event, I designed custom presentation decks, live demo interfaces tailored to the audience (robotics, computer vision, fleet management), and branded booth materials. For live streams, I built custom OBS scenes, transitions, and overlays—creating a broadcast-quality experience for remote audiences. I also designed and maintained the Avocado OS website and visual identity, ensuring a unified brand relationship between Avocado OS and Peridio across every channel.

05. Design & Product Principles

Infrastructure that stays out of the way

Security by default

Secure boot, encryption, and integrity are not optional add-ons.

Customization without chaos

Hardware-specific optimization without fragmenting the system.

Lifecycle over installation

The OS must support years of updates, not just day-one success.

Invisible reliability

The best OS is the one users don’t have to think about.

From a design standpoint, this meant focusing less on interfaces and more on mental models, predictable behaviors, and clear boundaries between OS, firmware, and application layers.

06. Business Impact

The foundation that makes the platform possible

Product

  • Enabled safe, controlled device boot and runtime management
  • Made advanced firmware workflows possible through Peridio integration

  • Reduced operational risk as fleets scale across diverse hardware

Go-to-Market & Fundraising

  • Gave sales a concrete “infrastructure story” that differentiated from competitors

  • Featured in investor materials as a key technical moat
  • Designed event demos and conference materials that drove partner interest

Ecosystem & Partnerships

  • Positioned the company as an OS-level platform, not just a tooling vendor

  • Avocado OS’s edge-AI compatibility was central to the NVIDIA Partner Program approval

  • Strengthened credibility with OEMs, silicon vendors, and enterprise customers

07. Outcomes & Learnings

What Worked

  • Transforming an internal engineering layer into a named, branded product

  • Close, continuous collaboration with engineering on kernel-level decisions

  • Framing OS capabilities in business-relevant terms for investors and partners

  • Using design as the bridge between deep tech and go-to-market

Lessons Learned

  • OS decisions compound over time—early design clarity prevents years of technical debt

  • Simplicity at the surface requires enormous rigor underneath
  • Infrastructure products succeed when trust is earned through reliability, not marketing

  • The best brand work starts with understanding the engineering, not just the market

“Giving an operating system a name, an identity, and a story turned it from invisible infrastructure into the company’s strongest strategic asset.”

Let's Connect

Whether you're building a product, scaling a design team, or exploring what great UX could unlock for your business — let's find out what's possible together.