Clear public experiences with strong structure, responsive behavior, content hierarchy, and a useful path to action.
I build websites and systems around how the work actually needs to run.
I’m Karan Soni, a Web + Systems Developer based in Nepal, working across websites, custom software, operational systems, and independent products for local and remote work.
Purpose-built applications when the work needs rules, state, permissions, workflows, and more than a conventional website can carry.
Connected tools shaped around the real operation: handoffs, roles, repeated work, status changes, and the places where context usually disappears.
Owned directions where the responsibility continues beyond a screen into product rules, architecture, release decisions, and long-term shape.
Understand the real work before designing the surface.
Look beyond the requested screen to the repeated work, unclear handoffs, state changes, and practical constraints underneath it.
Do enough to solve the actual problem properly without creating complexity simply because more software can be built.
Structure, maintainability, responsive behavior, and future changes matter because the first release is rarely the end of the work.
The work should carry more weight than the claim.
The Builds archive holds the deeper product stories. These are a few directions where the same thinking is already operating in real systems.
Explore all buildsI’m interested in useful problems, not predetermined formats.
Bring the problem. We can work out whether it needs a website, custom system, product direction, or a smaller technical intervention.
I build websites and systems around how the work actually needs to run.
I’m Karan Soni, a Web + Systems Developer based in Nepal. I work across websites, custom software, operational systems, and independent products for clients locally, across India, and remotely.
Different formats. The same responsibility for clarity.
The format changes with the problem. The useful part is understanding what the work needs before choosing what to build.
Websites
Clear public experiences with strong structure, responsive behavior, content hierarchy, and a useful path to action.
Marketing sites · institutional websites · custom frontendsUnderstand the real work before designing the surface.
I’m less interested in adding software than in choosing the right amount of it and making the result understandable, maintainable, and useful.
Look beyond the requested screen to the repeated work, unclear handoffs, state changes, and practical constraints underneath it.
Do enough to solve the actual problem properly without creating complexity simply because more software can be built.
Structure, maintainability, responsive behavior, and future changes matter because the first release is rarely the end of the work.
The work should carry more weight than the claim.
The Builds archive holds the deeper product stories. These are a few directions where the same thinking is already operating in real systems.
Explore all buildsI’m interested in useful problems, not predetermined formats.
Dwaar System and SETU Connect continue as owned product directions while client work, websites, and custom systems keep the practice grounded in real operating needs.