Ethyx v1.0: Building the foundation

Editor's note: These are historical release notes. Bring-your-own-key (BYOK) was retired in v1.2—provider access is now included with your Ethyx account, so you no longer connect your own API keys.

Ethyx v1.0 was our first public release: a web-based AI client that hides provider SDK differences behind one consistent experience. Here is what we set out to ship—and what landed.

What we accomplished

• Unified streaming chat across OpenAI, Anthropic, and xAI from a single UI—no juggling SDKs or endpoints as a user.
• Bring-your-own-key (BYOK) so you connected your own provider API keys; Ethyx encrypted them and kept them out of plain text.
• Conversation history, projects, and context so threads persisted, organized, and stayed useful across sessions.
• Optional web research in chat with per-turn search modes (quick, balanced, expert) backed by configurable search tools when Tavily is enabled.
• Accounts built for real use—registration, password reset, authenticator-app (TOTP) MFA, rate limiting, and a responsive web UI for desktop and mobile browsers.

What v1.0 deliberately left out

We scoped v1.0 as a foundation, not a finished product. Billing through Ethyx, native mobile apps, teams, and cloud integrations were explicitly deferred. A formal WCAG accessibility audit was scheduled for v1.1, with inclusive practices baked in from day one.

Looking back

v1.0 established the provider-agnostic architecture, streaming chat pipeline, and account model that v1.1 and v1.2 extended. If you joined after subscriptions and Google Drive, this is the release that proved the core chat loop could work reliably at scale.

Thanks for being early users while we iterated.