Codapulse Global — Kathmandu, Nepal
Software that runs schools., job sites., restaurants., clinics., classrooms.
We're a small product company in Kathmandu building five management systems for places where real work happens. Two are live today; the other three have dates we intend to keep.
The company
Most software for schools, sites, and clinics is built far from the people who use it.
That distance shows up everywhere: screens nobody asked for, workflows that fight the actual day, support tickets that vanish into a queue. We work the other way round — small teams in Kathmandu, each responsible for one product from the first sketch to the support inbox. When something breaks, the person who wrote it is the person who fixes it.
- Founded in
- Kathmandu, Nepal
- Products
- Five in the line
- Live today
- Skolora & Sitora
- Working days
- Sunday – Friday
The portfolio
Five products, one standard
Two systems are in daily use; three more are on dated launches. Each is built end to end by its own team — designed with the people who'll run it, supported by the people who wrote it.
In daily use
On the way
Every product page has the full picture — what it covers, who it's for, and where it sits on the timeline.
Browse the full catalogHow we work
The habits behind good software
We stay after launch
The team that builds a product keeps running it. Bug reports and feature requests go to the people who wrote the code, not a ticket queue.
One product, one job
A school system and a restaurant system should not feel like the same app with different labels. Each product is designed around the people who use it.
We ship on a schedule
Two products are live. Three more carry real dates on the timeline — and we treat those dates as commitments, not decoration.
Inside every product
Shared standards, separate products
The five systems share no screens and no shortcuts, but they're all held to the same standards.
Built for real connectivity
Slow networks and power cuts are part of the spec here, not an edge case. Every product keeps working through them and catches up when the line returns.
Nepali and English
Interfaces, reports, and receipts work in both languages, because front desks and finance offices do.
Role-based from day one
Principals, site supervisors, cashiers, and doctors each see what their job needs — and nothing else.
Local support, same day
Questions go to the team in Kathmandu that wrote the code. Answers come back within working hours, not time zones.
From Nepal
Designed and built in Kathmandu
The valley we work from runs on the same schools, sites, kitchens, and clinics we build for. We visit the classrooms, walk the sites, and eat at the restaurants that use our software — our users are neighbours, not tickets.
Timeline
Two shipped. Three on the way.
Dates reflect our current build schedule.
Tell us what you run
A school, a site office, a restaurant floor, a clinic — if one of our products fits, we'll show you around it. And you'll be talking to the product team, not a sales desk.
- 01
Write to us
A few lines about what you run and what's getting in the way is plenty to start.
- 02
See it with your day
We walk you through the product using your timetable, your site, your menu — not a canned demo.
- 03
Roll out with the team
We handle setup and training, and we stay reachable long after the first login.