Cloud database

With the Singularity Database; development, security, subscriptions, data policies and resource budget allocation can be managed via a web-based UI. All of the data is owned by identities (end-users), who can grant other identities or groups tailored access rights to its data.

Its user interface can be used to administrate the database, as well as for developing and authoring new applications, deploying and managing SaaS applications, running internal apps right inside the database, as well as handling end-user support, price plans, subscriptions, and more. It is designed to Build, Deploy, and Scale SaaS.

You don't need to build APIs

We have got you covered with highly scaleable multi-tenant micro services APIs already available covering most use-cases for handling data, and they are all abstracted and available through our easy to use object oriented SDK. The client application hands over its local data to the CloudBackend SDK, which in turn in real-time syncs it with the Singularity Database.

Think of it as moving the hand-off point of the cloud from being a container or virtual machine in the cloud to be a SDK running within your app on devices, where everything inbetween is done for you.

Stateful devices

The application state is kept on devices through the SDK, 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 through a built-in transaction manager.

SDK - The local database

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 cloud database and platform. The SDK is used in apps, devices, containers and virtual machines interacting with CloudBackend.

It works as a cache and data pump to and from CloudBackend and is used for building apps or connectors in the cloud to existing databases, APIs, or services that is interfaced into the Singularity Data Model. The SDK can be used to feed AI/ML, data lakes or third party cloud services, since the entire database and data model is event-based.

Provided services

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 apps, since it provides most of the backend functionality like; database, identities, authentication, subscriptions, price plans, payments, end-user communication, push notifications, client-client communication, statistics and KPIs on how your SaaS business is going and more. All delivered directly into your apps through the client-side SDKs.

A superior experience

It is easy to get accustomed to the easy of use and built-in functionality of CloudBackend. It replaces in most case 100% of the required backend development, and in many cases up to 70% of the code required to be developed for each supported device like Android, iOS, Web, and Linux.

This means that security, privacy, scalability, global availability, collaboration, and instant data availability within apps is native to the CloudBackend service. Think of it as a platform to work with active real-time data through a single unified data model that is the same within the apps you are building as in the cloud.