Activation from your own tables
Define “activated” once in SQL or the visual modeler, then reuse it everywhere.
Read-only replication of your Postgres tables every 15 minutes. Join users, orders and events with every other source.
Live demo workspace with fictional data · no signup, no credentials needed

PostgreSQL on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
Define “activated” once in SQL or the visual modeler, then reuse it everywhere.
Link public.users to Stripe customers and HubSpot contacts through email or external ids.
Track which features new accounts adopt in their first week, by plan and acquisition channel.
“Which plans had the most upgrades last month?” Kimo writes the SQL and shows its work.
Kimo maps PostgreSQL into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| string | ||
| plan | enum | Low-cardinality dimension |
| created_at | timestamp | Incremental cursor |
| utm_source | enum | Low-cardinality dimension |
This model ships with the Business Intelligence demo. Open it to see every join and measure.
MRR, new customers, expansion and churn from Stripe + product DB.

Fictional data · hover the chart for daily values
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
Grant SELECT only. Kimo never writes to your database.
Allow Kimo’s static egress IPs, use an SSH tunnel, or run the on-prem agent inside your network.
Credentials are encrypted at rest with a per-workspace key and tested before saving.
Choose what to sync, starting with public.users. Kimo backfills, then keeps it fresh.
CREATE USER kimo_reader WITH PASSWORD '<generated>';
GRANT USAGE ON SCHEMA public TO kimo_reader;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO kimo_reader;
ALTER DEFAULT PRIVILEGES IN SCHEMA public
GRANT SELECT ON TABLES TO kimo_reader;Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
By default Kimo syncs PostgreSQL every 15 min. You can change the schedule per table, or trigger a sync manually from the connector page.
Try it on the live demo workspace first, then connect your own account when you are ready.