Let your team use AI on real customer data, safely
Rig gives every person and every AI agent its own permissions on your warehouse, hides the fields they should not see, and logs every question asked. Fraud and disputes get their case context in minutes instead of an hour, and nobody has to hand out database credentials to make it happen.
// In plain terms
Rig is AI-native data infrastructure. Think Stripe or Vercel, but for data.
We connect all your sources, build a brain that sits on top of them, and let your team and your AI tools reach that data safely. For a fintech that means fraud, disputes, ops and finance can each ask the warehouse a question directly, see only the fields their role allows, and leave an audit trail behind every one.
// What you'd build
What a fintech builds first
These are projects, not features. Fintechs were already careful about who could reach customer data; what changed is that the people who cannot get access now have Claude and ChatGPT open in another tab, and the path of least resistance is to paste data into one of them.
Dispute and chargeback evidence packs
Every case assembled in one pass: the transaction and its history, the customer's prior disputes, the support contacts around it, and the device and session context. This is the job that took Cleo's analysts 30 to 60 minutes per case before anyone could decide anything.
Your warehouse · Stripe · Zendesk · Intercom
KYC and onboarding review queue
Verification outcomes ordered by risk rather than by arrival, so analysts spend the day on the cases that need judgment instead of clearing the ones that never did.
Sumsub · Your warehouse
Approval-rate diagnostics
Why approvals moved last week, cut by segment, cohort and channel, against the rule and model changes that shipped in the same window. The question every payments and lending team asks and few can answer the same day.
Your warehouse
Repayment risk and limit alerts
Cohorts drifting off plan before they reach collections, and limit changes surfaced as alerts rather than found in a monthly review. Two of the things Cleo's finance and disputes teams built.
Your warehouse · Stripe
Fraud rule performance and false positives
How each rule actually performs: what it catches, what it costs in good customers declined, and which rules have quietly stopped earning their place.
Your warehouse
Support quality and escalation patterns
Every conversation reviewed rather than a 2% sample, with escalation patterns and weekly summaries surfaced automatically. Cleo runs conversation-quality reviews and escalation tracking this way.
Zendesk · Intercom · Front
Channel and campaign performance
Spend against the accounts it actually acquired and what those accounts went on to be worth, rather than against platform-reported conversions. Cleo built top-performing ad detection and channel reviews on this.
Meta Ads · Google Ads · Your warehouse
Per-agent access and audit
Each person and each AI agent scoped to its own role, queries running in a sandbox rather than against the raw database, PII masked by policy, and a full log of who asked what. The part that makes the rest of this list allowable.
Rig MCP · Claude · ChatGPT · Cursor
// In production
"Every team has a Rig agent now. Ops, support, fraud, marketing. We stopped being the bottleneck."
Cleo, consumer fintech, Series C
- 16 weeks from a fraud-team pilot to org-wide
- Seats went from 37 to 204 over three months
- Five functions actively building, from three analysts automating data documentation to roughly 200 business users automating data-heavy work
- Loan limit alerts, repayment risk warnings, dispute backlog triage, campaign tracking, OKR progress and conversation-quality reviews all running on the same layer
What we are not going to claim
Two things are worth saying plainly, because you will find them out in procurement anyway and we would rather it came from us.
There is no fintech connector suite. We connect the commercial stack you run around the product, plus Sumsub for KYC, but there is no core banking, ledger, card issuing or lending connector in the catalogue. Rig's place in a fintech is on top of the warehouse your product data already lands in, which is how Cleo runs it.
And on compliance: SOC 2 Type II is in progress rather than held, and we do not hold ISO 27001. PII masking is applied by policy rather than on by default, so classifying columns and setting those policies is a real part of onboarding. The mechanisms are there, the certification is not yet, and your risk team should hear that before they see a demo.
// Proof
Cleo runs on Rig, and so do these
Cleo is the fintech, running Rig across five functions on its own warehouse. It is the only one so far, which is why the rest of the wall is labelled with what those companies actually do rather than left to imply otherwise.
Consumer fintech
Sustainable oral care
Food and supplements
Homecare software
Online education
Workplace management
Hospitality tech
K-12 school software// Built on Rig
What fintech teams build on Rig
Real examples assembled from Rig's building blocks, running on the warehouse your product data already lands in.
Account health & expansion
One health score across product, support and finance
A live account health view that blends usage, support load and revenue signals to flag churn risk early and surface the accounts ready to expand.
Investor & board reporting
Auto-assemble the board pack from source data
Generate the monthly board and investor update straight from finance, product and CRM data, with the numbers and commentary built in minutes, not days.
minutes, not daysSelf-serve dashboards
Let anyone build a custom dashboard in plain English
Business teams ask for the report they need and Rig builds a governed, custom dashboard on your modelled data, so the data team stops being a ticket queue.
CleoCommon questions
Almost certainly not, and we would rather say so. The catalogue covers the commercial stack a fintech runs (Stripe, CRM, support, ads, finance tools) plus Sumsub for KYC, but there is no core banking, card issuing or lending connector. That is not usually the blocker, because your product data already lands in your own warehouse. Rig sits on top of that warehouse, which is exactly how Cleo runs.
SOC 2 Type II is in progress, not held, and we do not hold ISO 27001 or a financial services accreditation. Data can stay in your own warehouse so it never moves to us, or you can use EU-based Rig hosting. The security page carries the current status, and we are happy to walk your risk team through it on a call rather than have you take a badge on a landing page at face value.
Access is role based per person and per agent, queries run in a sandbox rather than against the raw database, PII columns can be classified and masked by policy, and every query is logged for audit. Worth knowing before you scope a rollout: masking is applied by policy rather than on by default, so classifying your PII columns and setting those policies is part of onboarding, not something that happens automatically.
At Cleo, a consumer fintech at Series C, fraud and dispute analysts had been spending 30 to 60 minutes assembling context per case before they could decide anything. Rig built a self-healing context layer over a 4,000-table warehouse, and the rollout went from a fraud-team pilot to org-wide in 16 weeks, with seats going from 37 to 204 and five functions building on it.
No, it removes them from the request queue. Cleo's own framing was going from three analysts automating data documentation to roughly 200 business users automating data-heavy work. The data team still owns the definitions and the access policy, which is the part that actually needs judgment.
That is close to Cleo's exact number, and Novakid runs 5,000+. The context layer is generated from the warehouse rather than hand-written, and it re-derives as the schema drifts, which is the only reason a warehouse that size stays documented at all.
Give the tools your team already uses a governed door
Bring your warehouse and your access rules. We'll show you what the context layer builds over them.