Coming soonFor sites with a poor connection

Working offline with OpenBoxes Lift

We are building a way to run OpenBoxes at a site with a poor or intermittent connection, such as a ship, a remote clinic or a warehouse, working on the same data as your OpenBoxes Lift instance in the cloud.

Being built. None of this works yet, and we do not publish dates.

Who it is for

Organizations that run OpenBoxes at sites where the internet connection comes and goes, and want those sites and the cloud working on the same data.

  • A ship that spends long stretches at sea.
  • A remote clinic or field warehouse with an unreliable link.
  • A regional office that has to keep working when its internet goes down.

What it will do

Being built. None of this works yet, and we do not publish dates.

OpenBoxes at your site

OpenBoxes on a server at your site, which keeps working while the connection is down.

One set of data

People in the cloud and people at each site work in the same OpenBoxes data. It is introduced step by step, each part only once it has been proven safe.

Changes cross at the next connection

What either side creates or changes reaches the other side after the site is connected again.

Each record has one owner

A site changes what it owns: its own locations' stock, the documents in its hands and the records it creates. A change to a record owned elsewhere is refused with a clear message.

Hand records to a site

Give a site the shared records it has to change while offline, one by one or a whole category at a time, from the portal.

Sync status you can see

A read-only page showing the sync status of each of your sites.

What does not change

  • It is the same OpenBoxes at your site and in the cloud. A few things work differently on every copy, the cloud included: posted stock transactions are corrected by an adjustment rather than deleted, and products are not merged. At a site, people sign in with their OpenBoxes username and password.
  • Records every site uses, such as products, suppliers and users, stay with the cloud unless you hand them to a site.
  • The AI assistant, webhooks, alert emails, DHIS2 reporting, the Reporting API and the scheduled export keep running in the cloud, over the data your sites have sent.
  • Phones and handheld scanners still save nothing offline. This is about a server at your site, not about phones.
  • Offline sites will not be offered on the Shared plan.

What you can do today

OpenBoxes Lift runs in the cloud today. For a site with a poor connection, you can:

  • Run OpenBoxes yourself at a site that is never onlineOpenBoxes is open source. A site that can never count on a connection can run its own OpenBoxes server, on its own.
    Self-hosting compared →
  • Look up stock on a handheld with no signal (beta)Look up in Lift Mobile keeps working offline once the app has synced its product list. Nothing is saved offline.
    Handheld scanning →
  • Use OpenBoxes Lift from any site with a connectionA Shared or Dedicated instance works from every site while that site has a connection.
    Compare plans →
  • Move a self-hosted OpenBoxes into Lift laterIf you run OpenBoxes yourself today, our migration path brings it into OpenBoxes Lift when you are ready.
    Migrating your data →

Today OpenBoxes Lift runs only in the cloud and needs a connection to use. Nothing runs at your site, and nothing syncs between a site and the cloud.

Running OpenBoxes where the connection drops?

Tell us about your sites: how many there are, how they connect today and how long they go without a connection.

Talk to us

Is the capability you need in here?

Ask about any feature: lot tracking, integrations, mobile, reporting. If we don't do something you need, we want to hear that too.

AI assistant. Conversations are recorded to improve our service. Please don't share sensitive data. Privacy