Quick start

1. Create your account

Start free with Google, or with an email address and a password of 8 characters at least — then open the link we email you to verify the address, and sign in. Your account is a space of its own: nobody else sees your sources, destinations, links or data.

2. Private systems: a link

Skip this step when your systems are reachable from the internet. When they are behind a firewall, BridgeStick reaches them through a link: an agent you install on a machine inside that network, which dials out over HTTPS — nothing is opened in your firewall.

• In BridgeStick, open Links → New link, then New auth key: the key and the install command for each system are shown once.
• Run the command on a machine inside the network, and allow what the agent may reach (sudo bridgestick allow add sap.corp.local:44300).
• Every step, with the allow list and high availability: Install the agent.

3. Add a source

Open Sources → New source and pick SAP, PostgreSQL, MySQL, SQL Server, Oracle Database, Google BigQuery, SQLite, MongoDB, CouchDB or ArangoDB. Fill in the host, the user and the password; as Network, choose Public internet or your link. Test connection before you Save, then open Explore to browse its tables, fields and rows.

• SAP is read through its standard interfaces — SOAP-RFC (the /sap/bc/soap/rfc service) or OData v2 — with a user your SAP team allows to read the tables you sync. Nothing is installed in SAP, and nothing is ever written back.
• A SQL source needs a user that can only read.

4. Add a destination

Open Destinations → New destination and pick PostgreSQL, MySQL, SQL Server, Oracle Database, Google BigQuery, SQLite, MongoDB, CouchDB, ArangoDB, Amazon S3, Google Cloud Storage or Azure Blob Storage. Test connection, then Save. A Tables prefix (sap_) puts every table it receives under one name.

5. Create a connection

Open Connections → New connection: choose the source and one or more destinations, then tick the tables to sync. Each table gets suggested settings from its fields — a full refresh, a cursor on a change date, a window on a fiscal year, or a comparison — and Auto-configure brings them back after an edit. Pick a schedule (manual, every hour, every 6 hours, every 24 hours, or a cron expression) and Save.

• The connection's Sync plan shows how each table will sync, and why.

6. Run the first sync

Press Sync now. Jobs shows each table's progress as it runs; every page is written to all the destinations at once and published atomically, so readers never see a half-written table. A job that stops resumes from its last checkpoint. Replay… reads a window of a cursor table again — rows changed behind the cursor — without moving the cursor.

7. Check it row by row

Open Compare, pick the connection and Start comparison: every row of the source is checked against every row each destination holds. Changes the next sync will carry are told apart from real discrepancies, and each discrepancy comes with its reason and a fix you can apply. A table that has not changed since the last comparison — at either end, as the databases themselves attest — is not read again.

8. Schedule checks and alarms

On Compare, Schedule a comparison to have a connection checked on its own, and choose what raises its alarm: more discrepancies than you accept, a share of a table, the same rows run after run, or rows changed at the destination by someone else. Alarms arrive under the bell, as notifications, and as push notifications on your desktop or phone when you turn them on.

9. Read the data from your apps

On the source, turn on Expose via data API. Open API Keys → New API key, scope it to All my sources or to the ones you pick, and copy it — it is shown once. Then read rows with it:

curl -H "Authorization: Bearer bsk_…" "https://api.bridgestick.com/api/v1/data/sources/sap-prod/tables/rows?table=MARA&fields=MATNR,MTART&limit=1000"

• Every endpoint, paging, values and errors: Data API reference.

Limits during early access

While BridgeStick is in early access, each space holds up to 50 sources, 50 destinations and 50 connections, 10 links (with 10 agents and 50 auth keys each) and 50 data-API keys; a schedule runs every 5 minutes at most, 2 syncs of a space run at once (the others wait their turn), and a data-API key makes 600 requests and reads 1,000,000 rows a minute, 4 reads at a time. Need more? Write to us.