ATLAS Explain Sign in Add to your AI assistant

How it's built

The technical design behind ATLAS Explain, for developers and for the judges of Google's #BuildHybridAI challenge. Everyday use needs none of this.

The AI-assistant connector (MCP)

Setup steps for each assistant are on the setup page.

Hybrid inference with Firebase AI Logic

In the web app, every explanation goes through the Firebase AI Logic Web SDK in hybrid mode, with prefer_on_device as the default.

  1. On the device. When Chrome's Prompt API reports Gemini Nano as available, the prompt runs locally. Nothing leaves the computer, and the answer is labelled "On this device".
  2. In the cloud. When Nano is unavailable (phones, other browsers, older hardware) or the text is too long for it, the same prompt goes to Gemini Flash-Lite in the cloud and is labelled "Cloud".
  3. Private context stays local. Private notes and watchlists are only ever included in on-device prompts. A cloud fallback drops them and says so.

The path that actually ran is read from the SDK's response and shown on every answer. It is never guessed.

Protection and configuration

Data

Stack

Source

Everything runs online: the website and web app on Firebase Hosting, and the AI-assistant (MCP) address on Cloudflare's free plan. The code is open source under Apache-2.0 at github.com/MISHHF93/atlas-explain.