GitHub launches theguysudo/ENZO: Self‑hosted AI workspace with agents, skills and Gmail/Calendar tools, running on your own API keys (including BYOK, Grok, OpenRouter, NVIDIA, Hugging Face, Google)
agents google huggingface nvidia open-source
| Source: Mastodon | Original article
An open‑source AI workspace called ENZO lets users self‑host agents, skills and tools such as Gmail and Calendar, running entirely on their own provider API keys—including Groq, OpenRouter, NVIDIA, Hugging Face and Google AI.
A new open‑source project called ENZO has been posted on GitHub, offering a self‑hosted AI workspace that runs entirely on users’ own provider API keys. The repository, created by the developer known as “theguysudo,” was announced on the Show HN forum with a brief description of the platform’s capabilities.
ENZO bundles a range of freely available large‑language‑model APIs under a single interface, allowing users to chat with more than 300 models and to build autonomous agents equipped with “skills” such as Gmail and Calendar integration. The system is designed for “bring‑your‑own‑key” (BYOK) operation: it supports keys from providers including Groq, OpenRouter, NVIDIA, Hugging Face and Google AI. All keys are kept sealed in the browser, and the entire stack can be launched with a one‑command Docker install, meaning the platform can run on any private server or cloud instance without sending data to a third‑party host.
The release arrives at a moment when European and Nordic regulators are urging greater control over AI infrastructure. By keeping model access and data processing in‑house, ENZO gives enterprises and developers a way to sidestep the growing concentration of AI services in a handful of large cloud providers. Its open‑source nature also invites community scrutiny and customization, which could be attractive to organisations that need to meet strict data‑privacy standards.
The next steps will reveal whether ENZO gains traction beyond hobbyists. Key indicators to watch include adoption by Nordic startups or public‑sector pilots, the emergence of third‑party extensions that add domain‑specific tools, and any security audits that assess the robustness of the BYOK key‑sealing approach. If the platform proves reliable, it could become a practical alternative for organisations seeking a locally controlled AI stack while still leveraging the breadth of commercial model APIs.
Sources
Back to AIPULSEN