🧪 Preview (Beta)
Suitable for production read workloads.
Most PostgreSQL driver features are supported; some PostgreSQL features may not yet be tested and could behave differently or not work in some tools.
Suitable for production read workloads.
Most PostgreSQL driver features are supported; some PostgreSQL features may not yet be tested and could behave differently or not work in some tools.

Connect Omni to Firebolt using the PostgreSQL protocol
This guide explains how to connect Omni to Firebolt using Firebolt’s PostgreSQL-compatible (pgwire) interface. Firebolt is exposed as a PostgreSQL endpoint, which allows Omni to query Firebolt databases using its built-in Postgres connector.Overview
When using Omni with Firebolt over the PostgreSQL protocol:- Firebolt is exposed as a PostgreSQL-compatible endpoint
- Authentication is done using Firebolt service accounts
- Database names use a triple identifier format:
<account>@<database>@<engine>
Prerequisites
Before starting, make sure you have:- Omni account Access to an Omni workspace with permissions to create connections, views, topics, and dashboards.
- Firebolt account An active Firebolt account. If you do not have one, you can sign up.
- Firebolt database and tables Access to a Firebolt database that contains data ready for analysis. If needed, you can create a database and then load data into it.
-
Firebolt service account
An active Firebolt service account, including:
- Service account ID
- Service account secret
- Firebolt user A Firebolt user associated with the service account, with:
Connect Omni to Firebolt
ℹ️ Network access requirement
Omni does not support mutual TLS (mTLS). In most cases, connections work without additional setup.
If you encounter connectivity issues, your Omni IP address may need to be allowlisted by Firebolt. See Allowlisting Omni IP Addresses.
Omni does not support mutual TLS (mTLS). In most cases, connections work without additional setup.
If you encounter connectivity issues, your Omni IP address may need to be allowlisted by Firebolt. See Allowlisting Omni IP Addresses.
Step 1: Create a PostgreSQL connection
- In Omni, go to Settings → Connections
- Click Add connection
- Select Postgres
Step 2: Configure connection details
Fill in the connection form with the following values.Basic settings
- Display Name: Any descriptive name (for example:
Firebolt Production) - Host:
pg.<region>.app.firebolt.io- Replace
<region>with your Firebolt account region (for example:us-east-1)
- Replace
- Port:
5432 - Database:
<account_name>@<database_name>@<engine_name>- Where
<account_name>is your Firebolt account name<database_name>is the target Firebolt database name<engine_name>is the target Firebolt engine name
- Where
Authentication
- Username: Firebolt service account ID
- Password: Firebolt service account secret
Schema configuration
Firebolt does not support custom schemas. All objects in Firebolt are created and queried in the defaultpublic schema.
As a result, schema configuration in Omni must be kept minimal.
Use the following settings:
- Include schemas: Leave empty or set to
public - Offloaded schemas: Leave empty or set to
public - Schema for table uploads: Leave empty or set to
public
Do not specify custom schemas in the Omni connection configuration.
Firebolt currently supports only the public schema, and configuring other schemas may result in query errors.
Firebolt currently supports only the public schema, and configuring other schemas may result in query errors.
Timezone configuration
Firebolt supports timezone-aware timestamps (TIMESTAMPTZ).
However, Omni timezone conversion features are not currently compatible with Firebolt.
Use the following configuration:
- Database timezone
UTC - Query timezone Do not set
- Allow user-specific timezones Disabled
Do not enable Query Timezone or Allow user-specific timezones in Omni.
Enabling these options may result in query execution errors when running queries against Firebolt.
Enabling these options may result in query execution errors when running queries against Firebolt.
Allowlisting Omni IP addresses
Omni connects to Firebolt from a fixed, stable set of outbound IP addresses. If you experience connectivity issues when connecting Omni to Firebolt, your Omni IP address may need to be allowlisted by Firebolt.How to allowlist Omni IPs
- In Omni, open the Firebolt connection configuration
- Locate the outbound IP addresses displayed in the connection screen
- Copy all listed IP addresses
- Contact Firebolt Support and request allowlisting
- See more about how to contact Firebolt Support and the severity guidelines.
- Your name and email address
- Your organization name
- The tool name (Omni)
- The Omni IP addresses to allowlist