~4 min read
Docs: Connect PostgreSQL
- 1Create a read-only kimo_reader role
- 2Allow-list Kimo egress IPs or open an SSH tunnel
- 3Pick schemas, enable logical replication for CDC
Read the guidePostgreSQL integration
66 connectors · new ones every month
Every source,
one data officer.
From MySQL and Stripe to Search Console, Splunk and AIS feeds — plug your sources into Kimo and get models, dashboards and answers in minutes.
0
Connectors
0
Categories
0
Minutes to connect
1Connect
OAuth, API key or a read-only database user. Most sources take under three minutes.
2Model
Kimo maps schemas, suggests joins across sources and lets you certify metrics once.
3See
Dashboards, maps, funnels and alerts — or just ask Kimo in plain English.
Popular
Where most teams start.
The sources connected first in Kimo demo workspaces.
Directory
All connectors.
Filter by category or by the Kimo that uses them. Click any card for tables, metrics and setup.
/
Showing 66 of 66 connectors
Custom sources
Not in the list? Kimo still reads it.
Kafka topics, webhooks, files and any REST API become first-class sources — same models, same dashboards.
Apache Kafka
Subscribe to any topic. Avro, Protobuf or JSON, with schema registry support.
- Exactly-once ingestion with consumer-group offsets
- Windowed aggregates for live dashboard tiles
- SASL/SCRAM, mTLS and private networking
kimo.yaml
source: kafka
brokers:
- broker-1.internal:9093
- broker-2.internal:9093
topic: sensors.telemetry
format: avro
schema_registry: https://registry.internal
auth:
mechanism: SCRAM-SHA-512
username: kimo-reader
window: 10s # live tiles refreshsensors.telemetry1,840 events/s
{"sensor_id":"cam-21","reading":22.0,"unit":"dB"}
p3 · offset 482,230
{"sensor_id":"gate-03","reading":21.5,"unit":"dB"}
p2 · offset 482,193
{"sensor_id":"buoy-12","reading":21.0,"unit":"dB"}
p1 · offset 482,156
{"sensor_id":"radar-07","reading":20.5,"unit":"dB"}
p0 · offset 482,119
Setup guides
Connected in three minutes, documented in full.
Step-by-step guides with screenshots, network requirements and the exact permissions Kimo needs.
~2 min read
Docs: Connect Search Console
- 1Sign in with Google (OAuth, read-only scope)
- 2Select one or more verified properties
- 3Kimo backfills 16 months of queries and pages
Read the guideGoogle Search Console integration
~3 min read
Docs: Sync schedules & freshness
- 1Choose a cadence per source: 15 min to daily
- 2Set freshness SLAs and alert on stale tables
- 3Incremental cursors keep syncs cheap
Read the guide
By product
Each Kimo starts from different sources.
Same connectors, three products. Pick the one that matches your questions.
Kimo Marketing
Search, ads, email and product data.
Search Console, GA4 and every ad network joined to your signups, so each channel shows the revenue it actually drives.
02 — Business Intelligence
Billing, CRM, finance and warehouse.
Stripe, HubSpot, Salesforce and your ledger modelled once, so MRR, pipeline and cash agree across every team.
// Defense Intelligence
Sensors, SIEM and open sources.
AIS, ADS-B, SIEM, Kafka and OSINT feeds fused on-prem, with every connector shipped in the air-gapped build.
Read-only by default
Kimo never writes to your sources unless you enable Reverse ETL.
Encrypted credentials
Per-workspace keys, AES-256 at rest, rotated automatically.
SSH tunnels & PrivateLink
Reach databases that never touch the public internet.
Runs on-prem too
Every connector ships in the sovereign and air-gapped builds.
Most requested
Upvote to bump the roadmap
- AmplitudeAnalytics
- KlaviyoMarketing
- JiraProduct
- Microsoft SentinelSecurity
- Pinterest AdsMarketing
- MISP threat sharingIntelligence
See your sources in a live workspace.
The demo comes pre-connected with mock data for all three Kimos. No signup needed.