What is this?
ENZO is a self-hosted AI workspace bundling agents, skills and tool integrations such as Gmail and Calendar. The defining constraint is BYOK: it runs against your own provider API keys rather than a hosted subscription. Supported providers listed by the author include Groq, OpenRouter, NVIDIA, Hugging Face and Google AI.
Built with
TypeScript, Docker, and the Model Context Protocol for tool wiring.
Why it is interesting?
The BYOK model inverts the usual arrangement. Instead of paying a monthly fee for a hosted agent platform, users pay their own inference bill and keep the data on their own machine. The Hacker News thread ran to 13 comments, mostly about that trade-off.
Who should look at it?
ENZO is a useful reference for people who want one workspace for agents and tool integrations without handing the whole workflow to a hosted service. It also gives developers a concrete place to compare provider support, local deployment and tool wiring.
What to inspect
Start with the provider configuration, the Docker setup and the Gmail/Calendar integrations. Those files reveal the real operating model more clearly than the product description: where credentials live, how tools are exposed, and what the user has to run locally.
Watch point
BYOK changes the cost and control boundary; it does not remove the need to secure API keys or review what an agent can do. Treat the self-hosted claim as an architectural property to verify in the repository, not as a guarantee that every integration is isolated.