Deployment Options for SARU TECH Products

Data and deployment guide

One platform, multiple deployment paths

SARU TECH products can use a managed cloud database, an organization-owned CouchDB-compatible database, or a database hosted inside a local area network. Each device can then work local-first for offline continuity or connect directly to the remote database.

Managed cloud Bring your own CouchDB LAN deployment Local or remote mode

Who is this guide for? This is the shared deployment reference for SARU TECH products that use CouchDB and PouchDB. Product availability, licence terms, and configuration fields may vary, but the deployment concepts are the same.

The simplest way to understand deployment

Deployment becomes much clearer when hosting and device behavior are treated as two separate decisions. First choose where the shared CouchDB database lives. Then choose how each device uses that database.

Where will CouchDB be hosted?

Choose one remote or shared database destination:

SARU TECH managed cloud
Your own cloud or private server
A server inside your LAN

How will each device access data?

Choose the operating mode:

Local Database stores data locally and can synchronize
Remote Database reads and writes directly to CouchDB

A common default setup Many organizations use the SARU TECH managed cloud database together with Local Database mode. Staff can continue working when the internet is interrupted, and paid accounts synchronize changes with the cloud when connectivity is available.

Choose where the shared database is hosted

All three options provide a CouchDB-compatible destination. The main differences are who manages the infrastructure, where the data is located, and whether public internet is needed to reach it.

Option A

SARU TECH managed cloud

A CouchDB-compatible database is supplied and managed with the paid licence. Each client uses a separate database.

Good fit when:

You want the simplest supported deployment
You do not want to maintain a database server
Authorized users need remote access

Option B

Bring your own CouchDB

Use IBM Cloudant or another compatible CouchDB service hosted in your cloud account, private cloud, data center, or approved region.

Good fit when:

Your organization has an approved provider
Data residency or private networking is required
Your IT team manages backups and availability

Option C

On-premise LAN

Host CouchDB on a computer or server inside the organization's local area network. Other authorized devices connect through that network.

Good fit when:

Public internet is limited or prohibited
Data must remain within the premises
Several devices need one shared local database

Common deployment combinations

Hosting and Database Mode can be combined. These examples show how the choices work together.

Managed cloud + LocalOffline-capable devices keep local data and synchronize with the SARU TECH-managed database when online.

Managed cloud + RemoteDevices work directly against the managed database. Continuous internet is required and no local PouchDB operational database is used.

Your CouchDB + LocalDevices keep local data and synchronize with your approved cloud or private CouchDB instance.

LAN + Local or RemoteLocal mode adds device-level offline continuity. Remote mode connects directly to the LAN server and requires the device to remain connected to the local network.

Choose how the device works

Database Mode controls whether the product uses a database stored on the current device. It does not select the cloud provider or server location.

Local Database

DEFAULT

This deviceLocal PouchDBCouchDB

Designed for local-first and offline-capable work.

Operational records are stored in a local PouchDB database.
With a valid paid licence and remote database, changes synchronize in both directions.
Users can keep working when internet access is interrupted.
Synchronization resumes when connectivity returns.
The Free plan supports local use on one PC without cloud synchronization.

Remote Database

PAID LICENCE

This deviceRemote CouchDB

Designed for direct, remote-only access.

Records are read from and written directly to CouchDB.
No local PouchDB operational database or synchronization process is used.
The CouchDB server must be reachable whenever the product is in use.
A valid, unexpired paid licence is required.
Remote Database is unavailable on the Free plan.

Feature	Local Database	Remote Database
Works during an internet interruption	Yes, using local data	No, CouchDB must remain reachable
Operational database stored on the device	Yes, in PouchDB	No local PouchDB database is used
Synchronization	Used when a remote database is licensed and configured	Not used; reads and writes are direct
Network requirement	Can continue offline	Continuous internet or LAN connection
Free plan	Available for local use on one PC	Not available
Best suited to	Unreliable connectivity and offline-sensitive workflows	Reliable networks where local operational storage is not wanted

Important for Remote Database users Changing to Remote Database stops the product from using local PouchDB, but it should not be treated as proof that previously stored device data has been securely erased. If your policy requires removal, first verify the remote data and backups, then use the product's Erase Local Database action with administrator approval.

LAN deployment explained

A LAN deployment uses a CouchDB database hosted on a computer or server within the same private network as the product devices. It can operate without public internet, but every device still needs a working connection to the LAN database host.

What the LAN setup contains

Database hostA reliable computer or server runs CouchDB and remains available to other devices.

Private networkAuthorized devices reach the database using its local IP address or network name.

Operational safeguardsPlan backups, firewall rules, fixed addressing, power protection, and administrator access.

Read the step-by-step LAN deployment guide

Local mode on a LAN: each device keeps its own PouchDB database and synchronizes with the LAN CouchDB server. This gives an additional level of continuity if a device temporarily loses its network connection.

Remote mode on a LAN: each device reads and writes directly to the LAN CouchDB server. Public internet is not required, but the local network and server must remain available.

Bring your own CouchDB with Alternative DB

Alternative DB allows an organization to replace the SARU TECH-managed remote endpoint with an approved CouchDB-compatible database. It can be hosted by IBM Cloudant, another compatible provider, a private cloud, a data-center server, or a LAN server.

Step 1Provision CouchDBCreate a compatible database in the approved location and confirm capacity and availability.

Step 2Secure the serviceUse least-privilege credentials, encrypted connections, access restrictions, monitoring, and backups.

Step 3Enter Alternative DBIn General Settings > Account & License, enter the approved connection URL and save.

Step 4Test the workflowConfirm login, reading, writing, synchronization, backup, and recovery before production use.

Protect the URL and credentials These details can grant access to important business or clinical data. Do not expose them in screenshots, public documents, support forums, or unencrypted messages. Use a secure handover process with SARU TECH support or your database administrator.

How to change Database Mode

Database Mode is an account setting. Coordinate a mode change with an administrator, especially when multiple people or devices use the same account.

Open General SettingsGo to Settings > General Settings.

Open Account & LicenseSelect the Account & License tab and locate Database Mode.

Choose the modeSelect Local Database (Default) or Remote Database. The remote option is disabled without a valid paid licence.

Save and allow the product to reloadSelect Save. The choice is recorded on the customer account, the database connection changes, and the product reloads.

Remote mode always needs a working connection Do not choose Remote Database for a site with intermittent internet or an unreliable private network. If CouchDB cannot be reached, users cannot read or save operational records until connectivity returns.

Which setup should you choose?

Internet may be interruptedChoose Local Database so the device remains usable offline.

Internet is guaranteedChoose Remote Database when direct access is preferred and local operational storage is not wanted.

Your organization controls hostingUse Alternative DB with an approved CouchDB or IBM Cloudant service.

The site is internal or isolatedHost CouchDB on the LAN and connect devices through the private network.

Before going live

Confirm the database location meets organizational and legal requirements.
Test every device from the network it will normally use.
Confirm user roles, authentication, device restrictions, and firewall rules.
Test local-first synchronization after a deliberate connection interruption.
Verify backups and perform a test restoration.
Document who manages the server, credentials, updates, monitoring, and incident response.

Need help choosing? Share your internet reliability, number of devices, preferred data location, internal IT capabilities, and offline requirements with SARU TECH. Those five details are usually enough to identify the most suitable deployment.