01
I WANTED TO SEE FURTHER.
At eleven, I was fascinated by astrophysics. My family couldn't afford a telescope, so I started learning optics from YouTube and built one myself.
SCRL 0.00CRSR 0.00001 — HOME
FOUNDER / DEVELOPER + AI ENGINEER
SYSTEMS · AI ARCHITECTURE · PRODUCTS
SAHOL.
FOUNDER — KRONXSYSTEMS & AI — ELITE HEIGHTSSOFTWARE · AI TOOLS · PRACTICAL SYSTEMS
SCROLL02 — ORIGIN
ACQUISITION LOG
How the founder was acquired — in four entries, unpolished.
02
THE LOGIC UNDERNEATH.
Building and dissecting things was the attraction from the beginning. I wanted to understand the underlying logic — how the parts could make something more than themselves.
03
THE INSTRUMENTS CHANGED.
Now that curiosity reaches into software, AI, systems, ESP32s and sensors. The materials change. The urge to understand and make things stays.
04
I STAYED FOR THE PROCESS.
The building itself is the point now. Jack of all trades, master of a few — shipping systems that outlive the reasons they were started.
03 — ABOUT · THE FOUNDER
Builder of systems. Founder by temperament.
I'm Sahol Mohammad — founder of Kronx, working on systems and AI at Elite Heights. I build systems: software, AI architecture, products that ship. And I research the question most of the industry skips — whether AI actually helps the people it claims to help. Students first.
I think in systems before mechanisms — the why gets written before the how. Speed and rigor aren't rivals here; reversibility decides. If a decision can be undone, move now. If it can't, slow down and get it right. That one rule runs everything: fleets of AI agents on raw infrastructure, PostgreSQL on metal I manage myself, and a delivery standard of weeks, not years — without ever shipping a toy.
The operating philosophy is connection but detachment: close enough to move fast, detached enough to stay clear. Jack of all trades, master of a few — and honest about which is which. The work is the argument. Everything else on this page is just the museum built around it.
THE PERSON BEHIND THE WORK ↗TOSHINELIKEASTAR,YOUGOTTABURNLIKEONE.
Standing out is paid for in energy. I budget for the burn instead of pretending it's free.
DREAMSAIN'TWHATYOUSEEINYOURSLEEP—THEY'REWHATDON'TLETYOUSLEEP.
The filter for what gets built: if it doesn't keep me up, it doesn't get my hands.
COMFORTNEVERCREATEDALEGACY.
Comfort is a fine reward and a terrible strategy. I treat it as the former, never the latter.
SELECTED WORK
What I’ve
built.
Open a project. Separate its interface, its structure and the reason it exists.
From a shop conversation to an actionable order.
LIVE WEBSITE · 2026-09-15Open live site ↗
WHY / DESIGN / BUILD
What shaped the design.
Connect conversations to the shop's catalog, keep negotiation within the owner's limits, and turn confirmed details into a structured order workflow.
Keep the seller in control. A useful sales assistant needs constraints as well as language. Prices and negotiation boundaries belong to the shop.
Start with the actual conversation. Bangla and Banglish are central to the product's intended conversation flow.
05·B / THE EVIDENCE
Proof, in
perspective.
An idea leaves the room.
These are the places it became.
06 — VENTURES · THE PERMANENT COLLECTION
V.01KRONXThe studio-engine. Products shipped for clients and for the house — proof and revenue in the same motion.LIVE — KRONX.TECHV.02ELITE HEIGHTSAI systems and products built for real use. Capability is not the question — help is.SYSTEMS & AI — ELITEHEIGHTS.ORGV.03TANETShop conversations into order workflows. Catalog-aware Bangla and Banglish replies, negotiation within the seller's limits, and structured order details.CONVERSATIONAL COMMERCE — TANET.KRONX.TECH
07 — PROOF · WHAT’S SHIPPED
08 — WORKSHOP · HOW IT RUNS
DIVISION 4 / 4
THE FLOOR CONTINUES BELOW
09 — THE DIFFERENCE
The usual developer, and then there’s me.
THE USUAL DEVELOPERSAHOL
TASTEShips the template, tweaks the accent.Grades every pixel into one palette. Nothing is default.
CINEMATakes a screenshot and calls it a hero.Composes every frame — light, grain, negative space. Cinematography, not decoration.
ARTPulls a component off the shelf.Builds the component, then the shelf, then the room it lives in.
SPEEDA quarter to ship. Maybe two.A week’s promise — and it still isn’t a toy.
SYSTEMSWires the happy path and hopes.Architects the whole machine. Reversibility decides the speed.
D.01 — THE DESK · WHAT YOU CAN COMMISSION
The museum is free. The work is not.
Three ways to put me on something. Each one states what it is, what leaves with you, and — on the same card — when you should not buy it.
YOU GET
- a working product on a real domain
- the source, in your repository
- the infrastructure, in your name
YOU OWN
Everything. Source, domain, database, deploy keys. Nothing I run is a hostage.
DON'T COMMISSION THIS IF
START THIS — 30 MIN you want a design mockup, a pitch deck, or a thing that looks finished and isn't. No toys ship.
YOU GET
- the architecture written down before it is built
- postgres and linux managed by hand, not by a dashboard
- AI agents orchestrated in fleets, where they actually earn it
YOU OWN
The whole machine and the reasoning behind it. Intent survives the handoff.
DON'T COMMISSION THIS IF
START THIS — 30 MIN the requirements are still being discovered. Philosophy before mechanism — if the why isn't written, the how is guesswork.
YOU GET
- the agents that build, review and watch
- raw infrastructure kept by a human who reads the logs
- reversibility maintained: it rolls back in one move
YOU OWN
Your keys stay yours. Cancel and everything keeps running without me.
DON'T COMMISSION THIS IF
START THIS — 30 MIN you need someone on a rota answering tickets. This is engineering leverage, not a helpdesk.
WHAT DOES IT COST
Priced on scope, and quoted inside the first thirty minutes — not after three meetings and a proposal. If the budget and the scope don't meet, you'll hear that on the call, from me, while it still costs you nothing.
D.02 — THE DESK · THE WEEK
A week's promise, printed as seven days.
Said four times elsewhere on this page and never shown. Here it is, with the column nobody else prints: what the week costs you.
- Day 01SCOPE BY CUTTINGEverything that isn't load-bearing comes out on day one. You approve the cut list before a line is written.YOUR TIME — 60 MIN
- Day 02THE SPINEData model, routes, infrastructure. Postgres and Linux on metal I manage by hand. Nothing decorative exists yet.YOUR TIME — NOTHING
- Day 03THE FIRST REAL SCREENNot a mockup — the actual thing, on a real URL, with real data. You open it in your own browser and tell me what's wrong.YOUR TIME — 20 MIN
- Day 04THE MACHINEThe parts that do work: auth, payments, agents — whatever the product is actually for. Behind flags, so it rolls back in one move.YOUR TIME — NOTHING
- Day 05THE GRADEType, spacing, motion, palette. The day it stops looking built and starts looking made. No default anything.YOUR TIME — 15 MIN
- Day 06THE BREAK ATTEMPTI try to break it. 390px, reduced motion, slow networks, wrong input, hostile input. What survives is what ships.YOUR TIME — NOTHING
- Day 07A LIVE URLYours. Source in your repository, infrastructure in your name, deploy in one command. Shipped is the only state.YOUR TIME — 30 MIN
YOUR TOTAL — UNDER TWO HOURS
BOOK DAY ZERO — 30 MIN That is the whole ask on your side. The reason the week works is that it doesn't run on your calendar.
D.03 — THE DESK · THE HOSTILE QUESTIONS
The things you're already thinking.
Asked the way you'd ask them if I weren't in the room.
No. A template is something that already exists being recoloured. The week works by cutting, not by reusing — day one removes everything that isn’t load-bearing, which is the only reason day seven arrives. Open the collection above: nothing in it shares a layout with anything else in it.
One person, plus fleets of AI agents running on infrastructure I manage by hand. That’s the leverage, and it’s written down in the workshop room rather than implied. What you don’t get is a project manager relaying your words to a junior who has never spoken to you.
Source in your repository. Infrastructure in your name. Deploy in one documented command. Nothing I run is a hostage — that’s a design constraint, not a courtesy. If you want to test it, ask for every key on day seven and watch nothing break.
Then you want the build or the fleet, not the week. I inherit other people’s decisions without editorialising and I read logs before I read opinions. The one thing I won’t do is quietly rewrite something that already works so that it looks like mine.
Because I don’t know what you’re asking for yet, and a number invented before the scope is a number that gets revised upward later. What I will commit to: a real quote inside the first thirty minutes, from me, on the call. If your budget and the scope don’t meet, you’ll hear that then — while it has cost you nothing.
You’ll have seen it on day three, on a real URL, with real data — not at week six in a slide. Reversibility governs speed: everything ships behind a flag and rolls back in one move, so you see it early enough that changing it is cheap. That is the entire reason the rule exists.
Because each one links to the thing it came from, and because the rating shown above is 4.8, not 5. The projects with no sourced outcome display no outcome — a title and nothing else, which looks worse and is true. If a claim on this page can’t be checked, it isn’t on this page.
Anything still unanswered is a better use of the thirty minutes than anything answered above.
ASK IT DIRECTLY — 30 MIN10 — RESEARCH · THE STUDY
Does AI actually help students learn — or just feel like it does?
Capability keeps outrunning evidence. This inquiry is mine — not a venture's. I build the systems, then ask the uncomfortable question: did anyone actually learn? For the students and the people it claims to help. The honest answer is being built, measured, and rebuilt.
STATUS: ONGOING — PERSONAL RESEARCH
11 — THE LIBRARY · WHAT I READ OVER COFFEE
PULL A BOOK FROM THE SHELF
1984 — The manual for watching the watchmen.
NOW — BUILDING INSTRUMENTS, SOFTWARE & SYSTEMS · SEPTEMBER 2026
14 — THE WORKSPACE · STATE A: THE VOID
This is the actual room, photographed — lid closed, chair empty, the posters holding the wall. Everything the museum just showed you was built between that chair and those two screens. The grain gives way where you look.
S / 01 — THE VISITOR RECORD
A little proof
you were here.
Your chapters, your time, your way through. Printed onto something you can pull out of the machine.
PRESS PRINT · PULL DOWN TO TEARS / 01 — VISITOR RECORD
THERMAL
DIRECT FEED
DIRECT FEED
TICKETS — KEEP YOUR STUB
SAHOL — THE MUSEUM
ADMIT ONE · NO RE-ENTRY REQUIRED
FLOOR I · THE MUSEUMnot visited
FLOOR II · THE ACCELERATIONnot visited
FLOOR III · THE LIMITnot visited
DEEPEST POINT0 M BELOW STREET
TIME INSIDE00:00
INCIDENTSNONE
STAMPED 03:25 +06
the museum remembers you now
TORN — THE VISIT COUNTED ANYWAY
THE MUSEUM ENDS. THE BUILDING DOES NOT.
CHAPTER I ENDS AT THIS DESK
CHAPTER 1 OF 3 — 2 FLOORS BELOW THIS ONE
DESCEND — CH.II: THE ACCELERATIONBelow the museum floor: the sketchbook. The speed before the polish, the notes before the systems — how the mind actually moves.
12 — ELSEWHERE · FIND ME
THE SIGNALS I KEEP LIT