BridgeStick
Menu
Sign in Start free
New Links: reach private networks with one command

SAP and SQL data, synced anywhere. Every value, exactly.

BridgeStick reads SAP through SAP's own standard interfaces — no ABAP, nothing installed in SAP — and PostgreSQL, MySQL, SQL Server, Oracle Database, Google BigQuery, SQLite, MongoDB, CouchDB or ArangoDB. It syncs the tables you pick to any database, document store or object storage, proves them row by row, and serves them through a secure data API.

Start free Read the docs

Free during early access · No credit card

Behind a firewall? An agent reaches it, outbound only.

BridgeStick between your sources and destinations

Sources

  • SAP
  • PostgreSQL
  • MySQL
  • SQL Server
  • SQLite
  • Oracle Database
  • Google BigQuery
  • MongoDB
  • CouchDB
  • ArangoDB

BridgeStick

Plan · Sync · Compare

Destinations

  • PostgreSQL
  • MySQL
  • SQL Server
  • SQLite
  • Oracle Database
  • Google BigQuery
  • MongoDB
  • CouchDB
  • ArangoDB
  • Amazon S3
  • Google Cloud Storage
  • Azure Blob Storage

Data API

REST and WebSocket

At a glance

lines of ABAP to install in SAP
0
inbound ports to open in your firewall
0
sync strategies, chosen table by table
4
command to install an agent
1

Why SAP data is hard to move

Moving data is easy. Moving it exactly is not.

The hard part is never the first copy. It is reaching systems behind a firewall, keeping every digit, and knowing the copy still matches next month.

Locked in private networks

Your SAP system and databases live behind a firewall. Inbound ports and VPNs mean change requests, upkeep, and more for an attacker to reach.

See how Links reach them

Values bent on the way

A careless pipeline rounds decimals into floats, turns empty strings into NULL and cuts long texts. An amount that changes on the way is a wrong report.

How values stay exact

Drift nobody sees

A cursor sync cannot see a row deleted or changed in place. Without a comparison, the gap shows only when the numbers stop adding up.

See comparisons

How it works

From SAP to anything in four steps.

One flow for every source: SAP, PostgreSQL, MySQL, SQL Server, Oracle Database, Google BigQuery, SQLite, MongoDB, CouchDB or ArangoDB.

  1. 01

    Connect a source

    Point BridgeStick at your SAP system or a SQL database. Test before you save, then explore its tables, fields and rows.

  2. 02

    Pick tables, get a plan

    Search and tick tables. BridgeStick suggests each one's key, cursor or window from its fields — SAP change dates and fiscal years included — and shows how every choice was resolved.

  3. 03

    Sync to every destination

    Each page is read once and written to all destinations at the same time, staged and published atomically. A run that stops resumes from its last checkpoint.

  4. 04

    Prove it

    Compare source and destinations row by row, on demand or on a schedule. Alarms fire on real discrepancies only — never on changes the next run will carry.

Connectors

The systems you run, in both directions.

SQL databases are read and written by the same connector, so SAP → SQL and SQL → SQL share one engine. SAP is read-only: nothing is ever written back to it.

  • SAP

    Source

    Read through SAP's own standard interfaces. Read-only.

  • PostgreSQL

    Source and destination

    Read and written, paged by key, with TLS you choose.

  • MySQL

    Source and destination

    Read and written, decimals with every digit.

  • SQL Server

    Source and destination

    Read and written, every time to its last digit.

  • SQLite

    Source and destination

    Read and written, as files on the server or an agent's machine.

  • Oracle Database

    Source and destination

    Read and written, every number to its 38th digit, dates and instants typed.

  • Google BigQuery

    Source and destination

    Read and written through its API, decimals to 76 digits, no driver to install.

  • MongoDB

    Source and destination

    Collections read and written by key, decimals kept to the digit.

  • CouchDB

    Source and destination

    Databases read and written by document id, every write idempotent.

  • ArangoDB

    Source and destination

    Collections read and written by key, a run swapped in at once.

  • Amazon S3

    Destination

    CSV or JSON files, each run marked complete.

  • Google Cloud Storage

    Destination

    CSV or JSON files, each run marked complete.

  • Azure Blob Storage

    Destination

    CSV or JSON files, each run marked complete.

  • Data API

    REST and WebSocket

    A secure data API

Platform

Built for data you cannot afford to get wrong.

Everything between the first read and the last proof, without scripts to babysit.

Every value arrives exactly

Amounts keep every digit, numbers their precision, text its blanks and zeros. A value a column cannot hold exactly turns the column into text — it is never rounded, trimmed or nulled.

SAP without ABAP

Tables are read through SAP's standard interfaces, page after page: every row exactly once, at a steady pace, picking up where it stopped after a restart. Nothing is installed or transported into SAP.

A strategy per table

Full refresh; incremental by cursor, with several fields and a lookback; by window, the last N days, months or fiscal years; or by comparison, for tables with no change column.

Atomic, staged publishing

Every run stages its pages and merges each table in one transaction. Readers never see a half-written table, and a failure, a cancel or a crash leaves every destination consistent.

Comparisons that tell the truth

Source and destinations compared row by row. Changes the next sync will carry are told apart from real discrepancies, each with its reason and the fix that applies.

Scheduled checks and alarms

Compare on a schedule and raise warnings or critical alarms on your thresholds: discrepancies, a share of a table, the same rows run after run, rows changed at the destination by another hand — told under the bell and pushed to your desktop or phone.

A secure data API

REST and WebSocket reads of a source, or of a destination's copy to spare it, with API keys that are hashed, scoped per source, expiring, revocable and rate-limited.

Built to keep running

A health monitor reconnects sources by itself, failed reads are tried again, interrupted jobs resume where they stopped, and a circuit breaker holds back a connection that keeps failing.

A space of your own, shared with your team

Every user is a tenant: their sources, destinations, connections, keys, notifications and audit trail — and nothing of anyone else's. Share yours with the people who work on it: admins manage the members, editors change everything else, viewers only look, and every action is logged with who did it.

Links · private networks

Your network stays closed. Your data stays home.

Install a small agent next to your SAP system or database. It dials out to BridgeStick over HTTPS and runs the work right there: the rows never cross BridgeStick.

  • One commandcurl, apt or PowerShell, joined with an auth key.
  • Outbound onlyHTTPS on port 443. Nothing opened in your firewall.
  • Runs where the data isData residency by design, and next to no egress.
  • High availabilitySeveral agents per link: the next one takes over.
  • Allow lists you controlThe agent reaches only what you allow. Nothing by default.
Explore Links Install an agent
Install, allow, check
curl -fsSL https://assets.bridgestick.com/downloads/install.sh | sh -s -- --auth-key bslk_…sudo bridgestick allow add sap.corp.local:44300sudo bridgestick statusLink:    plant-networkState:   connectedServer:  https://api.bridgestick.comAllowed: sap.corp.local:44300

Security

Security built into the architecture.

Not a checklist added at the end: each guarantee comes from how BridgeStick is built.

  • Tenant isolation

    Every query, event and API key keeps to its tenant.

  • Secrets encrypted at rest

    Never returned by the API, scrubbed from the logs.

  • Signed agent identity

    A key made on the agent never leaves it.

  • Outbound-only agents

    No inbound port, no tunnel, certificates checked.

  • Allow lists

    Enforced by the agent, whatever the cloud asks.

  • Egress policy

    Cloud connectors reach public addresses only.

  • Signed downloads

    The installer checks a signed manifest before it installs anything.

  • Read about security

Use cases

One bridge, many jobs.

SAP to your analytics database

Land MARA, BSEG and the rest of the dictionary in PostgreSQL, SQL Server or MySQL for BI, refreshed by change dates or fiscal years.

Feed plant and operations systems

Keep manufacturing and operations databases supplied with SAP master data every hour, with an alarm when they drift.

A data lake landing zone

Write CSV or JSON files to S3, Google Cloud Storage or Azure Blob, laid out the way data lakes expect: each run marked complete, the newest full copy always one step away.

Apps that read SAP on demand

Give your tools a scoped API key and let them page through SAP tables — or a destination's copy, to spare the source.

Database to database

Replicate PostgreSQL, MySQL, SQL Server or SQLite tables across engines — or into MongoDB, CouchDB and ArangoDB, and back — with types mapped exactly and keys kept apart.

Reconciliation you can show

Prove that each destination matches its source, table by table, with a CSV report of every difference and why it is there.

Pricing

Free during early access.

Every feature, for every user, while BridgeStick is in early access. No credit card, and no trial that runs out.

Early access

$0

today, with every feature

Start free Talk to us
  • Every connector: SAP, PostgreSQL, MySQL, SQL Server, Oracle Database, Google BigQuery, SQLite, MongoDB, CouchDB, ArangoDB, Amazon S3, Google Cloud Storage and Azure Blob Storage
  • Links and agents for your private networks
  • Every sync strategy, with staged, atomic publishing
  • Comparisons, scheduled checks and alarms
  • The data API, with scoped, expiring keys
  • A space of your own, with notifications — on your phone or desktop too — and an audit trail

An agent runs on a machine you already have, and its control channel uses a few tens of megabytes a month.

Questions, or a walkthrough with your own systems? Write to sales. Already using BridgeStick? Write to support.

FAQ

Questions, answered.

What is BridgeStick?
BridgeStick is a data bridge: it syncs tables from SAP and SQL databases to databases and object storage, compares them row by row, and serves them through a secure data API. It reads SAP through SAP's own standard interfaces, with no ABAP, keeps every value exact, and reaches private networks through agents.
How much does BridgeStick cost?
Nothing, during early access: every feature, for every user, with no credit card. The agent runs on a machine you already have and uses a few tens of megabytes a month of control traffic. Should paid plans come, they apply to you only after you are told and choose them.
Do I need to install anything in SAP?
No. BridgeStick reads SAP through the standard interfaces SAP already comes with, with a user you give it. There is no ABAP and no transport, and nothing is ever written back to SAP.
Which systems does BridgeStick support?
Sources: SAP, PostgreSQL, MySQL, SQL Server, Oracle Database, Google BigQuery, SQLite, MongoDB, CouchDB and ArangoDB. Destinations: PostgreSQL, MySQL, SQL Server, Oracle Database, Google BigQuery, SQLite, MongoDB, CouchDB, ArangoDB, Amazon S3, Google Cloud Storage and Azure Blob Storage. SQL databases and document stores work in both directions; SAP is read-only.
How does BridgeStick reach a private network?
Through a link: you install the BridgeStick agent on a machine inside the network with one command and join it with an auth key. The agent dials out over HTTPS on port 443, so no inbound port is opened, and it runs the syncs there, reaching only what its allow list permits.
Does my data cross BridgeStick?
Not when a connection runs on a link: the agent reads the source and writes the destinations inside your network, and sends BridgeStick only counts, cursor values, progress and errors. Rows reach BridgeStick only when you ask for them there — the data API, Explore or a comparison of a private source — and when every end of a connection is public, it runs in BridgeStick's cloud.
What does it cost to run an agent?
An agent runs on a machine you already have — Linux, macOS on Apple silicon or Windows — and needs only outbound HTTPS. Its control channel uses some tens of megabytes a month (a heartbeat every 15 seconds: well under a cent of egress), and the rows it moves inside your network cause no cloud egress. The Links page shows, live, what each link moved and its estimated egress cost.
How does BridgeStick keep values exact?
Every source hands over each value exactly as it is — amounts with all their digits, dates and times with their full precision, files and binary data untouched — and every destination writes it into a matching column. A value a column cannot hold exactly turns the column into text instead of being rounded, trimmed or set to NULL.
Can my own applications read the data?
Yes, through the data API: REST and WebSocket endpoints behind API keys that are hashed, scoped to the sources you choose, expiring and rate-limited. An app can read a table at its source or as a destination holds it, falling back to the source when the destination cannot serve it.
Where does BridgeStick run, and what does it keep?
BridgeStick's cloud runs on Google Cloud in the United States, and you sign in through Firebase Authentication. It keeps your account, your configuration — credentials encrypted — and the history of your jobs, comparisons and audit trail. Rows that a link moves stay inside your network; see the privacy policy for the rest.

Bridge your data with nothing bent on the way.

Create your space, connect a source and run your first sync — free during early access. When your systems are private, an agent is one command away.

Start free Talk to us Read the docs