Can we connect a source that isn't on the list?

Goava ships with more than 80 native connectors covering databases, warehouses, BI tools, pipelines, messaging systems, and OpenAPI services; connectors for API gateways are in preview. If a system isn't covered, its metadata can be registered through Goava's APIs, and we can scope additional connector needs with your team during onboarding.

How is metadata ingestion scheduled?

You define the schedule per source — hourly, daily, or a custom interval. Each pipeline runs automatically, picks up new and changed assets, and updates the catalog without manual effort. You can also trigger an ingestion run on demand whenever you need a fresh view.

Does our data leave our environment?

No. Connectors read metadata only — schemas, names, descriptions, lineage, and usage signals — and never copy your underlying data. And because Goava deploys self-hosted on-premises or in the cloud inside Saudi Arabia, even that metadata stays within your environment.

80+ Native Connectors

Built to work with the stack you already run

80+ native connectors for databases, warehouses, BI tools, pipelines, messaging systems, and OpenAPI services, with API gateway connectors in preview. Goava catalogs what you already operate — no rip-and-replace, whether self-hosted on-premises or in the cloud inside Saudi Arabia.

Request a Demo Explore the Product

80+ native connectors

From Snowflake, BigQuery, and Oracle to Power BI, Kafka, Airflow, dbt, and OpenAPI services — connect your sources and let metadata flow into one unified catalog.

Databases & Warehouses46

Athena
Azure SQL
BigQuery
Bigtable
BurstIQ
Cassandra
ClickHouse
CockroachDB
Couchbase
Databricks
Data Lake (S3/GCS)
DB2
Delta Lake
Domo Database
Doris
Druid
DynamoDB
Exasol
AWS Glue
Greenplum
Hive
Impala
IOMETE
MariaDB
MongoDB
SQL Server
MySQL
Oracle
Pinot
PostgreSQL
Presto
QuestDB
Redshift
Salesforce
SAP ERP
SAP HANA
SAS
SingleStore
Snowflake
SQLite
StarRocks
Teradata
TimescaleDB
Trino
Unity Catalog
Vertica

BI & Dashboards18

Domo
Grafana
Hex
Lightdash
Looker
Metabase
MicroStrategy
Mode
Omni
Power BI
Qlik Cloud
Qlik Sense
QuickSight
Redash
Sigma
SSRS
Superset
Tableau

Pipelines & Orchestration15

Airbyte
Airflow
Dagster
Databricks Pipelines
dbt
dbt Cloud
Domo Pipelines
Fivetran
Flink
Glue Pipelines
Kafka Connect
NiFi
OpenLineage
Prefect
Spline

Messaging & Streaming4

Google Pub/Sub
Kafka
Kinesis
Redpanda

Storage2

Amazon S3
Google Cloud Storage

Metadata Platforms3

Alation (export)
Amundsen
Apache Atlas

ML Models2

MLflow
SageMaker

Search2

Elasticsearch
OpenSearch

Drives & File Transfer2

Google Drive
SFTP

APIs1

OpenAPI (REST)

API Gateways (preview)5

Kong
Amazon API Gateway
Azure API Management
Google Cloud API Gateway
NGINX

How ingestion works

Metadata comes in. Your data stays put.

Goava's ingestion pipelines run on schedules you define and read metadata only: schemas, table and column names, descriptions, lineage, and usage signals. Your data is never copied or moved — the catalog stays current while everything sensitive stays exactly where it lives today.

Scheduled, metadata-only ingestion pipelines — no data is ever copied
Schedules you control: hourly, daily, or a custom interval per source
Every run keeps the catalog automatically up to date as your stack evolves
Runs entirely within your environment — self-hosted on-premises or cloud inside Saudi Arabia

Explore the Data Catalog

Frequently asked questions

Connect your stack to one catalog

See your own sources flowing into Goava — metadata only, inside your environment — in a live demo.

Request a Demo