Real-time
Two-way sync
Changes in Box or Dremio instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Data warehouse
Box to Dremio integration — real-time, two-way sync
Keep Box and Dremio 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 Box and Dremio
Bridge query-ready tables and stored files: Dremio and Box keep the same records in step, in real time, in both directions.
Dremio keeps the tables and query results a business reports on; Box keeps the raw files, documents, and objects that the same business produces and shares. The two overlap wherever a dataset lives as both — a file dropped in Box that has to become rows in Dremio, or a result in Dremio that people downstream need back as a file in Box. When that overlap is bridged by manual export and import or an overnight job, one side spends the day working from a stale copy.
Stacksync syncs Apache Iceberg tables, Spaces and folders, Reflections, Jobs in Dremio with Events, Files, Folders, Metadata in Box field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Reverse-ETL aggregates computed over lake data out to CRMs and finance tools for business users.
- 02 Publish operational database tables into Iceberg via Dremio so the lakehouse reflects current application state.
- 03 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
- 04 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
Common sync patterns
Where Dremio computes the labels: push them onto the files
Classifications, scores, or status derived in Dremio are written back onto the matching Events, Files, Folders, Metadata in Box as metadata or tags, so the file store reflects what analytics decided.
Where Box receives the raw files: land them as query-ready rows
Files and exports that arrive in Box are parsed into Apache Iceberg tables, Spaces and folders, Reflections, Jobs in Dremio as they land, so analysts query current data instead of waiting on the next scheduled load.
Where Box is the shared drive: publish results back as files
Curated tables and query results from Dremio are written to Box as files the rest of the business can open, keeping the shared copy current without a hand-run export.
What you can sync between Box and Dremio
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.
| Box objects | Dremio objects | How this pairing syncs | |
|---|---|---|---|
| Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. | Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. | Folders is specific to Box and Sources to Dremio — each maps to any object or custom field on the other side. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. | Metadata is specific to Box and Physical datasets to Dremio — each maps to any object or custom field on the other side. | |
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. | Collaborations is specific to Box and Virtual datasets (views) to Dremio — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads. | Users is specific to Box and Apache Iceberg tables to Dremio — each maps to any object or custom field on the other side. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Spaces and folders Namespaces that organize virtual datasets and govern access. | Groups is specific to Box and Spaces and folders to Dremio — each maps to any object or custom field on the other side. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Reflections Materialized accelerations that make repeated extraction queries cheaper. | Tasks is specific to Box and Reflections to Dremio — each maps to any object or custom field on the other side. |
How changes propagate between Box and Dremio
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.
Box Dremio Sub-second propagation
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is applied to Dremio as a row-level write, with types converted between the two schemas.
Dremio Box Interval-based propagation
DetectionStacksync polls Dremio for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL.
DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
- Dremio: Bounded by engine capacity and workload management rather than API rate limits.
What ships with Box ⇄ Dremio
Connect Box and Dremio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Dremio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Dremio 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 Box or Dremio record.
Observability
Monitoring
Track your Box ⇄ Dremio sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Box and Dremio.
How the Box and Dremio connectors work
Box
- Integration surface
- REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
- Authentication
- OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
- Change detection
- V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
- Capabilities
- read · write · webhooks
- Rate limits
- Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
Dremio
- Integration surface
- Arrow Flight SQL, JDBC/ODBC, and a REST API
- Authentication
- Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
- Change detection
- Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
- Capabilities
- read · write
- Rate limits
- Bounded by engine capacity and workload management rather than API rate limits
How it works
How to connect Box to Dremio — 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 Box and Dremio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Box
connected
Dremio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Dremio 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 · Box ⇄ DremioCustomers 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.
Box DremioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Dremio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Dremio: authenticate both systems, choose the objects to sync (such as Box's Folders and Metadata), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Dremio side: Apache Iceberg tables, Spaces and folders, Reflections, Jobs, plus custom fields where Dremio exposes them. On the Box side: Events, Files, Folders, Metadata. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Box and Dremio: Where Dremio computes the labels: push them onto the files; Where Box receives the raw files: land them as query-ready rows; Where Box is the shared drive: publish results back as files. Classifications, scores, or status derived in Dremio are written back onto the matching Events, Files, Folders, Metadata in Box as metadata or tags, so the file store reflects what analytics decided.
-
Box: REST API (api.box.com/2.0), plus the Events API and V2 Webhooks. Authentication: OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing. Dremio: Arrow Flight SQL, JDBC/ODBC, and a REST API. Authentication: Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud. Stacksync manages authentication, retries, and rate limits on both sides.
-
Dremio: Dremio queries data in place on lake storage (S3, ADLS, HDFS) rather than ingesting it, so syncs read through Dremio to underlying files and Iceberg tables. Box: The user Events API is consumed with a stream_position and long-polling; enterprise/admin events retain roughly one year of history and can lag strict ordering for near-real-time reads. Stacksync's field mapping accounts for these differences between Box and Dremio without custom code.
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
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 425 integrations available for Box and Dremio.
Popular · 7 of 425
-
Box ⇄ BigQuery -
Box ⇄ MotherDuck -
Box ⇄ Databricks -
Box ⇄ AWS S3 -
Dremio ⇄ Egnyte -
Dremio ⇄ Amazon S3 -
Dremio ⇄ Sharepoint
No integrations match .
