# Spend, credit, and market data in one query Source: https://www.hotdata.dev/industries/fintech Site index: https://www.hotdata.dev/llms.txt Join transactions, payments, and market data across every source in milliseconds, without touching production. ## How data flows Data comes from: - Operational database - Payment processor - Data lake Hotdata runs in your VPC (Cross-source joins, Forks, Audit trail), and the data is used by: - Analysts - Risk models - Internal apps ## Common workloads - **Spend and expense analytics.** Roll up card and expense activity by company, team, and category, and flag spend that breaks policy. - **Credit decisions.** Pull an applicant's full history in one query, so decisions come fast. 9×: Faster than ClickHouse, on the same hardware. - **Research on market data.** Run many research queries over years of market data at once, with no one waiting. 5×: Faster than Snowflake, with 10 concurrent clients. - **Collections and payables.** Track what each customer owes and has paid, including installments, and what each partner is owed. - **Reconciliation and reporting.** Match records against processor and bank data, and flag the ones that disagree. [16×: Bigger Snowflake warehouse, still slower than Hotdata.](/blog/benchmarking-concurrency-on-hotdata-snowflake-and-bigquery#sizing-and-cost-implications) ## How Hotdata fits - **Many queries at once.** With 10 concurrent clients, Hotdata runs 5× faster than Snowflake. - **One SQL surface across sources.** Join operational databases, payment processors, and lake tables in one query, written in PostgreSQL, DuckDB, Snowflake, or ClickHouse SQL. See [HotSQL](/docs/sql). - **Production stays untouched.** Read-only access to production, isolated environments, and a full audit trail. - **Forks for reproducible work.** Fork a database before a close or a research run, so every result traces back to its data. See [Forking a database](/docs/cli-reference#fork-a-database). - **Corrections without full reloads.** Upserts, updates, and deletes apply refunds and status changes without a full reload. See [Load modes](/docs/push-data#load-modes). - **Control over heavy queries.** Run long queries in the background and reuse stored results. See [Query runs](/docs/api-reference/query-runs). ## Get started The [quick start](/docs/quick-start) gets a table into Hotdata in a few minutes.