The CloudBackend

CloudBackend and its Singularity Database enables customers to build their solution on a virtual database and intermediate data layer decoupled from all existing cloud providers to make their service become distributed with automatic roaming and sharding of data to wherever their users are — optimized by speed, scalability, or low cost.



With the Singularity database, subscription, data policies and resource budget allocation can be managed via a web-based dashboard. All of the data is owned by a user, who can grant other users and groups tailored access rights to its data.

Node Replication

The data in an edge node can quickly and automatically be replicated to other nodes across both geographies and cloud providers. This data roams with the user, becoming both mobile and local. As a traveling user leaves a geography, the local copy is removed once the service discovers it is no longer needed there. Furthermore, while traditional data management systems would have to replicate large chunks of data to high cost, CloudBackend copies only the objects requested. This reduces the resources needed, reduces cost, and increases speed.

node replication

No-Code Singularity Database

The Singularity database delivers the next generation No-Code backend service. With data distribution managed by a No-Code Singularity Database — the next step after serverless infrastructure for data — orchestration of edge nodes in every corner of the world can be avoided. The client application hands over its local data to the CloudBackend SDK, which in turn will find a suitable place to store it. With time, the application can grow, step by step, to new areas of the edge as the business and budget expands. Configurable subscription policies determine where in the edge copies of data objects may reside. Managing code or containers at the edge for handling data is a thing of the past.

Stateful devices

The application state is kept in the client application, while the data service in the cloud can be seen as stateless. This enables development of applications where multiple users can interact and operate on a set of shared data at very high speed and with high transaction volumes. During a network failure, data changes are cached, and as the network connection is restored, synchronization of data changes with the cloud happens automatically.



Application development for the end-user is done with a Software Development Kit (SDK) which provides an abstraction layer functioning as a secure window to the data storage service in the cloud. The SDK is used in devices, containers and virtual machines implementing the end application at the edge.

It works as a data pump to and from the edge platform and is connecting to machines, sensors and human interfaces. The SDK can integrate with Artificial Intelligence (AI) and Machine Learning (ML). The SDK takes care of network discovery and communications, network failures and is keeping the state of all logged-in identities.

Core functionalities of the Service

What does the CloudBackend service at a high level do? It replaces the entire need to build a cloud backend for most SaaS, IoT or mobile app services with its serverless no code commitment, while also making it possible to have the backend service globally distributed through edge infrastructure clouds to achieve acceleration and a superior low latency user experience.


The CloudBackend architecture is modular by design.

Why developing with CloudBackend is superior


Old practices with extensive development of multiple backends and client/server data pumps.


The CloudBackend dbPaaS model saves time and money, and gives multiple and flexible deployment possibilities.