The whole suite, installed in your own data center.
Dashboard, discuss, todo, channels, helpdesk, CRM, knowledge base, survey, collection, broadcast, hospital, voice, and the data manager — one deployment, one database, one backup policy you control.
Premises is the complete PDS suite, installed on your own servers. One login gives access to every module the company is licensed for, and every record stays inside your network.
It is built for organizations that treat customer data as an internal asset: banks, hospitals, telcos, manufacturers, and government-adjacent operations that cannot depend on an internet connection to serve customers.
- 1Database for every module — contacts, tickets, calls, and appointments
- 12+Modules in the same deployment, no per-module licence server
- 100%Data inside your network; nothing leaves unless you route it out
Installed where the data already lives.
The stack runs on your own servers: application, database, queue workers, and the telephony node when voice is included. We size it against your concurrency and storage, install it, and hand over the runbook — access stays in your hands.
- Application, database, and worker sizing agreed before installation
- Telephony node included when the voice module is part of the scope
- Installation runbook and administrator handover at the end of the project
One install, every module, no integration project between them.
Because the modules share one database, a conversation can create a ticket, a ticket can raise an appointment, and an appointment can send a reminder through the same WhatsApp connector. Nothing needs a connector project to talk to its neighbour.
- Contacts shared by CRM, helpdesk, channels, and hospital
- One WhatsApp and email connector used by every module
- One permission model across the suite, scoped per role
Backups, upgrades, and monitoring you can audit.
Database backups follow your schedule, upgrades are delivered as a versioned release with a rollback note, and the application exposes health checks for the modules you rely on. The audit log records who changed what.
- Versioned releases with upgrade and rollback notes
- Health checks for application, workers, and telephony
- Audit log for configuration and permission changes
| # | Subjek | SLA |
|---|---|---|
| 1841 | Gagal login aplikasi | 2 jam |
| 1842 | Permintaan reset kata sandi | Selesai |
| 1843 | Invoice belum diterima | Hari ini |
What the on-premise plan includes
Full module set
Dashboard, discuss, todo, channels, helpdesk, CRM, KB, survey, collection, broadcast, hospital, voice.
Data manager
Dataset import and export with reference data kept consistent.
Voice node
PBX node, SIP trunks, IVR flows, queues, and recordings inside your network.
Identity
Roles and permissions per module, scoped per team.
Reporting
Operational reports per module, exportable without a second tool.
Support
Installation, handover, and an agreed support window.
From sizing to handover
Which modules in phase one, and who owns each process.
Concurrent agents, storage for recordings, and backup window.
Base install, reference data, and the import of existing contacts.
Administrator training, runbook, and the first upgrade window agreed.
Questions before an on-premise project
Whose hardware?
Yours, or a colocation you already trust. We size it and install on it.
Who runs backups?
Your team, following the runbook we hand over. We can operate them under a support agreement.
How do upgrades work?
A versioned release with notes and a rollback path, applied in a window you choose.
Can we start with one module?
Yes. The module set is a scope decision, not a licence decision.
Plan an on-premise deployment.
Send your server specification and the modules you need. We return a sizing recommendation and an installation checklist.