LabNexa · Community · Est. 2026

The people behind the taps.

LabNexa isn't a company. It's just three of us who got sick of watching computer labs run on paper logbooks, lost complaints, and endless "please restart the PC" messages. So we built the fix ourselves.

03 Builders
01 Mission
06 Roles
∞ Coffee

We started with a broken PC, a missing logbook, and a supervisor trying to watch four labs at once. Everything LabNexa is today came from just standing in those rooms and listening to the people who actually use them.

Our mission

To make every computer lab answer in a single tap, so no student ever wastes another minute on paper.

Craft over shortcuts

We sweat the small stuff. A caption, a colour, an easing curve. That is how trust gets built.

Small problems matter

A stuck logbook feels tiny until it eats an hour. We chase those hours down wherever they hide.

Ship and learn

Nothing lives longer in a folder than in a real lab. We ship, watch, and rewrite.

Open by default

Docs, designs, roadmap, all out in the open. If a school wants to fork us, we cheer from the sidelines.

Our members

Three minds.
One lab-sized dream.

the whole team, actually →
Portrait of Muhammad Luqman Bin Azad Khan Team Leader

Muhammad Luqman Bin Azad Khan

Team Leader · Product & Architecture

If the lab can answer in one tap, everything else is just detail.

LeadershipSystem DesignPHP / MySQL
Since Day 0 Based Malaysia
Get in touch
Portrait of Andrew Ooi Shen Xiang

Andrew Ooi Shen Xiang

Backend Engineer · Systems & Security

Security is not a feature. It is the floor everything stands on.

MySQLAuth & RBACAPIs
Since Day 0 Based Malaysia
Portrait of Muhammad Adib Ahnaf Bin Muhamad Noor Hafizi

Muhammad Adib Ahnaf Bin Muhamad Noor Hafizi

Frontend Engineer · UI & Motion

Motion is how a system says please and thank you.

CSSGSAPDesign
Since Day 0 Based Malaysia
0
Builders
0
Roles designed
0+
Screens crafted
0
Logbook buried
What we built

Six pieces.
One calm system.

everything on one tap →

Tap to open

NFC or QR opens a session in under a second. No login screens, no paper, no queue.

Live seat map

Every PC rendered as a live tile. Free, in use, faulty, or offline. Always current.

Fault reporting

Students flag a broken machine in two taps. Technicians see it ranked by impact, not volume.

Insight engine

Utilisation, peak hours, fault clusters and a maintenance score. The lab tells you where it hurts.

Role-based access

Six roles from student to admin, each seeing exactly what they need and nothing more.

Full audit trail

Every session, every fault, every edit is logged. If it happened in the lab, it is written down.

How we build

Four steps.
No shortcuts.

listen → build → ship → repeat

Listen

Two weeks sitting in a lab. We watch people tap and write down every sigh.

Sketch

Whiteboard, Figma, arguments. The best idea usually loses and the simplest one wins.

Build

Backend first, then frontend. Boring plumbing before any pixel gets to look clever.

Ship

Deploy to a real lab. Real taps, real breaks, real fixes. Repeat until calm.

Built with

Tools we trust

PHP 8 MySQL JavaScript GSAP Bootstrap NFC / QR RBAC Git
How we work

Rules we actually keep

non-negotiables

Own the boring parts

Audit logs, permission checks, duplicate-IC detection. Nobody claps for these, so we build them first. That is where trust lives.

Ship, then polish

A working feature in a student's hand beats a perfect mockup in a folder. Release early, watch real taps, fix what hurts.

Design for the tired student

Every screen is tested against one scenario. 11:55 PM, last class, battery at 9%. If it isn't obvious then, it isn't obvious.

Bury the logbook

Paper loses, paper lies, paper runs out mid-semester. Everything here exists so nothing ever depends on paper again.

Build with, not for

We stand in the labs and listen to the people who use them. Every feature started as a real complaint from a real room.

Privacy is non-negotiable

Student data stays inside the lab. No third-party trackers, no ad SDKs, no surprises in the fine print.

Our story

From broken PC
to one tap.

The spark

A dead PC and a missing logbook

A broken PC, a missing logbook, and a supervisor watching four labs at once. We decided the lab deserved better than paper.

First tap

One tag, one gesture

NFC tag on PC-07. One tap opened a session. We knew instantly this was the whole product in a single gesture.

The map

Every seat, live

We rendered every seat as a live tile. For the first time anyone could see which PCs were alive, free, or lying.

Intelligence

Sessions became insight

Sessions became insight. Utilisation, peak hours, fault clusters, and a maintenance score that ranks what hurts most.

Today

One tap, six roles

Six roles, thirty-plus screens, and a community of labs running on one tap. And we are only getting started.

From the labs

What people
actually say.

unedited, we promise

The first time a student tapped a PC and it just opened, I think half the room stopped to watch. That is the whole product.

Pn. Nurul A. Supervisor · Lab 3

I used to lose my logbook twice a month. Now I just check my sessions on my phone. It is honestly boring how well it works.

Hafiz R. Student · DCS Year 2

Fault reports used to reach me third-hand. Now I see the exact seat, the exact time, and the complaint. Fixing is twice as fast.

Mr. Tan W. Lab Technician
Questions

Things people
usually ask.

The core is open for any polytechnic or school to adapt. Reach out through any of our socials and we will share the repo and setup guide.

Any computer lab with networked PCs. The seat map, NFC tags and roles are all configurable, so it fits a 12-PC room as easily as a 60-PC hall.

Each PC carries an NFC tag or QR sticker. The browser reads it, matches it to the seat, and opens a session bound to your student ID.

Absolutely. We are three students and we would love a fourth. Backend, frontend, design, documentation, all of it is welcome.

They retire. Every session, fault and check-out that used to live on paper now lives in the system. Searchable, timestamped, and impossible to lose.

Get in touch

Say hi.
We actually reply.

three doors, pick any →

Whether you want to bring LabNexa to your lab, ask about the code, or just follow the build in public, the fastest way is one of the channels below. No forms, no waiting rooms.

Email: labnexatechnology@gmail.com Based in: Malaysia
Free for polytechnics & schools

Want to adopt
LabNexa?

Bring one-tap sessions, live seat maps and paperless labs to your campus. We walk schools through setup ourselves. No licence fees, no lock-in. Just a lab that finally answers in a single tap.