Limitless vs Omi
Limitless vs Omi: side-by-side comparison of two voice-first / wearable ai memory systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.
Cost & capability
| Limitless | Omi | |
|---|---|---|
| Capability band | entry | competent |
| Capability composite | 38 | 42 |
| Cost tier | mid | mid |
| Use cases | Memory Augmented Chat, Analytical Summarization, Long Running Session | Latency Sensitive, Offline Capable, Memory Augmented Chat, Long Running Session |
Where they differ (13)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| Limitless | Omi | |
|---|---|---|
| Capability band | entry | competent |
| Capability composite | 38 | 42 |
| Use cases | Memory Augmented Chat, Analytical Summarization, Long Running Session | Latency Sensitive, Offline Capable, Memory Augmented Chat, Long Running Session |
| Type | Wearable pendant + screen capture lifelog | Open-source wearable orb + memory graph |
| Created | 2022 (as Rewind AI; rebranded Limitless April 2024; acquired by Meta December 2025) | 2024-03 |
| Pricing | Discontinued — no new sales since 2025-12-05; existing Pendant owners get Unlimited plan free | Hardware-bundled |
| Funding | Acquired by Meta (announced 2025-12-05; terms undisclosed); prior VC total $34.3M | $2M seed (Jan 2025; Draper Associates, 468 Capital; prior $700K bootstrapped) |
| Backend storage | custom | searched not found |
| Deployment | Managed-only | Both |
| API surface | REST (developer API) | searched not found |
| Embedding | locked | searched not found |
| Multi-tenancy | hard-isolation (per user) | searched not found |
| MCP | via official adapter — Limitless Developer API | yes — repo ships an MCP server (mcp/ folder) |
At a glance
| Limitless | Omi | |
|---|---|---|
| Section | Voice-first / wearable AI memory | Voice-first / wearable AI memory |
| Tier | T1 | T1 |
| Type | Wearable pendant + screen capture lifelog | Open-source wearable orb + memory graph |
| Created | 2022 (as Rewind AI; rebranded Limitless April 2024; acquired by Meta December 2025) | 2024-03 |
| Latest release | — | v0.12.522+12522-macos (2026-10-22) |
| License | — | MIT |
| GitHub | — | BasedHardware/omi — ~13.2k stars, last commit 2026-10 |
| Pricing | Discontinued — no new sales since 2025-12-05; existing Pendant owners get Unlimited plan free | Hardware-bundled |
| Funding | Acquired by Meta (announced 2025-12-05; terms undisclosed); prior VC total $34.3M | $2M seed (Jan 2025; Draper Associates, 468 Capital; prior $700K bootstrapped) |
| Backend storage | custom | searched not found |
| Deployment | Managed-only | Both |
| API surface | REST (developer API) | searched not found |
| Embedding | locked | searched not found |
| Multi-tenancy | hard-isolation (per user) | searched not found |
| MCP | via official adapter — Limitless Developer API | yes — repo ships an MCP server (mcp/ folder) |
| A2A | searched not found | searched not found |
| OpenTelemetry | no — consumer product | no — consumer product |
| Optimised for | always-on capture + lifelog timeline + voice UX | always-on capture + lifelog timeline + voice UX |
| Anti-fit | not for enterprise compliance-regulated environments without explicit consent flows | not for enterprise compliance-regulated environments without explicit consent flows |
Taxonomy
| Axis | Limitless | Omi |
|---|---|---|
| storage | file | graph |
| retrieval | similarity | graph-traversal |
| persistence | lifelong | lifelong |
| update | append-only | append-only |
| unit | episode | episode |
| governance | user-controllable | user-controllable |
| conflict | append | append |
Pros & cons
Limitless
Pros: Local-first lifelog architecture (originated as Rewind) is privacy-stronger than competitors; Meta acquisition gives it deep funding.
Cons: Recent platform pivot from Rewind macOS; product direction post-acquisition uncertain.
Omi
Pros: Open-source hardware + firmware + cloud — only wearable lifelog with a fully inspectable stack; users can pick their LLM provider.
Cons: DIY-leaning — less polished than vendor-managed competitors; community support is the support model.