Identity Data Pipeline · AWS-Native · SOC2 Certified

Your LDAP Directory.
Clean JSON. Anywhere.

Stop wrestling with X.500 syntax, certificate chains, and persistent connections. Universal Directory Sync converts Active Directory, Entra ID, and Google Directory into structured JSON—piped directly into Amazon S3, SQS, or Webhooks. Zero code required.

Start Free — Up to 250 Records See How It Works
Before · Raw LDAP Query
ldapsearch -H ldaps://dc.corp.local:636 \
  -D "CN=svc_sync,OU=Service,DC=corp,DC=local" \
  -w $LDAP_BIND_PASS \
  -b "OU=Employees,DC=corp,DC=local" \
  "(objectClass=user)" \
  sAMAccountName mail department

# Error: SSL: CERTIFICATE_VERIFY_FAILED
# Retry with -ZZ flag... failed again.
# Lambda cold start killed the connection.
# Who rotates that bind password again?
Universal Directory Sync
After · Clean JSON in S3
{
  "users": [
    {
      "id": "jsmith",
      "email": "[email protected]",
      "department": "Engineering",
      "groups": ["vpn-access","github-org"],
      "active": true,
      "synced_at": "2026-03-26T08:00:00Z"
    }
  ],
  "meta": {
    "total": 4821,
    "source": "corp.local",
    "sink": "s3://identity-data/users.json"
  }
}
🔐
SOC2 Type II Certified
🌎
ISO 27001 Certified
☁️
AWS Marketplace Listed
🔒
TLS 1.3 · AES-256 at Rest
No Persistent Connections
🏢
20+ Years Enterprise Trust
The Protocol Paradox

Legacy directories shouldn't block modern apps.

LDAP was designed for a different era—before Lambda, before serverless, before stateless everything. Developers spend more time fighting the protocol than building their product.

  • 01

    SSL/TLS Nightmares on Port 636

    Works on 389, breaks on 636. Your AD certificate authority isn't trusted by anything. Hours of debugging, every time, on every new machine.

  • 02

    Lambda Can't Hold a Stateful LDAP Connection

    Serverless is stateless by design. LDAP is stateful by design. Cold starts kill TCP sessions. This architecture is fundamentally broken.

  • 03

    Credentials Written to Plain-Text Logs

    Poorly designed integrations log LDAP bind passwords on local workstations. One breach away from a major incident—and most developers don't know it's happening.

  • 04

    Auth0 Charges $1,725/mo Just to Start

    Auth0's B2B Essentials caps you at 3 enterprise connections for $1,725/month. You don't need a full IAM suite. You need a reliable data feed.

Common Lambda Failure Pattern
exports.handler = async (event) => {
  const client = ldap.createClient({
    url: 'ldaps://dc.corp.local:636'
  });
  // ❌ Does this connection persist?
  // ❌ Cold start kills the TCP session?
  // ❌ 5s Lambda timeout exceeded?
  // ❌ Who rotates the bind password?

  // This approach does not scale.
};
✓ The Universal Directory Sync Pattern
exports.handler = async (event) => {
  const data = await s3.getObject({
    Bucket: 'your-identity-bucket',
    Key:    'users/latest.json'
  }).promise();

  const users = JSON.parse(data.Body);
  // ✓ Stateless. Instant. No LDAP needed.
  // ✓ Data refreshed on your schedule.
  // ✓ Zero credential exposure.
};
The Pipeline

From messy directory to clean data stream. In minutes.

Universal Directory Sync handles every layer of LDAP complexity so you never have to. Configure once, consume forever.

01

Connect Your Directory

Point Universal Directory Sync at your LDAP server, Entra ID (Azure AD), or Google Cloud Directory. Upload your Root CA certificate directly in the UI—no backend access required. We handle the LDAPS handshake, paged results (RFC 2696), and referral chasing automatically.

Supports: Active Directory · Entra ID · OpenLDAP · Google Directory
02

Preview in Simulation Mode

Before a single byte hits your infrastructure, use Simulation Mode to see the exact JSON output your sync will produce. Verify attribute mappings, filter logic, and record counts. A safety switch halts any sync that would affect more than 10% of your records—protecting against accidental mass-deletion.

Dry-run preview · Safety threshold · No data committed until you confirm
03

Choose Your Destination Sink

Route identity data where your stack needs it: Amazon S3 for durable snapshots, Amazon SQS for reliable event-driven provisioning, or Webhooks for real-time pushes to tools like Retool or Appsmith. Multiple sinks from a single connection are supported.

S3 · SQS · Webhooks · EventBridge (coming soon)
04

Set Your Sync Frequency

Monthly for development and POCs, daily for production SMBs, or on-demand real-time via SQS for automated provisioning workflows. Upgrade your frequency at any time without reconnecting.

Monthly · Daily · On-Demand (SQS/SNS event-driven)
05

Consume Anywhere in Your Stack

Your Lambda functions, HR dashboards, provisioning scripts, and AI/RAG pipelines all read clean, versioned JSON from S3. No LDAP SDK. No persistent connections. No credential management in application code. Just structured data where you need it.

Lambda · ECS · Retool · Appsmith · Any REST consumer
Infrastructure Destinations

Your identity data. Your infrastructure. Your rules.

Universal Directory Sync writes to the AWS services your stack already uses. No new SDKs, no new services to manage.

🥳

Amazon S3

Durable, versioned JSON snapshots of your entire directory. Use S3 Event Notifications to trigger Lambda functions, feed search indexes, or build compliance audit trails.

s3://your-bucket/identity/users-latest.json
📬

Amazon SQS

Decoupled, reliable change events for every user add, update, or deprovision. If a downstream API is unavailable, messages queue and retry—nothing is ever lost.

{"event":"user.added","id":"jsmith",...}
🔗

Webhooks

Real-time HTTP POST to any endpoint whenever a specified group or user changes. Perfect for Retool, Appsmith, n8n, or custom REST APIs outside of AWS.

POST https://your-app.com/api/identity-sync
AWS-Native Architecture

Universal Directory Sync operates within your existing AWS account. Data flows from your directory, through our SOC2-certified processing layer, and lands directly in the S3 bucket or SQS queue you own. Your data never passes through a third-party data warehouse. Supports AWS PrivateLink for zero-public-internet LDAP traffic on Enterprise plans.

Corp LDAP / Entra ID / Google Dir
Universal Directory Sync (SOC2, TLS 1.3)
Your S3 Bucket / SQS Queue
Your Lambda / App / Dashboard
Transparent Pricing

No SSO Tax. No per-user surprises.

A flat per-connection fee that scales with your infrastructure—not your user count. Cancel anytime. Upgrade instantly.

The Lab
$0/mo
For developers validating JSON mapping and building proof-of-concepts. No credit card required.
  • 1 directory connection
  • Monthly sync
  • Up to 250 records
  • S3 and Webhook sinks
  • Simulation Mode included
  • Community support
Start Free
Standard
$125/mo per connection
Production-grade for startups and SMBs that need enterprise-ready directory sync without enterprise-level spend.
  • 1 directory connection
  • Daily sync
  • Up to 10,000 records
  • S3, SQS, and Webhooks
  • Simulation Mode + Safety Switch
  • Email support (48h SLA)
Start Trial
Most Popular
Real-Time
$200/mo per connection
On-demand sync via SQS/SNS events for high-velocity apps with automated provisioning workflows.
  • 1 directory connection
  • On-demand event-driven sync
  • Up to 25,000 records
  • S3, SQS, Webhooks + EventBridge
  • Simulation Mode + Safety Switch
  • Priority support (24h SLA)
  • AWS Marketplace billing
Start Trial
Enterprise
Custom
Metered pricing for large-scale directories, VPC PrivateLink, dedicated SLAs, and AWS / Azure Marketplace procurement.
  • Unlimited connections
  • Real-time metered sync
  • Unlimited records (metered)
  • AWS PrivateLink / VPC support
  • Dedicated success manager
  • 99.9% SLA + phone support
Talk to Sales
Enterprise metered pricing: Directories exceeding 25,000 records are charged $0.05 per 1,000 records—keeping costs predictable. Compare to Auth0 B2B Essentials at $1,725/month for just 7,500 users with only 3 connections. Universal Directory Sync is available on the AWS Marketplace—apply your committed cloud spend directly.
Market Landscape

Built for the gap the big players left open.

IAM suites capture login events. Universal Directory Sync gives you the data. That's a fundamentally different product for a fundamentally different need.

Scroll to see all columns
Product Model JSON / S3 Output Zero-Code Entry Price Best For
Universal Directory Sync Per-Connection SaaS Native S3 / SQS Yes $0 Free Tier Identity data pipeline for devs
Auth0 (Okta) Per-User (High TCO) No native output Reconcile Lambda required $1,725/mo (B2B) Full CIAM, large enterprise
WorkOS Per-Connection (SCIM) No S3/SQS output Yes (SCIM-focused) $125/mo B2B SaaS enterprise logins
AWS AD Connector AWS Native Gateway No JSON export EC2 domain-join only AWS pricing EC2 / WorkSpaces domain
n8n / Okta Workflows iPaaS (build yourself) Manual pipeline build Write all sync logic yourself $20–$50/mo Custom workflow orchestration
CData Sync Annual License ETL to S3 Complex setup required $7,999/yr Data warehouse ETL
Who Uses Universal Directory Sync

Two teams. Same problem. One solution.

🚀

The B2B SaaS Startup

Building Enterprise Readiness

You're post-Series A and just landed a Fortune 500 prospect. They require SCIM-based directory sync before signing. Auth0 wants $1,725/month and three months of legal review. You need to ship in two weeks.

"We just needed their users in our app. We didn't need an entire identity platform. Universal Directory Sync was live in an afternoon."
🛠️

The Internal IT Engineer

Building Internal Tools & Dashboards

You maintain an HR dashboard, license management scripts, and an automated onboarding workflow. You need a reliable, secure data feed from Active Directory—not a full IAM suite with a procurement cycle.

"I don't need Okta. I need AD data in S3 so my Lambda can read it. Universal Directory Sync does exactly that, and it was running in the same day."
Use Cases

What developers build with Universal Directory Sync.

Serverless Authentication

Pre-populate DynamoDB or S3 with directory data. Your Lambda identity providers run lookups in milliseconds—no persistent LDAP connection required. Dramatically reduce authentication latency on API Gateway and Transfer Family.

🤖

Automated Seat Provisioning

SQS events fire the moment a user joins an AD group. Your Lambda provisions (or deprovisions) a SaaS seat automatically. If a downstream API is down, the message queues—nothing is ever lost.

📊

HR & License Dashboards

Pipe Active Directory data into S3, then visualize in Retool, Appsmith, or Grafana. Build headcount reports, department-level license dashboards, and org-chart tools without ever touching LDAP directly.

🧠

Identity Pipelines for AI

Use versioned S3 snapshots as a retrieval source for RAG systems and LLM-powered internal tools. Query "who manages the data engineering team?" against your org's actual directory data—securely and at rest.

🔑

Enterprise SSO Readiness

Close enterprise deals faster by proving SCIM-compatible directory sync from day one. Give your B2B SaaS the directory integration story enterprise IT demands—without a six-figure IAM suite invoice.

📋

Compliance Audit Trails

Versioned S3 objects create an immutable historical record of every directory state. Demonstrate who had access to what, when—essential for SOC2, ISO 27001, and HIPAA audits—without querying a live AD.

Security & Compliance

Enterprise-grade security. Developer-grade accessibility.

Identity data is your most sensitive organizational asset. Every control you'd expect from a platform with 20+ years in enterprise environments.

🔑

AWS Secrets Manager Integration

LDAP bind credentials are never stored in plain text. All service account DNs and passwords are encrypted via AWS Secrets Manager and can be rotated without any code changes.

🛡️

Least-Privilege by Default

Your sync account is configured with read-only access to the specific Organizational Units you define. No write permissions, no admin access, no broad directory visibility by default.

🔐

End-to-End Encryption

All data in transit is encrypted via TLS 1.3. Data at rest in S3 uses AES-256 server-side encryption. Upload your own Root CA certificate for LDAPS on port 636 directly in the UI.

🔎

Audit Logging & Health Monitoring

Every sync event is logged: records added, updated, deleted, and any failures. Continuous health checks detect when LDAP is pingable but unresponsive—before your end users notice.

🏗️

AWS PrivateLink Support (Enterprise)

Deploy within your private VPC on Enterprise plans. LDAP traffic never touches the public internet. Fully compliant with zero-trust architectures and regulated industries including HIPAA candidates.

🧪

Simulation Mode & Safety Switch

Preview every sync before it commits. An automatic safety switch halts any operation that would change or delete more than 10% of your records—preventing catastrophic misconfiguration from day one.

SOC2 Type II
ISO 27001
TLS 1.3 in Transit
AES-256 at Rest
AWS Well-Architected
Stateless Multi-AZ
FAQ

Everything developers ask before signing up.

Does Universal Directory Sync store my directory data?
No. Universal Directory Sync processes your directory data and writes it directly to the AWS infrastructure you own—your S3 bucket, your SQS queue. We act as a processing pipeline, not a data store. Your data lands in your account and stays there. We do not maintain copies of your identity data on our infrastructure.
What directory sources does Universal Directory Sync support?
We support Microsoft Active Directory (on-premises), Microsoft Entra ID (formerly Azure AD), Google Cloud Directory, and any standard LDAPv3-compliant directory server including OpenLDAP. Multi-directory sync—combining Active Directory and Google—is supported and normalizes attributes into a single unified JSON schema.
How is this different from AWS AD Connector?
AWS AD Connector is a gateway for redirecting authentication requests to your on-premises AD—designed primarily for joining EC2 instances to a domain or enabling SSO for AWS-managed services like WorkSpaces. It does not export directory data in JSON format, and it has no native integration with S3 or SQS. Universal Directory Sync is a data pipeline: its entire purpose is to convert your directory tree into structured JSON and deliver it to the developer-native formats you already use.
I use Auth0 or Okta for SSO. Do I still need Universal Directory Sync?
Potentially, yes. Auth0's AD/LDAP Connector performs Just-In-Time (JIT) provisioning—data is only as fresh as the user's last login. If you need continuous background sync (for license management, HR dashboards, or provisioning users who haven't logged in yet), Auth0's connector won't help. Universal Directory Sync syncs on a schedule, independent of login events, so your data is always current.
Can I buy Universal Directory Sync through the AWS Marketplace?
Yes. Universal Directory Sync is listed on the AWS Marketplace as a SaaS subscription product. Enterprise customers can apply their committed AWS spend directly to their Universal Directory Sync subscription, often bypassing standard vendor onboarding entirely. Standard and Real-Time tiers are available self-serve at the same pricing as direct purchase.
How does the Safety Switch work?
Every sync run compares the incoming directory data against the last known state. If the delta would result in more than 10% of your records being modified or deleted in a single run, Universal Directory Sync pauses the sync and alerts you before committing any changes. This protects against accidental mass-deletion caused by a misconfigured LDAP filter—a common and catastrophic mistake. You can review the proposed changes and manually approve or abort.
How do I handle LDAPS on port 636 with a self-signed or AD certificate?
This is the most common LDAP pain point—applications work on unencrypted port 389 but fail on 636 because the server doesn't trust the AD certificate authority. Universal Directory Sync includes a Root CA Certificate upload field in the UI. Export your Domain Controller's Root CA as a .pem or .crt file and upload it directly. A "Relaxed TLS" mode is also available for development environments using self-signed certificates.
What happens if my downstream service is down when an SQS event fires?
Nothing is lost. Amazon SQS provides at-least-once delivery with configurable retention (default 4 days, up to 14 days). Identity change events remain in the queue and will be processed once your service recovers. This reliable decoupling is one of the core architectural advantages of SQS-driven identity sync over synchronous LDAP queries inside application code.

Start syncing in
under five minutes.

Free tier supports up to 250 records. No credit card required. No persistent LDAP connections. No protocol nightmares.

Start Free — The Lab Tier 📖 Read the 5-Minute Setup Guide