Skip to content
Database ⇄ Human resources

CockroachDB to Hibob integration — real-time, two-way sync

Keep CockroachDB and Hibob 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 CockroachDB and Hibob

Put your workforce data where your apps can reach it: CockroachDB and Hibob share the same people, positions, and org structure in real time.

Hibob is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. CockroachDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Lifecycle, Documents, Named lists, People (Employees) in Hibob need to exist as queryable Changefeeds, Databases, Schemas, Tables in CockroachDB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Changefeeds, Databases, Schemas, Tables in CockroachDB with Lifecycle, Documents, Named lists, People (Employees) in Hibob field by field, in real time. You decide which system owns which fields — Hibob typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Write application events from CockroachDB back to CRM fields to give go-to-market teams product context.
  • 02 Use changefeeds to propagate row changes from a multi-region cluster into a warehouse or search index.
  • 03 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.
  • 04 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.

Common sync patterns

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Lifecycle, Documents, Named lists, People (Employees) replicate into CockroachDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Hibob stay consistent in CockroachDB, so hierarchy-driven logic and permissions don't drift.

What you can sync between CockroachDB and Hibob

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.

CockroachDB objects Hibob objects How this pairing syncs
Schemas Namespaces within a database used to isolate synced tables from application tables. Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Schemas is specific to CockroachDB and Salaries to Hibob — each maps to any object or custom field on the other side.
Tables The core read/write target; rows sync bi-directionally with SaaS objects or other databases. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Tables is specific to CockroachDB and Time off to Hibob — each maps to any object or custom field on the other side.
Views Read-only projections used as curated sync sources. Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Views is specific to CockroachDB and Lifecycle to Hibob — each maps to any object or custom field on the other side.
Indexes Secondary indexes that keep sync lookup queries fast on key columns. Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Indexes is specific to CockroachDB and Documents to Hibob — each maps to any object or custom field on the other side.
Sequences ID generators that matter when writes originate from an external system. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Sequences is specific to CockroachDB and Named lists to Hibob — each maps to any object or custom field on the other side.
Changefeeds Built-in CDC streams that emit row-level changes to external sinks. People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. Changefeeds is specific to CockroachDB and People (Employees) to Hibob — each maps to any object or custom field on the other side.

How changes propagate between CockroachDB and Hibob

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.

CockroachDB Hibob Sub-second propagation

DetectionChanges in CockroachDB are captured at the source via change data capture — no polling loop against its API. CDC via changefeeds, which stream row-level changes.

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

Hibob CockroachDB Sub-second propagation

DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.

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

Rate-limit considerations

  • CockroachDB: No API rate limits in the SaaS sense; throughput is bounded by cluster capacity.
  • Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
What ships with CockroachDB ⇄ Hibob

Connect CockroachDB and Hibob for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every CockroachDB–Hibob connection.

Real-time

Two-way sync

Changes in CockroachDB or Hibob instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever CockroachDB or Hibob 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 CockroachDB or Hibob record.

Observability

Monitoring

Track your CockroachDB ⇄ Hibob sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between CockroachDB and Hibob.

How the CockroachDB and Hibob connectors work

CockroachDB

Integration surface
SQL wire protocol (PostgreSQL-compatible)
Authentication
Database credentials with TLS; client certificates or SCRAM password auth
Change detection
CDC via changefeeds, which stream row-level changes; polling as a fallback
Capabilities
read · write · CDC
Rate limits
No API rate limits in the SaaS sense; throughput is bounded by cluster capacity

Hibob

Integration surface
REST API (the Bob API)
Authentication
Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
Change detection
Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
Hibob setup guide
How it works

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

    Choose tables

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

CockroachDB and Hibob 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 443 integrations available for CockroachDB and Hibob.

Popular · 8 of 443
All CockroachDB integrations All Hibob 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