Custom software, built around the way you work.
Gen IO designs and builds the systems a business runs on: matched to the process your team already follows, secured from the first design decision, and deployed on infrastructure you control.
How a Gen IO system is built.
Three properties we hold to on every engagement. Together they are the reason a delivered system is still in use in its second year.
- Built to the job your team does
- No modules you never open
- Your vocabulary in the interface
- Role-based, least privilege
- Every write attributable
- Encrypted in transit
- Linux, or Windows with WSL2
- Inference on your GPU — or ours
- No public cloud in the path
What we do.
Three lines of work, often in combination. Each one is something we have built and continue to operate.
Systems built to your process.
Line-of-business software where nothing on the shelf fits: field applications, operations, ledgers, integrations. We map how the work runs today and build to that map, so the system follows your process rather than asking your team to learn a vendor's.
02 — Padu OSOne OS, on your premise.
Our own product: planning, automation, data and AI departments on one set of records, licensed per site and installed on your server.
03 — On-premise AIModels that run on your hardware.
Agents and assistants over your own records, with inference on your GPU — or ours as a service, with every run logged.
Security, decided at design time.
It is the first architecture decision and the last thing we test. These are the defaults every system we deliver is built to.
Closed by default.
The common failures in custom software are rarely sophisticated: a screen that trusted the browser, a query that did not filter by company, or an administrator account that did not need to exist. We remove those three classes of mistake in the architecture, rather than hoping a review catches them.
The design decisions are documented for you, and the evidence sits inside the system: who changed what, when, and from where.
Where a client's own policy is stricter than ours, their policy wins and we build to it.
Built, delivered, running.
Three systems built for clients, and two products of our own.
PANTAU — inspection with the radio off
A tablet client for the crew and a console for the office, on one set of records. Built for a Malaysian tower operator whose inspection sites have no signal at all.
TANDA — a register tied to the steel
A durable label on each component carries a short identifier that resolves to a live record, readable by a phone in spaces where there is no network at all.
F&B Order Ecosystem — two windows, one board
An internal order system for a Johor Bahru food-delivery business cooking against two daily batches. Entered once, read on a kitchen board and in Telegram — with a record of who took what.
Padu OS
Planning, automation, data and AI departments as one system on hardware the customer owns. Licensed by signed file, deployed on their server.
Gen IO Hub
Our own ERP: sales, projects, timesheets, invoicing with SST, double-entry ledgers, payroll and asset registers. We run the company on the same stack we sell.
How a project runs.
Short cycles, visible progress, and a scope you can read before you sign it.
Scope
We map the workflow, the constraints and the failure modes, then write the scope down — including what is not in it.
Prove
A working slice on your data, on your network, before the main build starts. If the difficult part does not hold, you learn that before the main spend.
Build
Two-week increments you can use, demonstrated on a working environment rather than in screenshots.
Hand over
Deployment, documentation and a runbook your team can follow without us. We stay reachable afterwards if you want us to.
One company. One OS.
On your premise.
Padu OS is our flagship: the operating system for a Malaysian company, running as one system instead of six tools and the person copying between them. Deployed on your server, priced per site, activated with a licence file you hold.
Tell us about the workflow.
Describe what your team does today, where it becomes difficult, and what an improvement would be worth. We will tell you what it would take, what it would cost, and what we would not build.