We start with ENZO, a self-hosted AI workspace that runs agents, skills, and tools using your own provider keys under a Bring-Your-Own-Keys (BYOK) security model.

The user workspace features six surfaces in one: terminal, model marketplace, music player, agent builder, research mode, and a secure vault, with real-time health traces and live metrics, plus natural-language task descriptions to generate operating manuals for agents.

ENZO offers a unified catalog of 300+ models from 9 providers, injectable agent skills, 74 bundled domain playbooks, an agent loop with neural memory, a 2-pass builder, and a robust suite of 44 security/QA assertions in CI alongside hundreds of test suites for agents, vault, crypto, and models.

Edition variants include Lite and full images with theme options; ENZO_IMAGE toggles full feature access, and hosted deployments let Google sign-in be optional, while self-hosted deployments require BYOK.

Security-focused BYOK design seals keys in the browser with AES-256-GCM and non-extractable guarantees, offers optional re-sealing with a passphrase, and runs 44 black-box security tests per push; servers boot without provider keys in BYOK mode.

The project is released under the Apache-2.0 license, with a link to the LICENSE file.

Intro framing: ENZO is a self-hosted AI workspace that lets you run agents, skills, and tools using your own provider keys in a BYOK security model.

What’s new in v1.4.0 includes an in-chat file converter, Google Colab run option, and self-healing Docker dependencies, while v1.3.0 highlighted the music player, real EQ, redesigned marketplace, NYC Subway theme, and UI refinements.

The core workflow uses a three-phase agent builder process (analysis draft, race of roughly ten free candidates, honest provenance), with continuous neural updates and memory integration for each agent.

Projects, skills, and memory are stored live in Docker volumes, keys never leave the browser, and the first paste of a key activates server-side features.

Cross-platform setup covers macOS, Windows, and Linux, with standard commands for logs, restart, update, and down; data persists in Docker volumes, and Colab offers zero-install runs.

Architecture-wise, keys are pasted in the browser and sealed client-side with AES-256-GCM, never read by the server; there is no central usage meter or subscription, as billing goes directly to providers.