Nimesh Regmi
I'm a Kathmandu-based full-stack developer building web applications, Flutter mobile apps, Django backends, and AI integrations. Independent, not agency-run β you talk directly to the person writing the code, not a project manager relaying messages.
What I do
My development focus
Web & Mobile
- β’Next.js / React / TypeScript
- β’Flutter / Dart
- β’Progressive Web Apps
Backend & APIs
- β’Django / Python
- β’REST API Design
- β’PostgreSQL / Redis
AI & Data
- β’TensorFlow / PyTorch
- β’LLM Integration
- β’ML Pipeline Design
Architecture
- β’SaaS Multi-Tenant
- β’CI/CD / DevOps
- β’Performance Optimization
Each of these areas has a page of its own explaining what a project in it involves, how long it usually takes and what it costs β see all services.
What I have shipped
Production work, with results
These are systems with real users, not side projects. Each one links to a case study covering the architecture, the problems that came up, and how they were solved.
Four are shown here; there are eight written up in full, and three of the clients have said something on the record about what it was like to work with me.
GymTaar
2023Fitness platform for trainers and members, built with Flutter and Laravel.
500+ active users. Live on the App Store and Play Store.
Read case studyβBus Management System
2023Fleet and ticketing platform replacing paper-based booking, on Django and Next.js.
60% reduction in booking errors.
Read case studyβFake News Detection
2022NLP classifier using LSTM neural networks, deployed behind a REST API.
94% classification accuracy.
Read case studyβForest App
2024Offline-first Flutter app for community forestry committees in remote areas.
Published on the Play Store. Works with no connectivity.
Read case studyβVerify it yourself
Work you can open right now
Hiring a developer eight thousand kilometres away comes down to one question: is any of this real? Three of these apps are installable from the App Store or Google Play, where Apple and Google have already verified a publisher exists. The rest are live sites serving their owners' customers today. None of them need a password.
- App Store
GymTaar
Fitness platform for trainers and members. Flutter + Laravel.
Openβ - Google Play
Forest App
Offline-first field app for community forestry committees.
Openβ - Google Play
EntranceDose
Exam-prep app for NEB, CEE and MBBS students. Flutter + Laravel.
Openβ - Live product
BabalCloud
Cloud infrastructure provisioning SaaS with Stripe billing.
Openβ - Live site
gymtaar.com
Marketing site for the fitness platform above.
Openβ - Live site
TravelWings
Travel services platform for a Nepal-based operator.
Openβ - Live site
BipinCreates
Marketing site built for a creative agency as their developer.
Openβ - Live site
Nikunja Regmi
Portfolio site for a professional video editor.
Openβ
My commit history is public on GitHub, and the reasoning behind decisions like choosing Agora over raw WebRTC, or SQLite queues over optimistic sync, is written up across the case studies and the blog.
Working from Nepal
Distance, honestly accounted for
I have delivered work for clients in Australia, the United States and the United Kingdom from a desk in Kathmandu. It works, but not by accident β it works because the overlap is planned rather than hoped for. Here is exactly what it looks like from your side.
- Language
- English, for everything. Briefs, calls, commit messages, code comments, API docs and handover notes. Every page on this site was written by me, which is the sample.
- UK & Ireland
- Three to four hours of same-day overlap. Your morning is my afternoon, so a question sent before lunch in London is normally answered the same working day.
- Continental Europe
- Four to five hours of overlap with CET and CEST β the widest of any region, which is why most of my European work runs on a same-day rhythm rather than a next-day one.
- Australia & New Zealand
- Three to four hours of overlap in your afternoon. Sydney standups land inside my working morning.
- United States
- Almost no overlap inside standard hours, so US calls are scheduled in my evening β 19:00β22:00 in Kathmandu is roughly 09:15β12:15 US Eastern. Arranged in advance, not ad hoc.
- Working week
- Sunday to Friday. Nepal's weekend is Saturday, so Friday is a normal working day here and Sunday is not a favour β one extra working day at each end of a Western week.
The full version β the six stages of an engagement, what you get each week, which tools we work in and what I need from you to keep it moving β is on how I work. Rates and engagement models are on pricing, with real starting figures rather than βcontact usβ.
Working with me
The practical details
- Based in
- Kathmandu, Nepal (NPT, UTC+5:45)
- Clients in
- Nepal, Australia, the United States, and the United Kingdom
- Response time
- Within 24 hours, on email or WhatsApp
- Engagement
- Fixed-price or hourly, agreed in writing before work starts
You can reach me directly on WhatsApp, by email at regminimesh7@gmail.com, or through the contact form. My code is on GitHub and my background on LinkedIn.
My philosophy
βGood software is not just how it works. It's how clearly it helps people move forward.β
I care about products that balance business goals with user needs, strong foundations with fast iteration, and ambitious ideas with practical execution.
How I work
Simple process.
Serious craft.
I start with the real problem, make progress visible, and leave every project clearer than I found it.
Understand
Clarify the goal, users, constraints, and what success should look like.
Build
Choose the right tools, ship in small steps, and keep feedback moving.
Improve
Measure what matters, refine the details, and prepare the product to grow.
Next step
Tell me what you are building
The first conversation is a free 30-minute call, in English, at a time that works in your timezone rather than mine. Bring the problem, not a specification β working out what actually needs building is part of the job. You will have a reply within 24 hours, and I will tell you plainly if your project is not something I am the right person for.