Hi all I maintain ENZO, a self-hosted AI workspace. It's Apache-2.0, about 60k lines of strict TypeScript, and it runs on your own provider keys (Groq, OpenRouter, NVIDIA, Hugging Face, Google AI). No ENZO account, no subscription, no middleman — you talk to the provider you picked and pay them directly. The v1.7.0 release is out today, and the biggest change in it is how you install it.
Repo: https://github.com/theguysudo/ENZO
v1.7.0: https://github.com/theguysudo/ENZO/releases/tag/v1.7.0
It installs like a normal app now
Until now ENZO was a docker compose file you cloned and edited. v1.7.0 ships a macOS .dmg and two Windows installers. No git clone, no Docker Desktop, no system Node — the bundle carries its own Node runtime and the built frontend, and serves the same backend on port 5200.
macOS (Apple Silicon): ENZO-1.7.0-macOS-arm64.dmg (~133 MB)
Windows x64, lighter theme set: ENZO-1.7.0-less-theme-setup.exe (~73 MB)
Windows x64, every theme and every video background: ENZO-1.7.0-full-theme-setup.exe (~289 MB)
It also updates itself: when a new release appears, a small banner offers Update now, the bundle is swapped in place and ENZO restarts. The reminder is deliberately gentle — at most twice per rolling week, never forced. Your data (memory, vault keys, investigations, neural state, generated projects) lives in a per-user directory outside the app bundle, so an update can't take it with you, and the browser session survives the restart. Docker installs are unchanged and still the better answer for a server — and as of this release a rebuild no longer wipes your investigation data.
ENZO Intelligence — research mode that cites its evidence
What: you write an objective in plain English, and it turns into a set of research questions.
How: connectors (Exa web search, website fetch, GitHub read-only, Wikipedia, your own documents) collect the sources, and a pipeline — plan → discover → extract → resolve → verify → report → diff — turns them into an evidence ledger where every claim carries a verbatim quote from the source it came from.
Why: the weak spot of AI research output is that you can't tell which sentence came from where. Here the claim and its quote sit side by side, and when two sources disagree, the conflict is shown rather than smoothed over.
There are two buttons with two depths: Run planning asks the questions and fetches nothing, Run investigation runs the full pipeline and diffs the result against the previous run. Click any node in the graph to get its explanation and the evidence behind it, and ask follow-up questions that are answered strictly from the ledger. The report downloads as markdown. Page caps, an evidence cap of 400 and a 10-run history are enforced in the orchestrator, not left to the model's judgement. Scraped pages arrive wrapped in an UNTRUSTED rule so a web page can't talk your agent into running commands.
Neural Engine (phases 0–4) — a private preference layer
What: a per-owner research profile across 8 preference dimensions, a knowledge graph, and an append-only audit trail of every mutation.
How: inference needs at least two samples and never overrides something you stated explicitly — the provenance order is always task override > what you said > what was inferred. Every write is schema-gated before it hits disk. A preference context of at most 1400 characters is injected after memory on the chat and research paths.
Why: it stays on your box, forget erases the profile on demand, and ENZO_NEURAL_OVERLAY=0 turns the whole thing off. There's also a zero-cost mode: a capability registry of 8 providers (free flags, quota behaviour, privacy class) drives a fail-closed route check that refuses paid routes. The Neural Map also got a 2D/3D toggle — the 3D orbit camera had existed but was unreachable.
A security pass over the whole surface
Seven fixes, each with a regression test:
Every user-supplied URL now goes through one pinned fetcher: https only, no credentials in the URL, the hostname resolved once with every DNS answer required to be public, and the socket connects to that exact validated address — which closes the rebinding window between "we checked the name" and "we opened the socket". The guard is re-applied on every redirect hop and the response is size-capped while it streams.
Anonymous callers can no longer touch instance state: the memory and skill commands, the learned-skill context and the neural research profile all require a vault session now.
The NVIDIA base URL is pinned, so a caller's key can't be relayed to a host they picked.
Project internals (manifest.json, generated databases) return 404, and every HTML/SVG served from a project gets the sandbox CSP — not just the entry page.
Generated code can no longer retry without the runtime permission model when its first boot fails.
The vault token is never persisted.
A high-severity dependency advisory (body-parser DoS) is fixed — npm audit now reports 0 vulnerabilities.
Verification is in CI: 13 test suites / 460 checks, plus a black-box pentest script (11 checks) that runs against the live server.
Smaller fixes worth knowing about
Six real chat reply bugs, found by using the app rather than reading it: a truncated stream lost the last line of an answer, an image attachment ate the reply, AI Assist overwrote the first frame, a stale auto-mode reference fought the UI, previews were detected when there was nothing to preview, and a failed request could leave a blank bubble. The README now also carries an app-downloads badge fed by GitHub's own release-asset counter, and a feedback form.
Why try it
If you've been meaning to self-host an AI workspace but didn't want to deal with compose files, volumes and Node versions, the DMG/EXEs are the shortest path — and it's the same server either way, so you can move between the app and Docker without changing anything. The only thing you need is one provider API key of your own. If something breaks, say so in the comments or open an issue; I read them.