XFQ/About
XFQ Innovation PLT
We build things that have to work on Monday.
XFQ Innovation is a Malaysian software engineering partnership. We are small on purpose: the person who designs a system is the person who writes it, deploys it, and answers when it misbehaves. There is no account layer between you and the engineer.
Operational software, owned end to end.
Our work sits in the category where failure is visible: a data feed a grid operator is waiting on, the ledger a company reports from, the message a patient is expecting. That shapes how we build — fewer moving parts, boring dependencies, explicit error handling, and documentation written for the person who inherits it.
We currently run three platforms. Each began as a specific operational requirement rather than a product idea, which is why each one does its job properly and does not pretend to do the others'.
- WebGSO — grid-compliance forecast delivery and a client dashboard for large-scale solar.
- OrbitOne — invoicing, stock, accounting, HR and pipeline for Malaysian SMEs.
- MediSMS — multi-tenant messaging with consent, approval, delivery tracking and audit.
Four positions we hold, even when they cost us work.
The specification belongs to whoever consumes the output
If a client's regulator publishes an inconsistent document, we implement the inconsistency and say so — because the thing that matters is whether the submission is accepted, not whether the code looks tidy in isolation.
We would rather tell you a number is missing than invent one
Where a data source does not exist yet, our dashboards say "not connected". Where a long-range forecast is modelled rather than measured, the documentation says so. A system that quietly fills gaps with plausible values is worse than one that admits them.
Technology choices should age well
We choose the stack that a small team can still operate in five years, not the one that is fashionable this quarter. Server-rendered where a build step would become a liability; a modern framework only where it genuinely earns its place.
If we cannot do it well, we say so
We would rather decline a project than take it on and learn the domain at the client's expense. When a requirement sits outside what we do, we will tell you that in the first conversation.
What we actually reach for.
Application
Server-rendered web apps · modern SPA dashboards · TypeScript · Python
Data
Relational and time-series databases · pipeline design · SQL reporting
Integration
REST · MQTT · industrial protocols · SMS & payment gateways · MyInvois
Operations
Containerised deployment · Linux hardening · automated TLS · server provisioning
Work with us
A short conversation is usually enough to tell.
Describe the operational problem in your own words. We will tell you whether it is something we can do well, and if it isn't, we will say that too.