Skip to main content
This section is for root administrators only.
Database Servers are the PostgreSQL instances where tenant databases are provisioned. You can have multiple servers to distribute tenants across regions, performance tiers, or for compliance with data residency requirements.
Database Servers list showing server names, hosts, and connection status

​
Database Server Fields

​
Connection Status

When you open the Database Servers page, each server shows a connection status badge:
  • Connected (green) — The platform successfully reached the server and validated the credentials
  • Disconnected (gray) — The server is unreachable or credentials are invalid
  • Last checked timestamp — Shows when the status was last verified
Click Recheck to manually test a server’s connection without making any changes.

​
Server Purpose

Database Servers are where tenant databases are physically created and hosted. When you create a new tenant, the platform:
  1. Connects to the database server using the credentials stored here
  2. Creates a new PostgreSQL database for that tenant (e.g., tenant_acme_corp_2024)
  3. Runs all required migrations to set up the tenant’s schema
  4. Returns a ready-to-use tenant environment
A tenant’s database remains on its assigned server for its entire lifetime — server assignments cannot be changed after tenant creation.

​
Add a Database Server

1

Go to Database Servers

Click Database Servers in the root admin sidebar.
2

Click New Server

Fill in the Name, Host, Port, Username, and Password.
3

Test Connection

Click Test to verify connectivity before saving. This checks that the host is reachable and the credentials are valid.
4

Save

Click Create. New tenants can now be assigned to this server.
Set one server as the Default so it is pre-selected when creating new tenants. This saves time when provisioning multiple tenants on the same server.
The database user provided must have the CREATEDB privilege in PostgreSQL. Without it, tenant database creation will fail silently. Test the connection and check server logs if tenant creation does not provision a database.

​
Assign to Tenants

When creating a tenant, select which database server to provision it on. Existing tenants cannot be moved between servers through the UI.

​
Frequently Asked Questions

This depends on the server’s hardware (RAM, CPU, storage) and the size of each tenant’s data. As a rough guideline, a standard server with 8GB RAM can comfortably handle 50–100 active tenants with moderate transaction volumes. Monitor server load and add additional servers when you approach capacity.
Yes. Add multiple servers in different regions and assign tenants based on their geographic location. This reduces latency for tenants and helps with data residency compliance.
DuitPOS requires PostgreSQL 13 or later. PostgreSQL 15 or 16 is recommended for best performance and security.
Update the password in PostgreSQL first, then edit the server record in the dashboard and enter the new password. Click Test to confirm connectivity before saving.

Tenants

Manage business accounts on this platform

Root Users

Manage platform administrator accounts

LHDN Admin

Configure platform-wide e-invoicing credentials