01
MRR you can audit
New, expansion, contraction and churn MRR, each traceable to the underlying invoices.
MRR movements
FinanceBeta
Paddle + Kimo
Merchant-of-record subscriptions and tax. Turn invoices, charges and subscriptions into MRR, retention and margin that match your books.
- Auth
- API key
- Sync
- Hourly
- Setup
- ≈ 3 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / paddleSyncing
Sync loghourly
- Succeeded:invoices+1,590 rowsnow
- Succeeded:accounts+809 rows2m ago
- Succeeded:transactions+752 rows4m ago
- Succeeded:invoices+2,371 rows6m ago
Rows synced · 30 days
132.2M
Workspaces
4%
What you can do
What teams build with Paddle
Paddle on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Net revenue retention
Cohort NRR by plan and segment, refreshed automatically for the board pack.
NRR by cohort
03
Failed payment alerts
Catch spikes in failed charges or overdue invoices before they become churn.
Dunning watch
Objects & tables
Exactly what gets synced
Kimo maps Paddle into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 14 fields
Tables
invoices
Incremental≈ 2,530,000 rows| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| customer_id | id | References customer |
| amount_due | decimal | Measure |
| status | enum | Low-cardinality dimension |
| due_date | date | Incremental cursor |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw Paddle tables to a certified metric
A starter model Kimo suggests the moment Paddle is connected. Every join is editable.
Paddle · Recurring revenue
Invoices and subscriptions joined with accounts to produce MRR movements.
- Paddleinvoices
- PostgreSQLaccounts
- HubSpotdeals
Model
customer_id · account_id
Measuresmrrnew_customers
MRR · last 30 days
$227.1K+3.2% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect Paddle in 3 min
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
- 1
Create a read-only key in Paddle
Use a dedicated key scoped to read access, so it can be rotated independently.
- 2
Paste it into Kimo
Keys are encrypted with a per-workspace key and never shown again.
- 3
Choose streams
Pick which objects to sync, starting with invoices.
- 4
Validate and sync
Kimo tests the key, backfills history and keeps it fresh (hourly).
Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
Connect Paddle
Step 2 of 3 · Kimo demo workspace
- Reaching host
- Authenticating
- Reading schema
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair Paddle with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
Paddle questions, answered
By default Kimo syncs Paddle hourly. You can change the schedule per table, or trigger a sync manually from the connector page.
Paddle · API key · Hourly
See your Paddle data in Kimo in 3 min.
Try it on the live demo workspace first, then connect your own account when you are ready.