One company. One OS.
On your premise.
Padu OS is the operating system for a Malaysian company: planning, automation, data and AI departments on one set of records, running on hardware you own.
What it is.
Most growing companies do not run out of software. They run out of the person who copies data between six tools. Padu OS is the alternative: one system, one login, one set of records — the customer, the employee and the invoice are the same record, not three exports.
One set of records.
A lead from an ad is the same contact on the pipeline, the same customer on the invoice, the same employee on the payslip. Switch on a new department and there is nothing to re-enter.
Departments that answer.
Finance, HR, operations and sales agents read the live records, answer in plain language, and can act — sending, approving, paying or closing — but only within the permissions of the person asking.
Local rules, in the product.
EPF, SOCSO, EIS, PCB, SST per line and e-invoice submission are part of the system, not a plugin you configure later.
Your server, your keys.
Installed on a Linux server you control, or on Windows with WSL2. It runs on hardware you already own, on your network, with no public cloud in the data path.
How inference works.
"Data never leaves the building" is a claim you should be suspicious of. Here is the honest version.
Records stay. Prompts travel.
Your database, documents and files never leave your server. When an agent answers, the prompt it sends — the question plus the specific rows it was allowed to read — goes to an inference service we operate, or to a model you host yourself if you have the hardware.
That is a real trade-off, so we make it visible: every agent run is logged with what it read, and you can turn hosted inference off entirely at the cost of running a smaller local model.
An agent that can act is only safe when it can never act as more than the person asking. That is the whole design.
What it doesn't do.
Every serious software decision starts with the limits. These are ours.
- Agents act with your permission, never beyond it. An agent can send, approve, pay or close a record — but only what the user who invoked it is already allowed to do. Every action lands in the audit log under that person's name, and anything above a threshold you set still needs a human click.
- Statutory submission stays yours. Padu OS computes contributions and prepares the filings; the submission to the statutory body remains a step a human takes.
- Hosted inference means prompts leave. If that is unacceptable, plan for a GPU on your side — and budget for it.
- No stock valuation or audit-grade year-end close in the first release. If you need that, we will tell you to keep your accounting system and integrate instead.
How you buy it.
Annual licence by invoice, or monthly by card if you would rather have automatic renewal. No trial that quietly turns into a subscription you did not order.
Scope
Which departments, how many users, what your statutory obligations are, and what hardware you already have.
Quote
A written quotation per site, with the licence term and the deployment work priced separately. SST-exempt where it applies.
Deploy
We install on your server, migrate the opening balances and records, and run it alongside your current tools until it is trusted.
Activate
You receive a signed licence file. The system verifies it locally — no phone-home, no seat server, no surprise shutdown.
Run the company on one system.
Tell us the departments, the headcount and the server you have. We will tell you what it takes to put Padu OS on it.