MicroQuant v1
Customer-specific GA · available on demand

Embedded inference built for your product.

MicroQuant v1 turns bounded, statically shaped integer graphs into deterministic ABI-v6 C. The promoted schemes are W8, PCQ4, SPQ4, KARQ, and mixed precision, with explicit limits, caller-owned workspace, and no runtime model parser.

Discuss your implementation Read the support contract
Current envelope ABI 6 5 schemes Portable C
MicroQuant compilerMQ-V1
ABI 6/6 compiler / runtime
Schema closedfail closed
W8–4bpromoted schemes
No heapruntime execution
256maximum graph operators
1–4graph inputs
1–4graph outputs
256 KiBmaximum caller workspace
Promoted v1 coverage

A narrow contract.
A complete failure boundary.

Every accepted model is validated before output is committed. Unsupported shapes, operators, quantization, targets, and malformed inputs fail with structured diagnostics.

Dense Identity Flatten ReLU Clamp
Bounded ingestion

Four explicit source formats.

Canonical ABI-v6 JSON, source-authorized JSON, quantized ONNX QLinearMatMul, and signed-int8 TFLite fully connected graphs enter the same typed compiler path.

Download machine-readable status
Customer-specific GA delivery

A production path
qualified for your exact product.

MicroQuant v1 is available through customer-specific GA engagements. We bind the model, generated artifacts, firmware, target toolchain, verification, and support to the exact implementation instead of offering a one-size-fits-all generic binary.

Delivery modelGAcustomer-specific
01

Compiler + runtime

ABI-v6 production foundation

Deterministic generated C, strict C/C++ integration, lifecycle checks, and numerical proof replay form the common v1 foundation.

02

Target integration

ESP32-S3 ready

The exact ESP-IDF toolchain and generated-source path are ready for customer qualification; additional microcontrollers are evaluated on demand.

03

Implementation validation

Bound to your product

Board measurements, received-byte parity, resource budgets, and integration tests are produced for the customer's exact model and firmware.

04

GA delivery

Available on demand

Each engagement completes the production signing, commercial terms, acceptance, support, and lifecycle package for that customer-specific release.

Read the machine-readable status Read the evaluation terms
Integration path

Model to generated C.
No hidden runtime.

The development workflow separates admission, compilation, received-byte verification, and firmware ownership so each boundary can be tested independently.

  1. 01

    Preflight

    Validate the model format, graph envelope, quantization, limits, target, and proof prerequisites without writing output.

  2. 02

    Compile atomically

    Create deterministic generated C, manifests, integrity identities, and an explicit manual source list.

  3. 03

    Verify and integrate

    Verify the received kit, compile the declared files, provide caller-owned buffers, and retain target acceptance as a separate activity.

Technical evaluation

Does your graph fit the v1 envelope?

Share the model format, graph shape, target, and constraints. We will qualify the fit and scope a customer-specific GA implementation for your product.

First stepContract-bound model review
✓

Request received.

We will follow up at .