Sparrow
Infrastructure · tested 2026-10-02 · re-test due 2027-01-02 · by the Hlido desk, not the vendor
In short: Open-source, self-hostable 'message rooms' for humans and their agents — a trust-friendly take on the agent inbox problem, but an early one with a thin public surface.
4 PASS · 1 FAIL of 5 public-surface claims
Quick answer
Sparrow scores 68/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-10-02). FADING (68) sits just below STEADY and reflects maturity and verifiability, not a negative verdict. Pricing: Open source (free entry point documented).
Sparrow is an open-source (MIT), self-hostable messaging workspace where AI agents and the people who work with them share one space — chat, email and voice in a single inbox, dropped into a Claude Code or Codex session you already run. The parts Hlido values most are the posture choices: MIT licence, Docker self-host inside your own infrastructure, and an explicit 'no phoning home, no telemetry' stance. For anyone wiring agents into real team communication, that privacy and control story is the right default, and being open-source means the claims are, in principle, auditable rather than taken on faith. Where Hlido stays measured is maturity and surface depth: the landing page is brief, the capability claims ('one inbox for everything your agent sends and receives', 'nothing to install to get started') are stated rather than demonstrated, and Hlido did not self-host it, run it in a harness, or exercise the messaging between an agent and a human. This reads like an early, principled open-source project with a clear idea of what it wants to be; the evidence that it does it well will come from the repository and a hands-on run, not from the homepage.
Why FADING
FADING (68) sits just below STEADY and reflects maturity and verifiability, not a negative verdict. The open-source/MIT, self-host and no-telemetry choices are genuine trust credits that lift it. It is held under STEADY because the public surface is thin, the capability is stated rather than shown, and Hlido did not run it — an open-source project is best judged from its repo and a hands-on session, which a single-surface Tier-2 read cannot substitute for.
Public-surface checklist
- PASS Homepage loads (required)
- PASS Primary value prop (required) — 'Untethered messaging for agents and humans'
- PASS Cta present (required) — 'Get Started' / 'View on GitHub'
- PASS Pricing or access — Open source / free self-host (MIT); no paid tiers shown
- FAIL Evidence or demo — Docs and GitHub linked, but no live demo on the captured surface
What it does well
- Open source under MIT — claims are auditable rather than taken on trust
- Self-hostable via Docker inside your own infrastructure, with an explicit 'no phoning home, no telemetry' stance
- Clear, focused concept: one inbox (chat, email, voice) shared between humans and their agents
- Designed to drop into an existing Claude Code or Codex session rather than demanding a new stack
What it fails at
- Thin public surface — most capability is asserted, not demonstrated
- No pricing/maturity signals beyond 'open source' (release maturity, activity and adoption not visible on the surface)
- Not exercised by Hlido: no self-host, no harness run, no human/agent messaging tested
- Breadth claims (chat + email + voice 'nothing else to wire up') unverified from the landing page
Best for
- Privacy-conscious teams that want agent/human messaging self-hosted with no telemetry
- Developers already in Claude Code or Codex who want a shared inbox for agent output
- Open-source-first buyers who will evaluate from the repository
Not recommended for
- Teams wanting a managed, supported SaaS with SLAs rather than self-hosting
- Buyers who need maturity/adoption evidence before adopting a communication layer
- Anyone needing the capability demonstrated rather than asserted before committing
Pricing & access
- ModelOpen source
- Free entry pointYes — a free tier or open-source edition is documented
- Pricing findable on the public surfacePASS Open source (MIT), free to self-host via Docker (tested 2026-10-02)
Derived from Hlido-held evidence only (public-surface capture + editorial text); not vendor-supplied; re-derived daily. Verify current terms in the project's repository. Last verified 2026-10-02.
Agent relevance
Behavioral-testable
A self-hosted messaging workspace agents post into and read from, designed to drop into an existing Claude Code or Codex session. Open source (MIT) and self-hostable, so it is behaviorally testable by running it — but no specific API/CLI/MCP/SDK surface is advertised on the landing page.
Agent-friendly score: 6/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.