Skip to content
AI ⇄ Database

Azure OpenAI to Citus integration — real-time data sync

Keep Azure OpenAI and Citus 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 Azure OpenAI and Citus

Sync the records in Citus into Azure OpenAI and land its embeddings, classifications, and generated fields back on the same rows, in real time and without a pipeline to maintain.

Azure OpenAI is a read-only source: Stacksync reads its data in real time and delivers it into Citus, so Citus always reflects the current state of Azure OpenAI — without exports, scripts, or schedulers.

AI systems do not hold customers or invoices the way business apps do. What they hold is derived from your data: the vectors and metadata in a vector store, or the classifications, extracted fields, and generated text a model produces over records it was given. Citus is where those source records actually live. The bridge between the two is the row itself, since an item in Azure OpenAI and the record in Citus it describes are two halves of the same thing, and they drift the moment one is updated without the other.

Stacksync syncs Reference tables, Local tables, Schemas, Views in Citus with Fine-tuning jobs, Files, Batch jobs, Usage and quota in Azure OpenAI in real time. Rows created or changed in Citus flow into Azure OpenAI so inference and embedding run on current data, and the scores, labels, and generated fields Azure OpenAI produces flow back onto the matching rows in Citus, mapped field by field. A change on either side appears on the other within seconds, with no extraction job or webhook plumbing to keep alive.

Because matching is by a stable identifier, every row in Citus stays tied to its AI-side counterpart in Azure OpenAI. Retrieval, enrichment, and generated content always resolve back to the record they came from, so there are no orphaned vectors and no labels describing a version of a row that no longer exists.

Common use cases

  • 01 Pull per-deployment TPM/RPM usage into a warehouse for FinOps chargeback and quota-exhaustion alerting.
  • 02 Mirror Assistants and Vector stores configuration into a database as an auditable inventory of retrieval assets and their linked files.
  • 03 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
  • 04 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.

Common sync patterns

Write results back onto the record

Scores, labels, extracted fields, or generated text produced in Azure OpenAI land on the matching row in Citus, next to the source data your applications already query.

Keep derived data fresh as sources change

When a row in Citus is updated or removed, its counterpart in Azure OpenAI is updated or removed too, so nothing in Azure OpenAI describes a record that has since changed or gone.

Backfill once, then stay in step

Load your existing rows from Citus into Azure OpenAI to build the index or enrichment set, then let ongoing changes sync automatically instead of re-running the whole job.

What you can sync between Azure OpenAI and Citus

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.

Azure OpenAI objects Citus objects How this pairing syncs
Fine-tuning jobs Training jobs with status, base model, hyperparameters, and result files; status is polled from queued through succeeded or failed. Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Fine-tuning jobs is specific to Azure OpenAI and Schemas to Citus — each maps to any object or custom field on the other side.
Files Uploaded training, validation, and batch-input files plus generated output files; listed and read by ID, not written back in sync. Views Curated projections over distributed data, often used as read-only sync sources. Files is specific to Azure OpenAI and Views to Citus — each maps to any object or custom field on the other side.
Batch jobs Asynchronous bulk-inference jobs; status and output-file IDs are polled to completion to drive downstream pipeline triggers. Sequences Key generators that matter when external writes must not collide with application inserts. Batch jobs is specific to Azure OpenAI and Sequences to Citus — each maps to any object or custom field on the other side.
Usage and quota Per-deployment TPM/RPM consumption and remaining quota, read from usage endpoints and Azure Monitor for cost and throttling reporting. Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Usage and quota is specific to Azure OpenAI and Distributed tables to Citus — each maps to any object or custom field on the other side.
Assistants Persistent assistants (preview) with instructions, tools, and linked files; read as configuration inventory, not authored via sync. Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Assistants is specific to Azure OpenAI and Reference tables to Citus — each maps to any object or custom field on the other side.
Vector stores File collections (preview) backing file-search retrieval; read as metadata such as name, file counts, and status. Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Vector stores is specific to Azure OpenAI and Local tables to Citus — each maps to any object or custom field on the other side.

How changes propagate between Azure OpenAI and Citus

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.

Azure OpenAI Citus Interval-based propagation

DetectionStacksync polls Azure OpenAI for changes on an incremental schedule, reading only records changed since the previous pass. Polling: list endpoints plus GET on job IDs for status.

DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.

Citus Azure OpenAI 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.

DeliveryAzure OpenAI does not accept inbound record writes, so this direction carries requests rather than records: Azure OpenAI's output flows back as field updates on the originating Citus records.

Rate-limit considerations

  • Azure OpenAI: Per-deployment TPM and RPM limits (about 6 RPM per 1000 TPM), scoped by region and subscription; control-plane ARM calls throttle separately.
What ships with Azure OpenAI ⇄ Citus

Connect Azure OpenAI and Citus for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure OpenAI–Citus connection.

Real-time

Real-time sync

Changes in Azure OpenAI or Citus instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure OpenAI or Citus 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 Azure OpenAI or Citus record.

Observability

Monitoring

Track your Azure OpenAI ⇄ Citus sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure OpenAI and Citus.

How the Azure OpenAI and Citus connectors work

Azure OpenAI

Integration surface
REST data-plane (inference + authoring) and Azure Resource Manager control-plane
Authentication
API key in the api-key header, or a Microsoft Entra ID bearer token / managed identity
Change detection
Polling: list endpoints plus GET on job IDs for status; no webhooks or change feed. Fine-tuning and batch jobs expose queued/running/succeeded states.
Capabilities
read
Rate limits
Per-deployment TPM and RPM limits (about 6 RPM per 1000 TPM), scoped by region and subscription; control-plane ARM calls throttle separately.

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
How it works

How to connect Azure OpenAI to Citus — 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.

  1. 01

    Connect your apps

    Authenticate Azure OpenAI and Citus with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure OpenAI connected
    Citus connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure OpenAI and Citus 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure OpenAI ⇄ Citus
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure OpenAI Citus
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure OpenAI and Citus integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 405 integrations available for Azure OpenAI and Citus.

Popular · 7 of 405
All Azure OpenAI integrations All Citus integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own