Blog

All Blog Posts | Next Post | Previous Post

Setting up and using BaaS: How it works with StellarDS

Thursday, November 6, 2025

Backend-as-a-Service in practical use – Part 2

In the first part, we demonstrated the advantages of Backend-as-a-Service (BaaS) for businesses and developers – from rapid scaling and cost transparency to simplified data management. The second part now takes this a step further: We provide a practical demonstration of how to configure a BaaS backend and how developers can access cloud data directly from their applications using SDKs.

TMS Software Delphi Components stellards.io

To use backend services, providers often offer platform-specific SDKs ( Software Development Kits ) and libraries. This allows developers to access the service directly in their preferred language, instead of writing HTTP requests themselves. The availability of a current and powerful SDK can be a decisive factor when choosing a BaaS provider.

The basic procedure for configuring the backend and communication from an app follows this pattern. We have described the steps using the StellarDS service as an example. The procedure can be applied to other providers.

The use of StellarDS begins with setting up the backend via the browser-based dashboard. After registration and login, a new project is created, serving as the overarching unit for data structures and access rules. Within this project, one or more tables can be created to store structured data. Each table receives a unique ID and can be assigned a description. Data fields are defined for each table – for example, names, birth years, email addresses, or Boolean values. The fields can have different data types (e.g., text, integer, date, Boolean) and their number and names are freely configurable. This structure allows for clear database modeling, analogous to classic relational databases.

The next step involves setting up user roles and permissions. StellarDS offers fine-grained access control, meaning you can define which roles have read, write, or administrative rights to specific tables or fields. These roles are later assigned to specific applications or OAuth2 clients. For example, an app can be configured to only write certain data but not read it – or vice versa.

To use the API , an access token is generated. This token is managed in the dashboard under Applications and linked to an expiration date, an assigned role, and an optional user. Alternatively, OAuth2 flows can be configured to securely manage user data and sessions within an application. After this backend setup, integration into an app or frontend can begin—for example, using the JavaScript SDK, which enables access to cloud data through simple API calls . Alternative SDKs are available for using the programming languages TypeScript, Delphi, Python, and C# (.NET-based applications).

TMS Software Delphi Components

Configuring a table structure in the dashboard – StellarDS.

Let's move on to interacting with the backend from within the app. We'll use integration into a web app (JavaScript) as an example and demonstrate how to work with the SDK to, for instance, retrieve data from a 'Persons' table. The SDK can be installed, for example, via the npm package manager (console):

npm install stellards-js-sdk --save

To use the SDK, an access token is required. This is generated in the StellarDS dashboard under the menu item Applications | Access Tokens. There you will also find the project ID and the table ID. The example code for retrieving all records from the "Persons" table looks like this:

import StellarDataStore from 'stellards-js-sdk';
let defaultClient = StellarDataStore.ApiClient.instance;
let Bearer = defaultClient.authentications['Bearer'];
Bearer.apiKey = 'YOUR API KEY';
let apiInstance = new StellarDataStore.DataApi();
let project = "project_example";
let table = 789;

// Retrieve all records from the table
dataApi.v1DataTableGet(projectId, tableId, (error, data, response) => {
  if (error) {
    console.error("Error retrieving data:", error);
  } else {
    console.log("Received data:");
    console.table(data.records); // displays results in table format
  }
});

This code allows you to conveniently and securely access the data in the cloud table – without needing your own server or complex backend logic. You can easily extend this approach to create (`v1DataTablePost`), update, or delete data.

Typical functions of the SDK

API endpoints form the basis for typical CRUD operations, file handling, authentication, and the management of data structures and permissions. They can be accessed directly via the JavaScript SDK (see examples in the table).

Frequently used endpoints of the StellarDS API that are accessible via the SDK

Endpoint	Functions	Typical use
DataTableGet	Retrieve all records from a table	Display or synchronize data
DataTablePost	Add new records to a table	Create new entries
DataTablePut	Update existing records	Modify existing entries
DataTableDelete	Delete individual records	Remove entries selectively
DataTableClearDelete	Delete all records in a table	Clear table completely
DataTableBlobGet	Retrieve a file (blob) from a record	Download images or attachments
DataTableBlobPost	Upload a file to a blob field	Store images or documents
SchemaTableGet	Manage tables: retrieve, create, edit, delete	Define table structures
SchemaTableFieldPost	Manage fields within a table	Add or modify data fields
OauthTokenPost	Request an OAuth2 token	Authenticate via client login
OauthRevokePost	Revoke a token	Log out or terminate user access
UserGet	Retrieve info about the logged-in user	Identify user
PermissionsGet	Check user permissions for a project	Apply access control in the frontend
PingGet	Check if the service is reachable	Network check before API access

Developer-friendliness and documentation

The acceptance of a BaaS depends heavily on the quality of its SDKs, documentation, and support structures. An intuitive API design and comprehensive guides significantly lower the barrier to entry. Reputable providers usually offer extensive examples, tutorials, and an API reference. In the case of StellarDS, for instance, there is a "Getting Started" guide that leads users step-by-step through the basic setup (creating tables, configuring OAuth, and running initial queries).

TMS Software Delphi Components

Configuring permissions in the dashboard – StellarDS.

Ultimately, a good developer experience is characterized by clear code examples, up-to-date SDK packages, and direct contact options (such as forums or a support team). For newer BaaS platforms, the community may be smaller, making in-house testing and proof-of-concept development crucial.

Summary

Backend-as-a-Service (BaaS) allows developers to use cloud backends (database, authentication, hosting , etc.) "as a service" instead of operating them themselves. Typical BaaS functions range from data storage and user management to push notifications. Providers like StellarDS abstract these services behind SDKs and dashboards. Developers can create a project and tables, configure the API, and store/retrieve data via code in just a few steps.

The costs are structured as follows: StellarDS offers a transparent, tiered pricing model. A free plan ("Free") is available for small or non-commercial projects, allowing up to 5 tables with 10 fields each and a maximum of 1,000 records per table, including 1,000 API requests per month. Paid plans start with the "Basic" package for €19.50 per month, which allows 10 tables, up to 10,000 records per table, and 100,000 requests per month. For larger applications, the "Pro" package is available (€39.50/month), which includes features such as multi- tenant support, blob fields, and up to 500,000 requests. The most comprehensive package, "Ultimate," is designed for data-intensive business applications with up to 50 tables, 1 million records per table, 2 million requests per month, and advanced sharing and user features. All packages are available on a monthly or discounted annual basis.

TMS Software Delphi Components stellards.io

Pricing page – StellarDS.

Cloud usage inherently provides scalability and availability with a BaaS (Backend as a Service), but API costs, data protection ( GDPR ), and provider dependencies should be considered. Overall, BaaS enables a quick start and easy integration of modern cloud backends without the need to set up your own server infrastructure .

Original article in German by Elena Bochkor and Dr. Veikko Krypczyk.

You can read the full article here: BaaS einrichten und nutzen: So geht es mit StellarDS

Aaron Decramer

Cloud Development with Backend-as-a-Service

Setting up and using BaaS: How it works with StellarDS

This blog post has not received any comments yet. Add a comment.