Start a conversation

Software that has to
keep working.

We build the software that businesses and institutions run on every day — and we stay responsible for it long after launch.

See what we've builtTalk to us

What we do

Software built for one organisation, and looked after properly.

Most software problems aren't exotic. They're a report that disagrees with the register, a payment counted twice, a system nobody can change any more.

  • We build it

    Internal systems, platforms and the machinery behind them — built around how your organisation actually works, not adapted from a template.

  • We hand it over

    Your team runs the day-to-day without an engineer on call. Routine changes are something you make, not something you request.

  • We keep it working

    Software ages. We build so it can still be understood, updated and trusted years later — including by someone who isn't us.

Our work

The systems we build.

Each one has the engineering detail underneath it, for anyone who wants to check rather than take our word.

The KAMS sign-in screen, with role selection across Student, Faculty, Admin and Super Admin and PRN-based sign-in.

KernelX product · In pilot

KAMS

An attendance platform where the register, the timetable and the reports cannot drift apart.

Field
Institutional software
Operator
A NAAC A+ accredited institute
Record
KX-P-001
Built with
Next.js 16 · App Router · TypeScript · Prisma 7 · MySQL / MariaDB · Signed JWT sessions in an httpOnly cookie

Sessions are signed with jose and held in an httpOnly cookie — no external session store, so the deployment has one fewer moving part to operate and one fewer place for identity data to sit.

More about KAMS
The KernelX Relay console: a workspace overview listing sending identity, a prompt to verify your own sending domain, and an empty recent-campaigns list.

KernelX product · In development

KernelX Relay

Private email infrastructure: a control plane for high-volume sending that never owns your contact data.

Field
Infrastructure
Record
KX-P-002
Built with
Python 3.12 · FastAPI · PostgreSQL as database and queue · SQLAlchemy 2 · Alembic · Argon2id · TOTP

Postgres is both the database and the delivery queue. No broker, no Redis — which makes delivery state transitions transactional, and that is precisely where duplicate sends are born in broker-based systems.

More about KernelX Relay
The event platform's public website, showing an event landing page with booking.

Custom system · Live

Event Platform

Event discovery, ticketing, payments, attendee management and access control as one system.

Field
Platforms
Operator
A party and event organizer
Record
KX-S-001
Built with
Public site · admin console · Ticketing and payment reconciliation · Idempotent payment callbacks · Media and access control

Ticketing and payment confirmation are idempotent, so a retried or duplicated provider callback cannot double-book a seat or double-charge a guest.

More about Event Platform
See everything we've built

Engineering is ultimately an exercise in responsibility.

KernelX operating principles

Why it holds

Built to still be working in five years.

The things that make software last aren't visible on launch day. They're the reason it's still fine two years later.

  • It keeps running

    We design for the day something fails, not only the day it launches. A retried payment can't charge twice. Backups get tested rather than assumed.

  • Your data stays yours

    We collect what the system genuinely needs and nothing more. You can see it, export it, and take it elsewhere.

  • Someone can change it later

    Written to be picked up by the next engineer, whether or not that engineer is us. No lock-in by accident.

  • It works for everyone

    Readable, operable by keyboard, and tested on real devices. Accessibility is part of building it, not a repair afterwards.

How we build

By the numbers

Counted, not claimed.

Every figure here is one we can show you the working for.

6

Systems in the registryEvery system KernelX has designed or built, including the ones still at concept stage.

Tell us what has to
keep working.

Describe the problem rather than the project. We'll tell you honestly whether it's worth building — including when the answer is no.

Start a conversationcontact@kernelx.in