Connect once. Query forever.
Arcus starts warehouse-first with BigQuery, Snowflake, and Postgres. When the metric only lives in a source app, scoped Pipedream connections can provide first-party data, and Copass keeps the source context, snapshots, and evidence trail together.
Speaks your business, not your schema.
Most tools ask you to translate "active customer" into a table join every time. Arcus learns it once. Define active_customer, paid_cohort, north_star — Arcus uses your definitions, every time.
- Configurable by tenant. Arcus uses the business definitions approved for each workspace.
- Reviewable changes. Metric definitions should have owners, notes, and a change trail.
- Existing models welcome. dbt and BI metadata can inform setup when available, but launch scope is reviewed case by case.
Trace every number to its source row.
"Where did this number come from?" Click. See the chain Arcus used: answer, metric, SQL or source request, warehouse table or connected account, Copass context, and available source evidence. Freshness checks depend on the fields and metadata connected during setup.
- Answer lineage. Across warehouse queries, source-native pulls, Copass memory, and answer artifacts.
- Freshness checks. Set expectations per source and flag stale warehouse tables.
- Schema drift review. Column changes can be flagged when metadata coverage supports it.
Row-level access. Audit-ready.
Arcus is designed around tenant isolation, read-only warehouse access, and application-level permission checks. Row-level and role-specific policies are scoped during setup and must match the customer's warehouse model.
- Warehouse-aware permissions. Launch setup uses read-only roles and tenant-scoped application access.
- Row-level rules. Scoped during pilot; not assumed as public self-serve.
- Audit log. Query and access history are captured for review; SIEM export is contract scope.
When the source is outside the warehouse, route it.
Pipedream, Copass ingestion, file drops, and custom APIs are scoped by tenant, source, auth model, evidence needs, and security review. Arcus should tell users which path is authoritative for each answer.
Source-native pulls when needed.
Pipedream-backed app accounts can be authoritative first-party data when the tenant has no warehouse table for that metric.
Evidence snapshots into memory.
Useful source summaries, onboarding docs, and citations can be ingested into Copass so Arcus has durable context without overriding SQL or source-native facts.
Write a query. Save it as context.
Sometimes raw SQL is the answer. Save reviewed queries as reusable context when that fits the tenant's semantic layer and evidence model.
The boring layer that makes everything else magic.
Connect a warehouse, scoped app account, or Copass source. Use guided setup when source coverage, permissions, citations, or semantics need review.