Dear Axiometa GENESIS backers,

Thank you to everyone who responded to our last update about the Genesis design. Your feedback has been invaluable as we finalize the platform.

Our Original Mission

When we launched Genesis, we set out to do two things:

1. Create a truly modular prototyping system
2. Introduce the AX22 protocol, a new breadboard compatible module standard

That mission hasn’t changed. What has changed is our understanding of how to best achieve it.

Why We’re Moving to an Integrated Design

When we first designed Genesis with a plug-in ESP32 controller, the idea was flexibility swap out the MCU for an RP2040, STM32, or whatever you needed. On paper, it sounded perfect. In practice, after extensive testing and development, we discovered it creates more problems than it solves.

Here’s what we learned:

The Pluggable Concept Fails on Multiple Levels

• Each AX22 port requires eight specific pin types: five communication pins (SPI + I2C), three flexible GPIOs (one must be ADC-capable), plus power and ground
• For eight ports, you need at minimum: eight ADC-capable pins, 24 GPIOs, and shared communication buses
• The RP2040 has only three ADC pins total, meaning only three of the eight AX22 ports could support analog modules
• The ESP32-S3 has pin count and capabilities most other MCUs simply don't

Pin Numbering Chaos

• What's "Pin 5" on an ESP32 might be "Pin 12" on an RP2040 and "PA3" on an STM32
• Each different MCU would need completely different pin definitions, libraries, and example code
• We'd be maintaining three or four separate codebases instead of one well-supported platform

Physical Constraints

• The pluggable MCU board has to be a specific physical size to fit the Genesis socket
• One can't just plug in any dev board; it must be custom designed for Genesis
• At that point, half the pins would be unused or non-functional anyway

The Economics Don’t Work

• After two years of lab use, we've never once removed the ESP32
• When a Genesis unit failed, replacing just the ESP32-S3 module (with its complex power routing) costs nearly the same as a completely new Genesis
• There's no actual cost savings from replaceability

Power Management Issues

Using Genesis in our own lab revealed serious power delivery problems with the plug-in design.
In the pluggable version, power takes a convoluted path: USB-C → MCU module → Genesis base → buck-boost converter → back to Genesis

This causes:

• Voltage drops across multiple connectors
• Brownouts during high current operations
• No appropriate placement for decoupling capacitors where they matter most

The Integrated Design Fixes All of This

• Capacitors placed directly next to the ESP32 for clean power
• Wider, shorter power traces with lower resistance
• Ideal diode ORing for seamless switching between USB and battery
• Integrated buck-boost converter in the optimal position
• Proper LiPo charging management all on one optimized board

Long-Term Software Support

We want Genesis to have official, maintained support in Arduino and Python for years to come.

Supporting multiple MCU variants would mean:

• Different pin mappings for each platform
• Separate libraries and examples for ESP32, RP2040, STM32, etc.
• Fractured documentation and growing incompatibility
• Our limited development time split across multiple platforms instead of making one great platform.

We can’t provide the quality support you deserve while maintaining multiple variants. It is better to have one well-documented, actively supported platform than several half-maintained ones.

The Real Path to Modularity

Here’s the key insight: true modularity comes from the AX22 protocol, not from swapping the main controller. If you want to use STM32 or RP2040, or any other MCU with AX22 modules, the appropriate approach is not to redesign the Genesis controller board. That will always lead to mismatched pins, incorrect silkscreen, disabled charging, and fewer usable ports.

A better path is to build your own MCU board and simply include AX22 ports. This preserves your preferred tool chain, keeps the hardware predictable, and lets you use the entire AX22 ecosystem exactly as intended.

What This Means for Genesis

• Integrated ESP32-S3 on a single, optimized board
• Smaller, more robust form factor that's easier to handle
• Better power management with proper battery charging
• Full long-term software support in Arduino and Python
• The AX22 protocol remains fully open and will continue expanding

We’re not reducing modularity, we’re focusing it where it actually matters. We’ll continue growing our library of AX22 modules and we plan to release dedicated breakout boards for other MCU platforms in the future. This way, the same AX22 ecosystem works everywhere, not just with Genesis.

Feedback Results

Out of our 100+ backers, we received responses from about four people who strongly preferred the pluggable version. We’ll be reaching out to each of you personally to discuss your specific use case and ensure Genesis still meets your needs.

Moving Forward

With this change, we can focus on shipping a single, well-supported platform that we can properly document, update, and improve for years to come. Production remains on track for our January 2026 delivery timeline.

The AX22 protocol, the real innovation at the heart of Genesis, stays true to our original mission: a breadboard-compatible, truly modular ecosystem that works across platforms. Thank you for your trust, patience, and understanding. Every decision we make is aimed at delivering something that will serve you well not just at launch, but for years to come.

With gratitude,

Povilas, Chad, Tomas, and Marija
The Axiometa Team