kimo
Open demo
DatabasesPopular

MySQL + Kimo

Your MySQL tables, replicated read-only every 15 minutes and ready to join with billing, CRM and marketing data.

Auth
Read-only credentials
Sync
Every 15 min
Setup
≈ 10 min
Request access

Live demo workspace with fictional data · no signup, no credentials needed

kimo / connectors / mysqlSyncing
Sync logevery 15 min
  • Succeeded:app.sessions+414 rowsnow
  • Succeeded:shop.order_items+2,033 rows2m ago
  • Succeeded:shop.orders+1,976 rows4m ago
  • Succeeded:shop.customers+1,195 rows6m ago
Rows synced · 30 days
85.7M
Workspaces
70%
Simulated demo data
What you can do

What teams build with MySQL

MySQL on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.

01

Orders and revenue

Daily orders, AOV and refunds straight from your shop tables, refreshed every 15 minutes.

AOV · daily
02

Customer cohorts

Retention curves by signup month and country, without exporting a single CSV.

Monthly cohorts
03

Join with support and CRM

Connect customers to Zendesk tickets and HubSpot deals to see the full account picture.

customers ⋈ tickets
Objects & tables

Exactly what gets synced

Kimo maps MySQL into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.

4 tables · 17 fields

shop.customers

Incremental (CDC)≈ 402,000 rows
FieldTypeNotes
ididPrimary key
emailstring
countrystring
created_attimestampIncremental cursor
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model

From raw MySQL tables to a certified metric

This model ships with the Business Intelligence demo. Open it to see every join and measure.

Customer support

Zendesk tickets joined to accounts: volume, SLA and CSAT by plan.

In the demo
  • Zendesk
    tickets
  • MySQL
    organizations
Model
org_id = id
Measuresticketsfirst_responsecsat
Tickets · last 30 days
169+2.0% wk/wk

Fictional data · hover the chart for daily values

Setup

Connect MySQL in 10 min

No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.

  1. 1

    Create a read-only user

    Grant SELECT only. Kimo never writes to your database.

  2. 2

    Open network access

    Allow Kimo’s static egress IPs, use an SSH tunnel, or run the on-prem agent inside your network.

  3. 3

    Enter connection details

    Credentials are encrypted at rest with a per-workspace key and tested before saving.

  4. 4

    Select tables

    Choose what to sync, starting with shop.customers. Kimo backfills, then keeps it fresh.

Create a read-only user
CREATE USER 'kimo_reader'@'%' IDENTIFIED BY '<generated>';
GRANT SELECT, REPLICATION CLIENT, REPLICATION SLAVE
  ON *.* TO 'kimo_reader'@'%';
FLUSH PRIVILEGES;

Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.

Connect MySQL
Step 2 of 3 · Kimo demo workspace
  • Reaching host
  • Authenticating
  • Reading schema
Read-only access
Illustration only · placeholder values, never real secrets
FAQ

MySQL questions, answered

By default Kimo syncs MySQL every 15 min. You can change the schedule per table, or trigger a sync manually from the connector page.

MySQL · Read-only credentials · Every 15 min

See your MySQL data in Kimo in 10 min.

Try it on the live demo workspace first, then connect your own account when you are ready.

Request access