Real-time
Real-time sync
Changes in ClickHouse or Crustdata instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ CRM
ClickHouse to Crustdata integration — real-time data sync
Keep ClickHouse and Crustdata in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect ClickHouse and Crustdata
Flow Crustdata data into ClickHouse in real time — no exports, no schedulers, no custom scripts.
Crustdata is a read-only source: Stacksync reads its data in real time and delivers it into ClickHouse, so ClickHouse always reflects the current state of Crustdata — without exports, scripts, or schedulers.
The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.
Stacksync does both with one connection. Tech Stack, Screener Results, Enrichment Responses, Companies from Crustdata land in ClickHouse as live tables, updated within seconds, and columns computed in ClickHouse write back to fields in Crustdata. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Common use cases
- 01 Append enrichment at lead-capture time so new records arrive scored and routable.
- 02 Enrich CRM accounts with firmographics, headcount growth, and tech stack so scoring and routing run on complete data.
- 03 Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.
- 04 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
Common sync patterns
CRM analytics on live data
Accounts, contacts, and activity from Crustdata are queryable in ClickHouse moments after they change, so dashboards stop lagging the reality they describe.
Scores and segments back on the record
Lead scores, churn risk, or usage segments computed in ClickHouse appear as fields in Crustdata, where the people working accounts actually see them.
A single customer view
Join Crustdata's relationship data with billing, product, and support data in ClickHouse to build the customer picture the CRM alone cannot hold.
What you can sync between ClickHouse and Crustdata
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| ClickHouse objects | Crustdata objects | How this pairing syncs | |
|---|---|---|---|
| Distributed tables Query-routing tables over cluster shards in self-managed deployments. | Enrichment Responses Real-time enrichment lookups keyed by domain or profile URL; read to append fresh firmographic and contact data at form-fill or record-creation time. | Distributed tables is specific to ClickHouse and Enrichment Responses to Crustdata — each maps to any object or custom field on the other side. | |
| Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. | Companies Firmographic records — industry, size, funding, growth signals; read out to enrich CRM accounts and warehouse company tables. | Dictionaries is specific to ClickHouse and Companies to Crustdata — each maps to any object or custom field on the other side. | |
| Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. | People Contact and profile data for decision-makers; read into a CRM or outreach tool to fill missing titles, emails, and LinkedIn profiles. | Tables (MergeTree family) is specific to ClickHouse and People to Crustdata — each maps to any object or custom field on the other side. | |
| Databases Namespaces that group tables and scope permissions for sync users. | Headcount and Growth Metrics Time-series employee counts by department and region; read to score accounts on hiring momentum and expansion signals. | Databases is specific to ClickHouse and Headcount and Growth Metrics to Crustdata — each maps to any object or custom field on the other side. | |
| Views Saved queries used as curated, read-only sync sources. | Tech Stack Detected technologies per company; read to build segments and route accounts by the tools they already use. | Views is specific to ClickHouse and Tech Stack to Crustdata — each maps to any object or custom field on the other side. | |
| Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. | Screener Results Saved company searches with filter criteria; read on a schedule so target-account lists in the CRM refresh as companies enter the criteria. | Materialized views is specific to ClickHouse and Screener Results to Crustdata — each maps to any object or custom field on the other side. |
How changes propagate between ClickHouse and Crustdata
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
ClickHouse Crustdata Interval-based propagation
DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.
DeliveryCrustdata does not accept inbound record writes, so this direction carries requests rather than records: Crustdata's output flows back as field updates on the originating ClickHouse records.
Crustdata ClickHouse Interval-based propagation
DetectionStacksync polls Crustdata for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: real-time enrichment endpoints for on-demand lookups plus periodic re-pulls of screeners and datasets.
DeliveryEach detected change is applied to ClickHouse as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Crustdata: Requests are metered by plan credits and per-minute rate limits; bulk dataset pulls are the efficient path for large refreshes rather than per-record enrichment calls.
What ships with ClickHouse ⇄ Crustdata
Connect ClickHouse and Crustdata for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ClickHouse–Crustdata connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever ClickHouse or Crustdata data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single ClickHouse or Crustdata record.
Observability
Monitoring
Track your ClickHouse ⇄ Crustdata sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between ClickHouse and Crustdata.
How the ClickHouse and Crustdata connectors work
ClickHouse
- Integration surface
- Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
- Authentication
- Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
- Change detection
- No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
- Capabilities
- read · write
Crustdata
- Integration surface
- REST API (JSON)
- Authentication
- API token — Authorization: Token header issued per workspace
- Change detection
- Pull-based: real-time enrichment endpoints for on-demand lookups plus periodic re-pulls of screeners and datasets; no webhooks or change feed
- Capabilities
- read
- Rate limits
- Requests are metered by plan credits and per-minute rate limits; bulk dataset pulls are the efficient path for large refreshes rather than per-record enrichment calls.
How it works
How to connect ClickHouse to Crustdata — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate ClickHouse and Crustdata with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
ClickHouse
connected
Crustdata
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the ClickHouse and Crustdata objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · ClickHouse ⇄ CrustdataCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
ClickHouse CrustdataCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
ClickHouse and Crustdata integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between ClickHouse and Crustdata — Crustdata is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Crustdata: Company records key naturally off domain and people records off profile URL, which makes idempotent upserts into a CRM straightforward. ClickHouse: It exposes both a native TCP protocol and an HTTP interface, and can additionally speak MySQL and PostgreSQL wire protocols for compatibility with existing drivers. Stacksync's field mapping accounts for these differences between ClickHouse and Crustdata without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means ClickHouse and Crustdata records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed ClickHouse and Crustdata connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom ClickHouse–Crustdata integration in-house.
-
Yes — Stacksync ships production-grade connectors for both ClickHouse and Crustdata. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on ClickHouse: No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source. On Crustdata: Pull-based: real-time enrichment endpoints for on-demand lookups plus periodic re-pulls of screeners and datasets; no webhooks or change feed. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 338 integrations available for ClickHouse and Crustdata.
Popular · 4 of 338
No integrations match .
