Product review

Omi DevKit 2 Review 2026: Open-Source AI Wearable vs NERALVO Halo

By NERALVO Editorial Team Published 31 August 2026 Reviewed 31 August 2026 3 minute read

The 60-second verdict

Quick answer: This article covers Omi DevKit 2 specifically, not every Omi consumer-device revision. DevKit 2 is an open-source wearable AI platform with 8GB onboard storage, a speaker, a programmable button and standalone recording.

Best fit: developers and technical users who value open hardware, custom firmware, self-hosting and integrations.

What makes Omi different?

Most AI recorders sell a fixed device plus a proprietary app. Omi's hardware, firmware, app and backend are designed to be open and customisable. That changes the buying decision: the value is control and extensibility rather than simply battery life or transcription minutes.

DevKit 2 position

Format	Wearable pendant
Processor	Xiao nRF52840
Storage	8GB onboard
Speaker	Built in
Control	Programmable button
Standalone recording	Supported
Software	Open-source ecosystem

Strengths

Open-source hardware and software.
Custom integrations and self-hosting options.
Wearable conversational-memory format.
Developer community and programmable behaviour.
Official developer documentation exposes storage/button test procedures rather than hiding the implementation.

Limitations

Less turnkey than mainstream consumer products.
Hardware and firmware revisions differ.
8GB DevKit 2 storage is below mainstream 64GB cards.
Wearable memory use raises strong privacy and participant-notice questions.
Open hardware can expose implementation-level failure modes that a buyer must be prepared to diagnose.

Omi DevKit 2 vs Halo

Feature	Omi DevKit 2	Halo
Format	Wearable/open-source	Magnetic card
Storage	8GB	64GB
Customisation	Very high	Consumer appliance workflow
Software	Open-source Omi stack	DOWAY

Omi DevKit 2 is stronger for builders. Halo is stronger for buyers who want a finished appliance without maintaining or customising software.

Engineering reliability evidence

Omi's current DevKit 2 testing documentation explicitly treats SD-card storage, offline audio, button events and safe storage handling as areas developers should test. That is useful because DevKit 2's value depends on the hardware/software chain working as a system rather than on a sealed appliance experience.

A July 2026 issue in the public BasedHardware/Omi GitHub repository reported a specific DevKit v2 failure mode on firmware 2.0.10: an SD-card mount failure could occur before Bluetooth initialisation and leave the device not advertising over BLE without a clear LED/serial error. This is a public engineering report, not evidence that every unit is affected. It is nevertheless a concrete reason to include cold boot, storage mount, BLE advertising, offline-recording and recovery in acceptance testing before depending on a custom Omi deployment.

Before buying or deploying

Confirm the exact Omi hardware and firmware revision.
Decide whether self-hosting/customisation is genuinely required.
Test cold boot, SD/storage mount, BLE advertising and offline recording repeatedly.
Test source-audio retention, import and export for that revision.
Define who owns firmware updates, backend operation, security and incident recovery.
Define a participant-notice workflow.
Compare the support burden against a closed consumer recorder.

Official and engineering sources

Verdict: Omi DevKit 2 is not simply another Halo/PLAUD clone. It is stronger when openness is the requirement, but the same openness shifts firmware, storage, Bluetooth and recovery validation onto the builder. Ordinary recording users may be better served by a finished appliance.

Optional comparison

Compare the same workflow with NERALVO Halo

Use the evidence and acceptance tests in this review first. Then compare Halo’s 64GB local storage, NOTE/supported CALL workflow, up-to-35-hour published recording time and current included service on the same requirements.

View Halo specifications and current offer

Found an error or an out-of-date claim? Email support@neralvo.com with the article address and a supporting source.

Buyer questions

Frequently asked questions

What should I verify before buying this competitor?

Verify the exact current SKU, recording route, source-audio access, export and deletion process, monthly AI allowance and total software cost on the official vendor page.

Are the battery and pickup figures guaranteed?

No. Unless the article explicitly identifies an independent test, treat headline battery and pickup figures as manufacturer-published maxima that need representative testing.

Why does this review compare the product with NERALVO Halo?

NERALVO sells Halo and discloses that commercial interest. The comparison is intended to identify workflow trade-offs rather than force a NERALVO win.

Confirmed

Supported by the current evidence

The exact product identity and current headline specifications are tied to dated sources in the article.

The comparison keeps manufacturer claims separate from independently demonstrated findings.

Conditional

Do not overclaim this

Battery, pickup range, transcription quality and long-term software terms remain conditional until tested in the buyer’s workflow.

Acceptance test

Prove this before relying on it

Run the exact recording route, transfer/export path, recovery process and monthly AI workload before relying on the product.

Decision gate

Choose Omi DevKit 2 when its specialist workflow solves the buyer’s main problem better.
Choose NERALVO Halo when a simpler 64GB magnetic recorder with up to 35 hours of published recording time and the current one-year DOWAY Max bundle fits better.
Choose neither yet if source-audio access, call compatibility, export/recovery, privacy requirements or two-year software cost are still unproven for the actual workload.

Evidence and freshness

Competitor-review evidence and sources

Reviewed: 31 August 2026. Prices, subscriptions, compatibility, privacy terms and software features can change. Check the official vendor links in this article before acting on time-sensitive information.

Commercial disclosure: NERALVO sells Halo. These reviews therefore have a commercial interest. A supplier specification establishes what that supplier currently claims; it does not prove independent battery life, pickup range, transcription accuracy, privacy quality or value.

Hands-on rule: do not treat a conclusion as NERALVO-tested unless the article states the device/software version, test date, setup, representative source recordings, measurements and retained original evidence. Otherwise the assessment remains desk research.