Two-way sync
Changes in Box or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Keep Box and OCI Database (Oracle Cloud) in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in OCI Database (Oracle Cloud) says a file exists and carries its name, location, and status, while Box holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.
Stacksync syncs Tables, Views, Materialized views, Schemas in OCI Database (Oracle Cloud) with Events, Files, Folders, Metadata in Box bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.
Every file or object in Box shows up as a row in OCI Database (Oracle Cloud), with its name, folder or key, size, type, and modified date as columns, so the contents of the store can be listed, filtered, and joined like any other table.
Tags, custom properties, owner, or status columns edited on a row in OCI Database (Oracle Cloud) write back to the matching file's metadata in Box, and metadata changed in Box updates the row, so the two never disagree about a file.
Where a record in OCI Database (Oracle Cloud) references a file in Box, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.
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 | OCI Database (Oracle Cloud) objects | How this pairing syncs | |
|---|---|---|---|
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | Schemas Namespace boundaries that scope which objects a sync connection can access | Events is specific to Box and Schemas to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side. | |
| Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. | Sequences Key generators that matter when writing new rows from external systems | Files is specific to Box and Sequences to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side. | |
| 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. | PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place | Folders is specific to Box and PL/SQL procedures and packages to OCI Database (Oracle Cloud) — 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. | JSON collections Document-style storage in the converged engine, synced alongside relational tables | Metadata is specific to Box and JSON collections to OCI Database (Oracle Cloud) — 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. | Partitions Physical table subdivisions relevant when replicating large fact tables | Collaborations is specific to Box and Partitions to OCI Database (Oracle Cloud) — 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. | Tables The primary sync surface; rows are read and written directly over SQL | Users is specific to Box and Tables to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side. |
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.
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 OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.
DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.
DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–OCI Database (Oracle Cloud) connection.
Changes in Box or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Box or OCI Database (Oracle Cloud) data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Box or OCI Database (Oracle Cloud) record.
Track your Box ⇄ OCI Database (Oracle Cloud) sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Box and OCI Database (Oracle Cloud).
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.
Authenticate Box and OCI Database (Oracle Cloud) with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Box and OCI Database (Oracle Cloud) 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Box and OCI Database (Oracle Cloud): authenticate both systems, choose the objects to sync (such as Box's Events and Files), map fields visually, and changes propagate both ways in milliseconds — no code required.
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. OCI Database (Oracle Cloud): SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP. Authentication: Database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available. Stacksync manages authentication, retries, and rate limits on both sides.
OCI Database (Oracle Cloud): Autonomous Database connections commonly use mutual TLS with a downloaded client wallet, which differs from a plain host-and-port database setup. Box: Files and folders share the Box ID namespace but are distinct object types; the account root is always folder ID 0. Stacksync's field mapping accounts for these differences between Box and OCI Database (Oracle Cloud) 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 Box and OCI Database (Oracle Cloud) records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and OCI Database (Oracle Cloud) connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–OCI Database (Oracle Cloud) integration in-house.
Yes — Stacksync ships production-grade connectors for both Box and OCI Database (Oracle Cloud). The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 425 integrations available for Box and OCI Database (Oracle Cloud).