Real-time
Two-way sync
Changes in Citus or Egnyte instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Storage
Citus to Egnyte integration — real-time, two-way sync
Keep Citus and Egnyte 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 Citus and Egnyte
Keep Citus and Egnyte in step: a row in Citus for every file in Egnyte, with names, paths, metadata, and status staying consistent in real time, in both directions.
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 Citus says a file exists and carries its name, location, and status, while Egnyte 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 Distributed tables, Reference tables, Local tables, Schemas in Citus with Files, Folders, Users, Groups in Egnyte 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.
Common use cases
- 01 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
- 02 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- 03 Two-way sync of Files and Folders between Egnyte and an operational database or another content store, keeping the folder hierarchy aligned.
- 04 Write custom Metadata such as classification tags and project fields onto Files and Folders from a governance or DMS system, and read it back for reporting.
Common sync patterns
A queryable index of the file store
Every file or object in Egnyte shows up as a row in Citus, 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.
File metadata kept in step
Tags, custom properties, owner, or status columns edited on a row in Citus write back to the matching file's metadata in Egnyte, and metadata changed in Egnyte updates the row, so the two never disagree about a file.
Records that point at documents
Where a record in Citus references a file in Egnyte, 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.
What you can sync between Citus and Egnyte
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.
| Citus objects | Egnyte objects | How this pairing syncs | |
|---|---|---|---|
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Files File content managed via the fs-content endpoint (upload/download, chunked for large files); synced two-way with other stores. | Distributed tables is specific to Citus and Files to Egnyte — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Folders Folder hierarchy managed via the fs endpoint (create, move, rename, delete); the tree structure is mirrored during sync. | Reference tables is specific to Citus and Folders to Egnyte — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Users Accounts managed via the Users API; provisioned, updated, and deactivated in sync with an HRIS or identity provider. | Local tables is specific to Citus and Users to Egnyte — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Groups Groups and membership managed via the Groups API; kept aligned with directory or IdP groups that drive folder access. | Schemas is specific to Citus and Groups to Egnyte — each maps to any object or custom field on the other side. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Permissions Folder permissions listed, set, and removed via the Permissions API; effective permission for a user/folder is computable. | Views is specific to Citus and Permissions to Egnyte — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Links Shared file and folder links created, listed, and revoked via the Links API; useful for governing and auditing external sharing. | Sequences is specific to Citus and Links to Egnyte — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Egnyte
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.
Citus Egnyte Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is written to Egnyte through its API, with automatic retries and rate-limit backoff.
Egnyte Citus Sub-second propagation
DetectionEgnyte notifies Stacksync of record changes through webhook events. Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata,.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Egnyte: Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request.
What ships with Citus ⇄ Egnyte
Connect Citus and Egnyte for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Egnyte connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Egnyte 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 Citus or Egnyte record.
Observability
Monitoring
Track your Citus ⇄ Egnyte sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and Egnyte.
How the Citus and Egnyte connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
Egnyte
- Integration surface
- REST Public API (pubapi/v1) with File System, Users, Groups, Permissions, Links, Metadata, Events, and Webhooks endpoints
- Authentication
- OAuth 2.0 scoped access tokens (Authorization Code or Implicit for partner apps, Resource Owner Password for internal apps, Refresh Token flow); token sent in the Authorization header
- Change detection
- Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata, permission, and comment events
- Capabilities
- read · write · webhooks
- Rate limits
- Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request
How it works
How to connect Citus to Egnyte — 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 Citus and Egnyte with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Citus
connected
Egnyte
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Egnyte 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 · Citus ⇄ EgnyteCustomers 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.
Citus EgnyteCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Egnyte integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Egnyte: authenticate both systems, choose the objects to sync (such as Citus's Distributed tables and Reference tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Citus side: Distributed tables, Reference tables, Local tables, Schemas, plus custom fields where Citus exposes them. On the Egnyte side: Files, Folders, Users, Groups. 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 Citus and Egnyte: A queryable index of the file store; File metadata kept in step; Records that point at documents. Every file or object in Egnyte shows up as a row in Citus, 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.
-
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Egnyte: REST Public API (pubapi/v1) with File System, Users, Groups, Permissions, Links, Metadata, Events, and Webhooks endpoints. Authentication: OAuth 2.0 scoped access tokens (Authorization Code or Implicit for partner apps, Resource Owner Password for internal apps, Refresh Token flow); token sent in the Authorization header. Stacksync manages authentication, retries, and rate limits on both sides.
-
Citus: Citus is a PostgreSQL extension, not a fork: clients connect with ordinary Postgres drivers and SQL, and the coordinator routes queries to shards. Egnyte: Default API keys are throttled to 2 requests/second and 1,000 calls/day; production volume requires contacting Egnyte to raise per-token limits. Stacksync's field mapping accounts for these differences between Citus and Egnyte 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 423 integrations available for Citus and Egnyte.
Popular · 7 of 423
-
Citus ⇄ Amazon S3 -
Citus ⇄ Box -
Citus ⇄ Sharepoint -
Egnyte ⇄ VoltDB -
Egnyte ⇄ YugabyteDB - Egnyte ⇄ Amazon DynamoDB
-
Egnyte ⇄ Reltio
No integrations match .
