Ishwor Subedi, Full-Stack Developer in Kathmandu.Code. Automate. Analyze.

I'm a full-stack developer, frontend to backend. When your business needs to save time, I automate the repetitive work. When it needs answers, I build the dashboards.

See the work in motion

What I do

Development comes first. Automation and dashboards come in when your business needs them.

Development

Websites, web apps, and APIs, built end to end. React and Next.js on the frontend; Node.js, Django, or FastAPI behind it.

Automation

When your team repeats the same steps every day, I automate them: tools connected, AI agents handling the routine, scripts running on their own.

Data & Dashboards

When your numbers are scattered across sheets and tools, I pull them into one dashboard, so you can see what's working and what isn't.

Some things I've built

A few projects I built end to end. More are on the Work page.

My AI and automation work is built for clients as internal tooling: LLM agents on OpenAI and Claude, wired into their systems through tool calling, MCP, and OpenClaw. Those repositories stay private.

Portrait of Ishwor Subedi, full-stack developer in Kathmandu

Who I am

I'm currently a Full Stack Developer, building products, the automation behind them, and the analytics layer on top of them. My background in data analysis with Python, SQL, and Power BI is still part of how I build today.

View more

The tools I build with

Frontend
  • React
  • Next.js
  • Vue
  • Nuxt
  • JavaScript
  • TypeScript
  • HTML
  • CSS
  • Tailwind CSS
Backend & APIs
  • Node.js
  • Express
  • NestJS
  • Django
  • FastAPI
  • Flask
  • Python
  • GraphQL
AI, Agents & Automation
  • OpenAI
  • Anthropic Claude
  • MCP
  • n8n
  • OpenClaw
Data, BI & Tools
  • Power BI
  • Pandas
  • NumPy
  • Matplotlib
  • Seaborn
  • GitHub
  • Docker

Framework agnostic by design. This is what I reach for most.

Let's build something

Got a problem worth solving, not just a feature to ship? That's exactly where I work: the product, the automation behind it, and the dashboard that proves it worked.

I build the product first, frontend to backend. Then I automate the repetitive work around it. Last comes the dashboard that shows how it's all performing.

A good product isn't just functional. It fits into how you already work, so it gets used instead of ignored. That's the standard I hold every build to, whether it's a web app, an automation, or a dashboard.