01
Web engineering
the thing people actually use
Full-stack applications end to end — interface, API, database and the deploy that puts them in front of someone.
ReactNext.jsDjangoPostgreSQL
I'm Prabhat.Game Developer
I build immersive experiences with code, design, and spatial thinking.
- 6
- projects shipped
- 3
- web · geomatics · games
- <1d
- typical reply time
ReactNext.jsTypeScriptTailwindDjangoPostgreSQLPythonDockerOpenCVLeafletQGISUnityUnreal EngineDigital TwinGaussian Splatting
Three fields, oneway of thinking
They look separate on a CV. In practice they all come down to modelling space and then making it interactive.
02
Geomatics and spatial
where it is, properly
Real projections, spatial indexes, LiDAR and digital twins. The half most stacks fudge until it breaks.
PostGISLiDARDigital Twin3D Gaussian Splatting
03
Game development
systems you can play
Engine work, level design and gameplay systems. It is where I learned to think in 3D space before it was my job.
UnityUnreal EngineC#C++
Work I take on
Seven things I do well. Most projects are some combination of two or three of them.
Web applications
The whole thing, front to back — interface, API, database, deployment.
Next.js + TypeScriptDjango RESTPostgreSQL
WebGIS and mapping
Interactive maps that stay fast when the data stops being small.
LeafletPostGISvector tiles
Spatial analysis
Proximity, routing, overlays and everything that needs a real projection.
GiST indexesQGIS / ArcGISgeoprocessing
LiDAR and point clouds
Processing pipelines that turn raw scans into layers you can act on.
classificationrasterisationGIS export
Applied computer vision
Detection and tracking pipelines from video, built to run repeatably.
YOLOv8OpenCVKalman tracking
APIs and integrations
Auth, payments and third-party services wired in without leaking keys.
JWT authpayment gatewaysDocker
Games and interactive 3D
Playable builds and interactive scenes — engine work, level design and the systems underneath.
UnityUnreal EngineC# / C++
Things I have built
Games I have shipped
PC builds where the engine work is the point — terrain tooling, movement systems and levels that teach themselves.
From a rough idea to something running
Four steps, no surprises. You always know what is being built and where it has got to.
01
Scope it
We agree on what the thing actually needs to do before a line of code exists. Fewer features, clearer ones.
02
Design the data
Models, endpoints and spatial schema first. Get this right and the interface almost writes itself.
03
Build in the open
Small commits, working deploys early. You see progress every week rather than at the end.
04
Ship and hand over
Dockerised, documented and yours. No black boxes and nothing that only I can maintain.
Skills
Four areas I keep sharp — the web stack I ship with, and the spatial work that sits underneath it.
Frontend
Interfaces that stay fast and legible at every breakpoint.
ReactHTMLNextjsCSSJavascriptTailwindCSSTypescriptReduxThree.js
Backend
APIs, auth and data models built to be handed over.
DjangoDjango RESTJWT AuthPostgreSQLRest APIDocker
Geospatial & 3D
Spatial queries, digital twins and analysis on real coordinates.
PostGISLeafletArcGISGIS AnalysisDigital Twin3D TilesPoint CloudsArrival Space3D Gaussian Splatting
Game Development
Engine work and level design, mostly Unity and Unreal.
UnityUnreal EngineGame DesignLevel DesignC#C++
A developer whoreads the map
I trained as a Geomatics Engineer and ended up building for the web. The overlap turned out to be the interesting part — most products eventually need to know where something is, and that is where a generic stack starts to creak.
- Two disciplines, one buildI write the application and I understand the spatial data underneath it. That is usually two people.
- Data model before pixelsSchema, projections and endpoints get settled first, so the interface has something solid to sit on.
- Nothing you cannot maintainDockerised, documented, conventional. No clever tricks that only make sense to the person who wrote them.
- Honest about scopeIf something is a bad idea or outside what I do well, I will say so before you have paid for it.
thesis, in numbers
Automated road defect monitoring from LiDAR point clouds — the project that pulled the two halves of my work together.
- 2.34h
- LiDAR model training
- 754k
- points processed
- 24.31
- PSNR achieved
- 6
- projects shipped
Before youwrite in
The things people usually ask first. Anything else, just send it over — I reply within a day.
What kind of work are you available for?
Full-stack web projects and geospatial work — freelance, contract or full time. I am based in Kathmandu and work with teams in any timezone.
What does your stack usually look like?
Next.js and TypeScript on the front, Django REST on the back, PostgreSQL with PostGIS when the data has coordinates. Docker for anything that needs to run somewhere other than my machine.
What makes the geospatial part different?
Most developers treat location as two float columns. I studied Geomatics, so I work with real projections, spatial indexes and LiDAR point clouds — which matters the moment your queries stop being simple.
Can you take a project from scratch?
Yes. Scoping, data modelling, the build, deployment and handover. I would rather own the whole thread than pick up a half-finished one, though I am happy to do either.
Do you work on machine learning too?
Applied computer vision, mostly — YOLOv8 detection, tracking and classification pipelines. My thesis used LiDAR and YOLOv8 for automated road defect monitoring.
How do we start?
Email me with a paragraph about what you are building. I usually reply within a day, and I will tell you honestly if it is not a good fit for me.
kind words
What the people Ibuilt for say
Short projects, long conversations. Drag the row, or leave it be and it will keep going on its own.
Prabhat took a rough brief and came back with something we could actually run ourselves. He was straight with us about what was worth building and what was not, and the site has been steady since the day it went up.
SRSaurav Raj KhanalBhumlu ConstructionKavre, Nepal · 2025
onBhumlu ConstructionWe came in with a spreadsheet and a vague idea of a map. Prabhat turned it into something our dispatchers actually use every day, and he explained the trade-offs in language we could follow.
ASAayush ShresthaOperations Lead, Logistics startupKathmandu, Nepal · 2025
onFood Delivery WebGIS APPDeadlines held, and the handover was the easiest part of the project. Everything was documented well enough that our own developer picked it up without a single call.
NGNisha GurungManaging Director, Retail groupPokhara, Nepal · 2024
onAutomax Ecommerce PlatformLet's buildsomething solid
Open to full-stack and geospatial work, freelance or full time. Tell me what you are building .
write to me
prabhatbhusal777@gmail.comKathmandu, Nepal local · usually replies within a day