Teams that choose Firebolt have usually outgrown what a standard warehouse can do. They're running high-concurrency workloads, building customer-facing analytics products, or serving real-time applications where query latency directly affects the user experience. That data is real-time and close to the product. But real-time data is only as valuable as your ability to query it in real time. If the data is live but access to it isn't, the speed you paid for stays on the table.
Ana closes that gap. Connect it to your Firebolt workspace and anyone on your team can ask questions in plain English, against the same warehouse, on the same data, right now.
How It Works
Ana connects directly to your Firebolt workspace, auto-discovers your schema, and translates natural language questions into SQL that runs against your Firebolt engine. No ETL, no data migration, no pipeline changes. Setup takes minutes. Because Ana queries Firebolt directly, it inherits Firebolt's performance characteristics. Answers, charts, and reports come back fast, even on large datasets.
Under the Hood
SQL dialect handling. Ana writes SQL the way a Firebolt specialist would. That means favoring Firebolt-native functions and avoiding patterns that force the planner into slower execution paths. The same question, answered with generic Postgres SQL versus Firebolt-optimized SQL, can return at very different speeds. Ana gets you the fast version.
Engine-aware routing. Firebolt separates compute (engines) from storage (databases), which gives teams precise control over workload isolation and cost. But it also means a misconfigured connection can succeed silently and return no data. The connector targets a specific named engine, with a fallback to the account default, and handles the misconfiguration case explicitly. If the engine is stopped or not attached to the right database, you get a clear signal rather than an empty result with no explanation.
OAuth service account authentication. Production data infrastructure shouldn't depend on individual user credentials. Ana connects via Firebolt's service account credential flow: client ID and secret, scoped to a dedicated service account. Credentials are encrypted at rest and never surfaced after initial setup. No shared logins, no manual token rotation, no credential exposure when team members change.
Getting Started
Navigate to the Connectors page in TextQL, select Firebolt, and fill in your account name, database, engine, and service account credentials. Ana discovers your schema automatically. You can start querying immediately. For full setup details, see the Firebolt connector docs.
The Firebolt connector is available today as a first-class connector. Find it on the Connectors page.
