Talk to usDiscuss a deployment
SQL Server · MongoDB · Postgres

Bring every remote site into your cloud offering. Built for the slow, high-latency links at remote sites.

Your product runs at customer sites with its own database. redfly keeps a central copy of every site current within a couple of minutes. You build the cloud features; we keep the data flowing.

Discuss a deploymentSee how it works
  • 100+ enterprise customers
  • No rewrite
  • No vendor lock-in
  • Cloud
  • Onsite
  • Production grade
  • 10B+ rows synced
  • Outbound only
  • Encrypted per site
System reliability
"Once you set it up, it just works. We never have problems afterward."
Director of Manufacturing, large AMR company in the supply chain & logistics space
Peak seasons
"They worked diligently with us over multiple Black Fridays and Cyber Mondays. Now it works like a well oiled machine."
Logistics customer, after several peak seasons
Sync under pressure
"During our time with this system, we saw everything break down. Sync worked perfectly throughout."
Operations leader, multi-site logistics company
WALMARTSAM'S CLUBHOME DEPOTNIKEFEDEXUPSPEPSICOMCKESSONCARDINAL HEALTHTHERMO FISHERABBOTTNEWELL BRANDSHANESBRANDSTIMBERLANDCRATE & BARRELSTITCH FIXRYDERKENCORADIALSADDLE CREEKSHIPMONKMATERIAL BANKCOOPER LIGHTING

Built on the infrastructure you already trust

Microsoft AzureSQL ServerMongoDBPostgres
The problem

Getting data out of each site is where the work piles up.

Every deployment sits behind a link you do not control.

Delayed features

Dashboards, diagnostics and reports wait on data from the sites.

Stale visibility

A view that is a day behind is a view nobody trusts.

Manual recovery

A link drops, an export fails, someone re-runs it by hand.

Repeated integration work

Every new site means the same collection job, rebuilt and re-tested.

Engineering diverted

Collectors, retries and monitoring eat time meant for your product.

Sites that must keep working

Anything that competes with the local database gets switched off.

At a glance

What redfly does

Your customer sites
McDonough, GAAtlanta area · Eastern timeSite databaseredfly
Lancaster, TXDallas area · Central timeSite databaseredfly
Fontana, CALos Angeles area · Pacific timeSite databaseredfly
  • Only changes
  • Compressed
  • Encrypted per site
  • Offline support
Your cloud
Central StoreLow-cost storage. Every row stamped with its site. Current to within minutes.
Your cloud applicationDashboards, support tools and analytics, built by your team.
Your users
Your customers
Your support desk
Your product team
No change to your productYour product stays exactly as it is; a small service runs beside it.
Your application, your dataThe central copy is yours to build on: dashboards, support tools, analytics.
Up to date in minutesEvery site's changes arrive within a couple of minutes over ordinary internet links.
Reliable over any linkOffline periods, high-latency links and spotty internet are handled.
What you get

Data from every site, without the plumbing.

Centralized data from every site

The current state of the tables you choose, every row stamped with its site.

Many sites per customer, one picture

All of a customer's sites, from your application.

A support desk that can see the site

Look before you call: the site's data is central within minutes.

Less to build and babysit

No collectors, retry logic or export jobs per site.

Operations come first

Dynamic throttling protects the site database under load.

Nothing reaches in

Outbound connections only. The site's network stays closed.

How it works

Five steps.

  1. 1

    A small service runs inside the site's network

    Beside the site database. Data goes out; nothing reaches in.

  2. 2

    You choose the tables and rank them

    Important tables stay current even on a slow link.

  3. 3

    Changes queue at the site

    Compressed and encrypted with a key unique to that site.

  4. 4

    They land in your central store within a couple of minutes

    One store, every row stamped with its site.

  5. 5

    Your application reads from one place

    Dashboards, support tools and analytics point at the central copy.

The full picture →
Reliability

Built for the bad days.

The link drops

Changes wait at the site and go when it is back.

Something restarts

Each table picks up exactly where it stopped.

Rows get edited and deleted

Edits and deletes carry through, not just new rows.

The site gets busy

Dynamic throttling to preserve operational database performance under load.

Design partners

Who we are looking for.

Technology at customer sites

Software, robotics or automation with its own database at each site.

SQL Server, MongoDB or Postgres

Any of the three at the site.

A central application

Existing or planned: a dashboard, support tool, reporting or analytics.

One contact, one site first

We install and run it with them, then roll out at your pace.

A contract to start, then a subscription: managing sync is a full-time job. See how pricing works

Discuss a deploymentBecome a design partner
Building the product?

What runs where, what a site needs, and where the limits are.

How it works →Running the warehouses?

Central visibility from the systems your sites already run.

Operators →
Track record

We have done this before.

10B+rows synced across 100+ sites, over ordinary internet links
Millionsof files kept in step for major US companies
20 yearsof keeping data in step over links that cannot be trusted
Also from redfly

The redfly API: reads served from memory, 70% off the database bill.

See caching and the redfly API →
Ready when you are

Talk to us about one deployment.

Tell us about one site, its database and its link. We will confirm fit and what a first site involves.

Discuss a deploymentBecome a design partner

redfly · Design-partner contract · Licensed directly from redfly