Real-time
Two-way sync
Changes in Active Directory or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Database
Active Directory to TimescaleDB integration — real-time, two-way sync
Keep Active Directory and TimescaleDB 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 Active Directory and TimescaleDB
Close the gap between your application data and your directory: TimescaleDB and Active Directory share users, groups, and access in real time, in both directions.
Active Directory is the system of record for who people are and what they can reach: users, the groups they belong to, and the applications assigned to them. TimescaleDB holds the operational data those same people show up in, whether an employee or member table that decides who should have an account at all, a customers list, or the rows an application checks before it authorizes an action. The two describe overlapping users and groups, and when a nightly export or a hand-run script is all that connects them, accounts lag joiners and leavers and the application authorizes against a stale picture of who has access.
Stacksync syncs Schemas, Hypertables, Chunks, Continuous Aggregates in TimescaleDB with Service principals & applications, Organizational units, Organizational contacts, Users in Active Directory field by field, in real time, and in both directions. You decide which system owns which fields, with the directory holding credentials and group membership and the database holding the source list of people who should exist at all, and Stacksync keeps every copy consistent, resolving conflicts by rules you set. A person added to a table becomes an account within seconds, a departure disables one just as fast, and the directory's users and groups are always present in your tables as ordinary rows.
Common use cases
- 01 Keep device or asset reference tables bi-directionally in sync between TimescaleDB and an ERP.
- 02 Consolidate metrics from several services into one hypertable to serve a single reporting layer.
- 03 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
- 04 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
Common sync patterns
Provision accounts from the source of truth
When a person is added to the employee, member, or customer table in TimescaleDB, Stacksync creates the matching user in Active Directory with the right attributes, so access starts from live data instead of a manual ticket.
Deprovision the moment the record changes
When someone is marked inactive or removed in TimescaleDB, the matching account in Active Directory is disabled within seconds, closing the window between a departure and a login that still works.
Read users and groups as ordinary tables
Users, groups, and their memberships from Active Directory land in TimescaleDB as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
What you can sync between Active Directory and TimescaleDB
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.
| Active Directory objects | TimescaleDB objects | How this pairing syncs | |
|---|---|---|---|
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | Schemas Postgres namespaces used to separate synced datasets by team or environment. | Devices is specific to Active Directory and Schemas to TimescaleDB — each maps to any object or custom field on the other side. | |
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. | Directory roles is specific to Active Directory and Hypertables to TimescaleDB — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. | Service principals & applications is specific to Active Directory and Chunks to TimescaleDB — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. | Organizational units is specific to Active Directory and Continuous Aggregates to TimescaleDB — each maps to any object or custom field on the other side. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. | Organizational contacts is specific to Active Directory and Regular PostgreSQL Tables to TimescaleDB — each maps to any object or custom field on the other side. | |
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Views Standard SQL views used to shape or filter data for consumers. | Users is specific to Active Directory and Views to TimescaleDB — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and TimescaleDB
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.
Active Directory TimescaleDB Sub-second propagation
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
DeliveryEach detected change is applied to TimescaleDB as a row-level write, with types converted between the two schemas.
TimescaleDB Active Directory Sub-second propagation
DetectionChanges in TimescaleDB are captured at the source via change data capture — no polling loop against its API. Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must.
DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
- TimescaleDB: No API rate limits; throughput is bounded by database resources and connection limits.
What ships with Active Directory ⇄ TimescaleDB
Connect Active Directory and TimescaleDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–TimescaleDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or TimescaleDB 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 Active Directory or TimescaleDB record.
Observability
Monitoring
Track your Active Directory ⇄ TimescaleDB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Active Directory and TimescaleDB.
How the Active Directory and TimescaleDB connectors work
Active Directory
- Integration surface
- Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
- Authentication
- OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
- Change detection
- Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
- Capabilities
- read · write · webhooks
- Rate limits
- Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
TimescaleDB
- Integration surface
- SQL wire protocol (PostgreSQL)
- Authentication
- Database credentials
- Change detection
- Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by database resources and connection limits.
How it works
How to connect Active Directory to TimescaleDB — 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 Active Directory and TimescaleDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Active Directory
connected
TimescaleDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and TimescaleDB 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 · Active Directory ⇄ TimescaleDBCustomers 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.
Active Directory TimescaleDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and TimescaleDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and TimescaleDB: authenticate both systems, choose the objects to sync (such as Active Directory's Devices and Directory roles), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and TimescaleDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–TimescaleDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and TimescaleDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Active Directory: Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling. On TimescaleDB: Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the TimescaleDB side: Schemas, Hypertables, Chunks, Continuous Aggregates, plus custom fields where TimescaleDB exposes them. On the Active Directory side: Service principals & applications, Organizational units, Organizational contacts, Users. 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.
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 427 integrations available for Active Directory and TimescaleDB.
Popular · 8 of 427
-
Active Directory ⇄ Airtable -
Active Directory ⇄ AWS Aurora MySQL - Active Directory ⇄ AWS Aurora PostgreSQL
-
Active Directory ⇄ MongoDB -
TimescaleDB ⇄ Auth0 -
TimescaleDB ⇄ Jumpcloud - TimescaleDB ⇄ Azure Active Directory
-
TimescaleDB ⇄ Okta
No integrations match .
