Question 1

What is AimDB?

Accepted Answer

AimDB is an async, in-memory dataflow engine that syncs sensor and state data across microcontrollers, edge gateways, cloud instances, and browser SPAs using portable data contracts. Distributed by design, data-driven by default.

Question 2

What platforms does AimDB support?

Accepted Answer

AimDB supports four tiers: ARM Cortex-M microcontrollers (STM32) with no_std + alloc Rust and Embassy, Linux-based edge gateways with Tokio, cloud deployments on Kubernetes, and browser-based SPAs via WebAssembly.

Question 3

What are portable data contracts?

Accepted Answer

Portable data contracts are schema definitions that compile identically for embedded no_std + alloc targets, standard Rust, and wasm32, allowing the same data logic to run on MCU, edge, cloud, and browser.

Question 4

Is AimDB open source?

Accepted Answer

Yes, AimDB is open source and available on GitHub at github.com/aimdb-dev/aimdb under the Apache 2.0 license.

Question 5

Can I use the same Rust code on MCU and cloud?

Accepted Answer

Yes, AimDB provides the same API across all runtimes. Code written for an STM32 microcontroller works identically on Linux edge gateways, Kubernetes cloud deployments, and browser SPAs via WebAssembly.

Question 6

Does AimDB support no_std Rust?

Accepted Answer

Yes, AimDB runs in no_std + alloc environments on embedded systems using Embassy's configurable heap allocator. It also supports Tokio on Linux and cloud, and WASM in the browser.

Question 7

How does AimDB compare to other embedded dataflow engines?

Accepted Answer

Unlike traditional embedded databases, AimDB provides portable data contracts that work across MCU, edge, cloud, and browser with the same codebase, enabling seamless data synchronization across all four tiers.

Question 8

What connectors does AimDB support?

Accepted Answer

AimDB supports MQTT and KNX connectors for edge computing integration, enabling data ingestion from industrial sensors and building automation systems directly into the Rust dataflow engine.

Question 9

How does schema evolution work in AimDB?

Accepted Answer

AimDB's MigrationStep trait provides typed, bidirectional schema evolution validated at compile time. The migration_chain! macro wires version steps into a chain that works across all targets — STM32 MCU, Linux edge, Kubernetes cloud, and browser — ensuring consistent data across your distributed system.

Question 10

What is a dataflow engine?

Accepted Answer

A dataflow engine is a runtime that processes data as it flows through a system of connected nodes. AimDB's Rust dataflow engine runs identically on microcontrollers, edge gateways, and cloud infrastructure, enabling real-time distributed data processing.

Dataflow engine for distributed systems.
MCU to Cloud. Same API.

Portable Data Contracts

One contract, many runtimes

Cost control by placement

Portable schemas + transforms

Why AimDB

Runs Where Data Starts

Same API Everywhere

Built for Continuous Change

Ready to Get Started?

Star on GitHub

Report Issues

Join Discussions

Dataflow engine for distributed systems.MCU to Cloud. Same API.