Independent .NET & Azure engineer · Nepal

Building software the way production teams actually need it.

I'm Bipin Paul. I design, build, and ship backend systems, web apps, and Azure-hosted services with ASP.NET Core, Blazor, and C#. Most days I'm somewhere between API design, database modelling, deployment pipelines, and the things that keep production calm.

See work on GitHub Read the blog Open resume

What I'm shipping ERP & QMS platforms ASP.NET Core, Blazor, and SQL Server — backend services and product UI for daily operational use.

Where it runs Azure-hosted services Container Apps, Functions, App Service, with managed data, queues, and storage tuned to the workload.

How it gets there Containers & CI/CD Docker, GitHub Actions, and Azure Pipelines so deployments are routine and recoverable.

Day-to-day stack

.NET 10
ASP.NET Core
Blazor
C#
Azure
Docker
GitHub Actions
PostgreSQL
SQL Server

What I focus on

Six places most of my engineering time goes.

From API design to data modelling and the delivery pipeline. The same things I do on real, paid client work — not a wishlist.

Backend & web apps

ASP.NET Core, Minimal APIs, Blazor, and EF Core for application logic, APIs, admin workflows, and product-facing web applications.

Azure cloud

Container Apps, Functions, App Service, Azure SQL, Storage, Cosmos DB, and Service Bus — cloud-hosted .NET services with managed data and messaging.

Containers & CI/CD

Docker, GitHub Actions, Azure Pipelines, and Portainer — repeatable builds, containerized applications, and deployment pipelines that teams trust.

Data

SQL Server, PostgreSQL, and Azure Cosmos DB — relational and document data models for business applications, designed alongside the product, not after it.

Ways of working

Remote collaboration, Agile delivery, clean architecture, and production support — the engineering habits around the code that decide how the system actually ages.

Writing & OSS

Technical blogging, sample apps, .NET Foundation member — reusable notes and small open-source utilities pulled out of real project work.

Open source & public work

Things I keep open on GitHub.

Public repositories, sample apps, and a starter platform — the parts of my work that get to live in the open.

Featured · Krafter

A modern .NET full-stack starter built like a real product.

Krafter is a vertical-slice, multi-tenant .NET platform with a Blazor WebAssembly front-end. It's the opinionated starting point I keep reaching for when a new product needs to be honest about architecture, identity, and deployment from day one.

Vertical slice architecture Multi-tenant Blazor WebAssembly .NET 10

Open Krafter on GitHub

Reference architecture

A delivery surface that stays inspectable end to end.

UI
Blazor hybrid front-end Composable pages, typed clients, feature-aligned folders.
API
Minimal API slices Routes, validation, and handlers grouped by feature, not by layer.
Data
Migrations & persistence Schema changes are checked in, applied automatically, reviewable.
Ops
Containers & CI/CD Docker images and pipelines so production stays a routine event.

Reference app C#

UrlShortener

URL shortener built with ASP.NET Core Minimal API, PostgreSQL, Auth0, and Blazor WebAssembly.

Minimal API
PostgreSQL
Auth0
Blazor

Developer tool C#

GitWorktreeManager

Tooling for managing Git worktrees more easily across day-to-day branch work.

Git
Tooling

Utility C#

ScreenShift

Open source utility for screen and workspace workflow improvements.

Open source
Workflow

Sample C#

BlazorDisplaySpinnerAutomatically

Blazor sample for showing loading state automatically during API calls.

Blazor
UX

Sample C#

Blazor.Seo.Friendly.FlickerFree

Examples for SEO-friendly, flicker-free Blazor rendering.

Blazor
SEO
Prerendering

Resume

Professional background & technical experience.

A concise PDF overview of my .NET, Azure, backend, data, and delivery work — written for hiring teams and technical reviewers.

Open resume Download PDF

Writing