Sync active — 12 objects
4,291 records synced
Next sync in 8s
Zero data loss
BIDIRECTIONAL SYNC
Free & Open-Source Salesforce Sync Engine

Sync Salesforce
to PostgreSQL.
In Real Time.

Trigger-based, bidirectional Salesforce ↔ PostgreSQL sync with fixed 10-second batch intervals. Free to use — try the hosted demo or self-host on your own infrastructure.

10s batch interval
SOAP + Bulk API
hstore change tracking
31-day archive
Start Syncing Free See How it Works ↓

How it Works

Production-grade sync precision.
Running on your stack.

AlgoBridge implements the same state machine, trigger names, and column conventions used by production Salesforce sync deployments. Migrate without changing a single query.

1
Detect Change

Trigger fires on every write

A PostgreSQL trigger (ab_{table}_logtrigger) captures every INSERT, UPDATE, and DELETE into _trigger_log, storing the changed columns as an hstore diff — the standard format for Salesforce sync.

2
Sync Engine Polls

Every 10 seconds, exactly

The sync worker reads all NEW rows from _trigger_log, marks them PENDING, then batches to Salesforce via SOAP API or Bulk API v2 — selected automatically based on record count and mapping configuration.

3
Confirm & Write Back

SF confirms, PG reflects

On success, _ab_lastop is set to INSERTED or UPDATED. SF→PG writes back with _ab_lastop = SYNCED, bypassing the trigger to prevent feedback loops.

Under the Hood

Sync as a structural
data layer.

Every design decision follows production Salesforce sync conventions. Same trigger names, same column conventions, same API thresholds. Your existing SQL queries run unmodified.

hstore Change Tracking

Column diffs stored as hstore — the standard for Salesforce sync. Not JSONB. CREATE EXTENSION IF NOT EXISTS hstore applied automatically.

SOAP + Bulk API Threshold

SOAP API for batches ≤200 records or merged-write mappings. Bulk API v2 for ordered-write mappings with >200 records and an external key field. Auto-selected per sync cycle.

State Machine: NEW → PENDING → SUCCESS

Industry-standard state names. PENDING means in-flight. Records never silently dropped — FAILED rows are retained with _ab_err populated.

31-Day Trigger Log Archive

Processed rows promoted to _trigger_log_archive, purged after 31 days. Full audit trail, zero unbounded table growth.

Salesforce
PostgreSQL
_trigger_log
id state _ab_lastop 8841 SUCCESS SYNCED 8842 PENDING PENDING 8843 NEW —
sfid stored as VARCHAR(18) — lookup columns preserve SF ID directly

Why AlgoBridge

Everything a production sync engine provides.
Nothing you don't own.

Fixed 10-Second Cadence

Not configurable — by design. The de facto standard for Salesforce sync is a fixed 10-second batch interval, and we follow it precisely. Predictable latency. No surprise API quota spikes. Production teams can plan around a known upper bound.

Your Infra, Your Keys

PostgreSQL credentials stored in AWS SSM Parameter Store as SecureStrings — never in env files. Bring your own PostgreSQL (e.g. Amazon RDS). Your tenant data stays in infrastructure you control.

Zero Migration Friction

Trigger names, system table schemas, column naming, and _ab_lastop values match the AlgoBridge sync specification. Move to self-hosted sync without touching your application queries.

-- System tables created on connection
CREATE TABLE _trigger_log (
id SERIAL PRIMARY KEY,
txid BIGINT,
table_name TEXT,
record_id INTEGER,
sfid VARCHAR(18),
action TEXT,
state TEXT DEFAULT 'NEW',
values hstore
);
-- Trigger installed per mapped table
CREATE TRIGGER ab_contact_logtrigger
AFTER INSERT OR UPDATE OR DELETE
ON contact
EXECUTE FUNCTION ab_contact_logger();

For Developers

Named to the
de facto standard.

Every trigger, function, and column is named to match the de facto Salesforce sync spec. Tools that introspect your schema — BI systems, dbt, Metabase — see the same structure they expect.

ab_{table}_logtrigger — CDC trigger per mapped object
ab_{table}_status_trigger — Write-back guard (skips on sync)
_abmeta — Schema metadata table
sfid VARCHAR(18) — SF ID stored directly, not FK

Pricing

The software is free.
Pay for service and support.

Use the hosted demo or self-host at no cost. Engage CloudAlgo when you need expert implementation, custom integrations, or a dedicated support arrangement.

Hosted Demo

Free

Try AlgoBridge instantly on our hosted instance. Ideal for sandbox and dev Salesforce orgs.

Get Started Free
  • Instant access, no setup
  • Full sync engine
  • Sandbox & dev orgs only
  • Community support
Recommended

Self-Hosted

Free

Deploy on your own infrastructure. Full control over your data, credentials, and environment.

Self-Host for Free →
  • Your infra, your data
  • Production Salesforce orgs
  • AWS ECS or Docker Compose
  • Open source, MIT licensed

Service & Support

Custom

Expert deployment, custom integrations, and dedicated support from the team that built the engine.

Talk to Us
  • Managed deployment
  • Custom field & org mappings
  • Dedicated support SLA
  • Multi-org & compliance work

The sync engine is free and open source. You only pay when you need expert help.

Free to Use · Open Source · Self-Hosted

Ready to Sync.

Try the hosted demo free, or deploy on your own infrastructure at no cost. Bring your own Salesforce org and PostgreSQL database — no platform lock-in.

Create Free Account Read the Docs

Prefer to run it yourself? Self-host for free →

CloudAlgo CloudAlgo Consulting

Need a custom
integration built?

AlgoBridge covers the standard sync pattern. But Salesforce integrations get complex fast — custom objects, multi-org routing, legacy middleware, compliance requirements. CloudAlgo builds those bespoke solutions for you.

  • Custom Salesforce ↔ PostgreSQL mappings & field transforms
  • Multi-org sync architecture & routing
  • Private cloud & on-premise deployment support
  • HIPAA / SOC 2 compliance-aware integration design
Talk to CloudAlgo

Common Engagements

Custom Sync Logic

Field transforms, lookup resolution, conditional sync rules, and upsert logic beyond what standard mapping supports.

Full-Stack Data Platform

Salesforce as your system of record, PostgreSQL as the analytics layer — built, deployed, and maintained by CloudAlgo.

Ongoing Managed Support

Schema changes, API version upgrades, sync monitoring, and incident response — handled by the team that built the engine.

CloudAlgo

CloudAlgo

cloudalgo.com