Integrations

Category slots

How connecting works

1. 1Press Connect on a provider. OAuth providers send you to their consent screen; the rest ask for a key, with a link to the exact page that issues it.
2. 2Credentials are validated immediately. An invalid or over-privileged key is rejected at the door rather than stored and failing quietly later.
3. 3They are then encrypted and stored in a vault the browser cannot read. The dashboard only ever shows a masked preview.
4. 4A first sync runs straight away, so a connection either produces data or produces an error you can see — never a silent healthy badge.
5. 5Billing providers also get one webhook endpoint registered in your account, so payments and cancellations arrive as they happen.

After connecting

• Sync cadence. A cron job refreshes every connected source every 30 minutes. Billing webhooks trigger an extra sync on the events that matter.
• Freshness. Each provider has its own staleness window — six hours for billing, two for error and infrastructure sources, a day for Search Console. Past it, the source stops counting toward the score.
• Healthy is earned. A provider only shows healthy after a sync actually succeeded.
• Disconnecting deletes the stored credentials, removes the webhook endpoint Seiton created, and strips the fields that provider owned out of your snapshots. Revoking access at the provider works too — you do not need us to complete it.

Every provider

StripeSubscriptions, invoices, failed payments, and churn.PaddlePaddle Billing subscriptions and transactions.PolarPolar orders and subscriptions.Lemon SqueezyLemon Squeezy store subscriptions and orders.Dodo PaymentsDodo Payments subscriptions and payments (read-only key).EasytoolsEasytools checkout and subscriptions. Built on Stripe — do not double-count.Google Search ConsoleOrganic clicks, impressions, and ranking movement.SentryError volume, crash-free rate, checkout exceptions.VercelDeployments, build failures, and hosting health. Optional.SupabaseDatabase, Auth, Storage, and Realtime health. Optional — not a table browser.Seiton AnalyticsCookieless visitors and pageviews from the Seiton snippet. Owns traffic when live.PostHogProduct activity from HogQL. Owns Product Health when connected. Fills traffic only if the snippet and GA4 are empty.Google Analytics 4Acquisition and traffic from GA4. Owns traffic when the Seiton snippet is empty. Does not own Product Health.CloudflareCloudflare edge 5xx rate. Request volume is not unique visitors.GitHubCompleted GitHub Actions workflow success and failure rate for one selected repository.LinearIssue tracker context. Not a product-engagement sensor.HubSpotCRM connection. Contacts are not paying customers and do not feed billing metrics.ResendCustomer email API. Domain inventory is not product engagement and is not Seiton's mailer.SlackMorning briefing and alerts. Output only — not a health data source.DiscordAlert delivery into a Discord channel. Output only.EEmailDaily founder briefing by email. Configure recipients under Settings → Reports.

Registered but not connectable yet