Skip to main content
Federated Analytics in SyneHQ lets you run a single SQL query across multiple databases and file sources—no data movement required. It’s powered by Tangent Lake (DuckDB under the hood) and works with your existing connections.

​
Why federated analytics?

  • One query, many sources: Join Postgres, MySQL, SQLite, DuckDB files, even CSV/JSON
  • Zero ETL: Analyze live data without pipelines
  • Faster iteration: Explore, validate, and answer questions quickly
  • Governed access: Uses SyneHQ connections, RBAC, and auditing

​
Get started in minutes

Create a Tangent

Build a federated workspace using your existing connections

How it works

DuckDB ATTACH, planning, and orchestration explained

SQL examples

Copy‑paste queries for cross‑database joins and metrics

​
Example: Postgres + MySQL

SELECT u.id, u.name, SUM(o.amount) AS revenue
FROM postgres_db.public.users u
JOIN mysql_db.sales.orders o ON u.id = o.user_id
GROUP BY u.id, u.name
ORDER BY revenue DESC
LIMIT 10;
This runs live—DuckDB fetches only the data needed and performs the join. No exports or imports.

​
Common patterns

SELECT DATE_TRUNC('month', o.created_at) AS month, SUM(o.amount) AS revenue
FROM mysql_db.sales.orders o
GROUP BY month
ORDER BY month;

SELECT u.email, c.last_login
FROM postgres_db.public.users u
JOIN read_csv_auto('https://example.com/logins.csv') c
  ON u.email = c.email;

CREATE TABLE top_customers AS
SELECT u.id, u.name, SUM(o.amount) AS revenue
FROM postgres_db.public.users u
JOIN mysql_db.sales.orders o ON u.id = o.user_id
GROUP BY u.id, u.name
ORDER BY revenue DESC
LIMIT 100;

​
How it works (at a glance)

  • Tangent session: Selected connections are attached into a DuckDB session
  • Federated planning: Filters and projections are pushed down to sources
  • Minimal movement: Only necessary data is pulled to complete the query
  • Extensible: Supports Postgres, MySQL, SQLite, files (CSV/JSON/Parquet), and more

Tangent Lake Overview

The federated query lake behind Federated Analytics

Local connections

Query private/on‑prem data with a secure tunnel

​
Tips

  • Start with smaller result sets; expand once logic is correct
  • Use explicit aliases for clarity across engines (e.g., pg_, mysql_)
  • Materialize intermediate results only when needed (for repeat jobs)
  • Monitor source credentials and permissions (least‑privilege recommended)
Federated Analytics is available in SaaS and enterprise self‑hosted. For large/regulated environments, contact us for sizing and rollout guidance.
⌘I