Built to work with the stack you already run
Around 80 native connectors for databases, warehouses, BI tools, pipelines, messaging systems, and API gateways. Goava catalogs what you already operate — no rip-and-replace, whether self-hosted on-premises or in the cloud inside Saudi Arabia.
Around 80 native connectors
From Snowflake, BigQuery, and Oracle to Power BI, Kafka, Airflow, dbt, and Kong — connect your sources in minutes and let metadata flow into one unified catalog.
Databases & Warehouses (41)
BI & Dashboards (14)
Pipelines & Orchestration (13)
Messaging & Streaming (3)
Storage (2)
API Gateways (5)
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
Frequently asked questions
Can we connect a source that isn't on the list?
Goava ships with around 80 native connectors covering databases, warehouses, BI tools, pipelines, messaging systems, and API gateways. 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.
Connect your stack to one catalog
See your own sources flowing into Goava — metadata only, inside your environment — in a live demo.