Skip to content
Niaga Labs

Independent software studio · Malaysia

Software for businesses that actually ship.

A small studio in Malaysia building production systems end to end — the storefront, the services behind it, and the infrastructure they run on.

Focus
Commerce · Quant
Built with
Go · TS · Py
Based in
Malaysia

What we do

One team across the whole stack, not a layer of it.

Most of the cost in a small product is the seams between people. There are none here — the same hands write the service, the screen and the deployment.

Backend systems

Go and Python services, event-driven where it earns its keep, boring where it does not. Schema changes reviewed as diffs, migrations that run forward and back.

Product front ends

Next.js and React storefronts and dashboards. Server-rendered, accessible, fast on the phones customers actually use.

The plumbing

One shared local stack, one command to start it. Containers, queues, object storage and search that behave the same on a laptop and in production.

Products

Things we run, not things we pitched.

Both of these are our own. They carry real data and real consequences, which is the only way to find out whether an architecture was a good idea.

Commerce platform

Niaga

In development

A factory-direct dropship store on its own microservice platform (built 2023-2026 as Desa Murni Batik).

Catalogue, orders, payments, fulfilment and search, split into Go services behind a Next.js storefront. Built to survive a real order book rather than a demo.

  • Go
  • Next.js
  • PostgreSQL
  • NATS
  • MinIO
  • Meilisearch

Quantitative research

luqman-quant

In development

A paper-trading platform for testing strategies against real market data.

Strategy backtests, walk-forward evaluation and a live paper-trading loop, with every result written to an evidence trail instead of a screenshot.

  • Python
  • FastAPI
  • React
  • PostgreSQL

How we work

Small team habits, kept even when nobody is watching.

  1. 01

    Tests green before it ships

    Exact counts quoted, never a summary. A failing test is reported as a failing test.

  2. 02

    Written down as it happens

    Every change carries its changelog entry and its ticket. Six months later the reasoning is still there.

  3. 03

    Honest status

    Skipped steps get said out loud. Nothing is called done until it is merged, documented and green.

Contact

Have something that needs building properly?

Tell us what the system has to do and what it has to survive. A reply usually comes the same day.