ENZO
Productivity · tested 2026-09-28 · by the Hlido desk, not the vendor
In short: A self-hosted, bring-your-own-keys AI command center with a genuinely strong key-custody story — let down on the surface by rough edges and a pricing table that says nothing.
5 PASS · 0 FAIL of 5 public-surface claims
Quick answer
ENZO scores 71/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-09-28). STEADY (71) for a coherent, genuinely useful self-hosted BYOK AI workspace with a specific, correct key-custody posture (AES-256-GCM, non-exportable key, optional passphrase, keys never on the vendor's servers) and a rea Pricing: Subscription.
ENZO's thesis is 'frontier AI without frontier lock-in': one console that routes across nine provider gateways (Groq, OpenRouter, NVIDIA NIM, Hugging Face, Google AI, Cloudflare Workers AI and more), a cognitive-mode agentic terminal with SSE reasoning streams, a model-catalog advisor, and a set of agent tools (search, mail, calendar, documents) — all running on the user's own provider keys, on the user's own machine. The part Hlido credits most is the custody model, which is specific rather than hand-wavy: provider keys are encrypted with AES-256-GCM before they touch browser storage, under a key the browser will not let any JavaScript export, with an optional passphrase leaving nothing usable at rest, and the vendor states plainly it never syncs, stores or logs keys. For a BYOK product that is the whole ballgame, and stating it precisely is the right instinct. The routing-through-your-own-machine, no-wrapper-markup pitch is coherent and increasingly in demand. Where the surface undercuts the product: it is hosted on a duckdns.org demo domain rather than a stable custom domain, there is a visible typo in the hero ('Welcmo to ENZO') that dents the craft impression, and the pricing table lists Starter, Pro and Enterprise all at $0 with playful copy ('Buy — we dare you') — which reads less as a decision than as commercialization not yet thought through. Traction is early (108 GitHub stars) and the console sits behind a login, so its behaviour is asserted, not demonstrated here. This is a substantive, security-minded open-source workspace reviewed from its public surface; Hlido did not log in or drive the agents.
Why STEADY
STEADY (71) for a coherent, genuinely useful self-hosted BYOK AI workspace with a specific, correct key-custody posture (AES-256-GCM, non-exportable key, optional passphrase, keys never on the vendor's servers) and a real breadth of routing and agent tooling. Held to the lower half of the band because this is a public-surface review (medium confidence, no login or hands-on run by Hlido), the surface carries craft and trust dents — a duckdns.org demo host, a hero typo, and a pricing table showing all three tiers at $0 that signals immature commercialization — and community traction is early (108 GitHub stars).
Public-surface checklist
- PASS Homepage loads (required) — enzo-hub.duckdns.org returned a full product page (page_title 'ENZO — AI Hub')
- PASS Primary value prop (required) — 'The command center for frontier AI without frontier lock-in — every model routable, every key yours, every request leaving from your own machine'
- PASS Cta present (required) — 'Explore the system' / 'SIGN UP'
- PASS Pricing or access — A three-tier pricing table (Starter/Pro/Enterprise) all listed at $0, with overage tokens billed at provider list price
- PASS Evidence or demo — A live demo host and detailed architecture/security sections shown; a hero typo ('Welcmo to ENZO') is visible and the console itself is behind a login
What it does well
- Specific, correct key-custody model — provider keys encrypted with AES-256-GCM under a browser key JavaScript cannot export, an optional passphrase leaving nothing usable at rest, and an explicit 'we never sync, store or log your keys'
- Coherent 'no lock-in, no wrapper markup' routing — one console across nine provider gateways, with requests leaving from the user's own machine at provider list price
- Real breadth for a self-hosted workspace — an agentic terminal with cognitive modes and SSE reasoning streams, a catalog advisor that recommends and launches a model, and agent tools for search, mail, calendar and documents
- Resilience touches that show engineering thought — auto-fallback across providers mid-stream, and a search path that tries four backends in order so a dead endpoint costs quality, not the feature
- Open-source and self-hostable, so the trust claims can in principle be audited by the user
What it fails at
- Hosted on a duckdns.org demo domain rather than a stable custom domain — a professionalism and continuity signal against an otherwise serious product
- A visible hero typo ('Welcmo to ENZO') that dents the craft impression on first contact
- A pricing table listing Starter, Pro and Enterprise all at $0 with jokey copy — reads as commercialization not yet decided rather than a deliberate free-forever position
- Early community traction (108 GitHub stars) relative to the breadth of what is claimed
- Login-gated console with no hands-on run by Hlido — routing, custody enforcement, and the agent tools are asserted on the surface, not demonstrated here
Best for
- Self-hosting power users and homelabbers who want one BYOK console across many model providers without a wrapper markup
- Privacy-conscious individuals who want provider keys encrypted and kept on their own device, never on a vendor server
- Developers wanting a single agentic terminal with provider auto-fallback over Groq/OpenRouter/NVIDIA/HuggingFace/Google AI and more
- Cost-sensitive users happy to pay providers directly at list price rather than a marked-up subscription
Not recommended for
- Non-technical users who cannot self-host or manage their own provider API keys
- Buyers who need a clear, stable commercial and support model — the all-$0 tiers and demo-domain hosting leave that undefined
- Teams needing verified custody guarantees before adoption — treat the (well-stated) security claims as unmeasured until audited
- Anyone wanting a polished, managed hosted product rather than an early self-hosted open-source workspace
Pricing & access
- ModelSubscription
- Pricing findable on the public surfacePASS A three-tier pricing table (Starter/Pro/Enterprise) all listed at $0, with overage tokens billed at provider list price (tested 2026-09-28)
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-09-28.
Related agents
Agent relevance
No programmatic surfaces
ENZO is a self-hosted, login-gated console a human operates — a BYOK workspace that runs agent 'tools' and cognitive modes internally and can consume MCP tools. It exposes no documented external API or MCP server on the public surface for a third-party agent to drive ENZO itself. It is best understood as a human-operated workspace upstream of agent workflows, not a component another agent calls remotely.
Agent-friendly score: 3/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- Self-hosted, bring-your-own-keys AI command center that routes across nine provider gateways from one console, with requests leaving from the user's own machine at provider cost (no wrapper markup) — source (2026-09-28) verified
- Provider keys are encrypted with AES-256-GCM before touching browser storage under a non-exportable key; an optional passphrase leaves nothing usable at rest; keys are never synced, stored or logged — source (2026-09-28) verified
- An agentic terminal with cognitive modes (normal/thinking/research/coding/image), SSE reasoning streams, provider auto-fallback, and a catalog advisor that recommends and launches a model — source (2026-09-28) verified
- Three plans — Starter, Pro and Enterprise — all listed at $0; overage tokens billed at provider list price — source (2026-09-28) verified
- Agent tools spanning search, research, mail, calendar and documents, running against the user's own infrastructure — source (2026-09-28)