Skip to content
Security and identity ⇄ Data warehouse

Jumpcloud to Starburst Enterprise integration — real-time, two-way sync

Keep Jumpcloud and Starburst Enterprise 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 Jumpcloud and Starburst Enterprise

Land the users, groups, and access events from Jumpcloud in Starburst Enterprise continuously for security analytics, and write computed results back — without building or maintaining a pipeline.

Jumpcloud is the record of who exists and what they can reach; Starburst Enterprise is where the business measures everything else. The two overlap on people and their access — the same users, groups, roles, and events that Jumpcloud governs are what security, compliance, and analytics teams want to query in Starburst Enterprise. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.

Stacksync syncs Directory Insights events, System Users (Users), User Groups, Systems (devices) from Jumpcloud into tables in Starburst Enterprise in real time, and the connection works in both directions: values computed in Starburst Enterprise, such as risk scores or access-review decisions, can be written back to attributes in Jumpcloud where the identity team acts on them. Schema changes are handled, API limits are managed, and the sync is something you configure rather than a pipeline you keep alive.

Common use cases

  • 01 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
  • 02 Write curated or reconciled results back to lakehouse tables through connectors that support inserts
  • 03 Drive Application and Policy assignments from HR attributes or entitlement tables so SSO access and device policies change the moment a role does.
  • 04 Two-way sync User Groups and their memberships between JumpCloud and a source-of-truth database so app, LDAP, and RADIUS access stays aligned with org data.

Common sync patterns

Directory data in the warehouse, minus the pipeline

Users, groups, and roles from Jumpcloud arrive in Starburst Enterprise as queryable tables, current within seconds instead of a nightly directory export.

Access and sign-in analytics

Sign-in and access events from Jumpcloud land in Starburst Enterprise, so security and compliance teams can query who reached what, and when, alongside the rest of the business's data.

Access governance on joined data

Join Jumpcloud's users and group memberships with HR, product, and usage data already in Starburst Enterprise to surface who holds access they no longer need.

What you can sync between Jumpcloud and Starburst Enterprise

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.

Jumpcloud objects Starburst Enterprise objects How this pairing syncs
Directory Insights events Audit stream of logins and admin actions across SSO, LDAP, RADIUS, systems, and MDM; read-only, queried by POST and used as the change feed and SIEM source. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Directory Insights events is specific to Jumpcloud and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side.
System Users (Users) Directory user accounts (email, username, attributes, status, MFA, group and app bindings); full CRUD via the v1 /systemusers API - create, update, activate or suspend, and delete to match an HR or identity source. Tables Queryable relations; writes pass through to sources whose connectors support them. System Users (Users) is specific to Jumpcloud and Tables to Starburst Enterprise — each maps to any object or custom field on the other side.
User Groups User groups that grant app, LDAP, and RADIUS access; created, updated, and deleted via v2 /usergroups, with membership managed through the graph association endpoints. Views Engine-level SQL views used to shape federated data before syncing it out. User Groups is specific to Jumpcloud and Views to Starburst Enterprise — each maps to any object or custom field on the other side.
Systems (devices) Enrolled macOS, Windows, and Linux machines running the JumpCloud agent; agent-enrolled, so the API reads, updates, and deletes systems for inventory and management rather than creating them. Materialized views Precomputed results that make repeated sync reads cheaper. Systems (devices) is specific to Jumpcloud and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side.
System Groups Device groups used to scope policies, commands, and access; full CRUD via v2 /systemgroups, with systems bound and unbound through association endpoints. Columns Typed per the Trino type system, mapped from each source's native types. System Groups is specific to Jumpcloud and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.
Applications (SSO) SAML and OIDC SSO app configs; read via v2 /applications and their user/group assignments created and removed to control who can reach each connected app. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Applications (SSO) is specific to Jumpcloud and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Jumpcloud and Starburst Enterprise

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.

Jumpcloud Starburst Enterprise Sub-second propagation

DetectionJumpcloud notifies Stacksync of record changes through webhook events. No database-style change log.

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

Starburst Enterprise Jumpcloud Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

DeliveryEach detected change is written to Jumpcloud through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Jumpcloud: JumpCloud rate-limits API requests and returns HTTP 429 (Rate limit exceeded) when a client sends requests too quickly; its guidance is to back off and retry at a lower rate. Specific per-minute ceilings are not published, and the Directory Insights API is metered separately. Webhook deliveries are retried three times with exponential backoff on 5xx, 408, or 429 responses.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Jumpcloud ⇄ Starburst Enterprise

Connect Jumpcloud and Starburst Enterprise for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Jumpcloud–Starburst Enterprise connection.

Real-time

Two-way sync

Changes in Jumpcloud or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Jumpcloud or Starburst Enterprise 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 Jumpcloud or Starburst Enterprise record.

Observability

Monitoring

Track your Jumpcloud ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Jumpcloud and Starburst Enterprise.

How the Jumpcloud and Starburst Enterprise connectors work

Jumpcloud

Integration surface
JumpCloud REST API - v1 (console.jumpcloud.com/api) for Systems, System Users, and Commands; v2 (/api/v2) for User Groups, System Groups, Applications, Policies, and resource associations; plus the Directory Insights API (api.jumpcloud.com/insights/directory/v1/events) and Webhook Channels for outbound events.
Authentication
Admin API key sent in the x-api-key header (keys are prefixed jca_, generated in the console with a 30-365 day expiry, and disabled for admins by default until enabled); an x-org-id header scopes calls to a single organization for MSP multi-tenant admins. System Context authorization (HMAC-signed) also exists for agent-run calls.
Change detection
No database-style change log. The Directory Insights API is queried by POST for login and admin events across SSO, LDAP, RADIUS, systems, MDM, and directory services - including the association_change event that records user-to-group and policy-to-device membership changes; Webhook Channels tied to Insights Rules POST JSON to a registered endpoint for near-real-time triggers.
Capabilities
read · write · webhooks
Rate limits
JumpCloud rate-limits API requests and returns HTTP 429 (Rate limit exceeded) when a client sends requests too quickly; its guidance is to back off and retry at a lower rate. Specific per-minute ceilings are not published, and the Directory Insights API is metered separately. Webhook deliveries are retried three times with exponential backoff on 5xx, 408, or 429 responses.

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect Jumpcloud to Starburst Enterprise — 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 Jumpcloud and Starburst Enterprise 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
    Jumpcloud connected
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Jumpcloud and Starburst Enterprise 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 · Jumpcloud ⇄ Starburst Enterprise
    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
    Jumpcloud Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Jumpcloud and Starburst Enterprise 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 434 integrations available for Jumpcloud and Starburst Enterprise.

Popular · 8 of 434
All Jumpcloud integrations All Starburst Enterprise 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