Anyone can generate a service skeleton now. The hard part was never writing the code — it's knowing which seams are safe to cut, what order to move things in, and what to leave alone until it's actually ready. That's eleven years of backend judgment, not a prompt.
Email hello@ankshilp.in Usually replies within a day.one deploy, one point of failure → independent services, deployed and scaled on their own
What I do
The code is the easy part. The real work is figuring out which pieces of your system are safe to pull apart, sequencing the move so nothing breaks in production, and knowing what to leave untouched for now. Done incrementally, alongside your existing system — not a rewrite from scratch.
Building a backend from scratch in Go for a product that's past the prototype stage and needs to handle real traffic, real data, and real failure modes from day one.
Diagnosing slow endpoints, memory leaks, flaky deploys, and scaling bottlenecks in an existing Go, Java, or Python backend, without a rewrite.
Background
No team of juniors, no handoffs. If you hire Ankshilp Software, I'm the one reading your code and writing yours. Currently also learning Rust for systems-level work where Go's garbage collector gets in the way.
Proof of work
Live product · built solo
A DNS filtering service built on DNS-over-HTTPS and DNS-over-TLS — it sits between a user's device and the internet, encrypting and filtering DNS lookups in real time to block ads, trackers, and malicious domains before a connection is even made.
It's the kind of system that has to be fast on every single request, has no tolerance for downtime, and deals directly with the networking and protocol-level detail that most backend work never touches.
How it starts
A call or email thread about what's slow, what's fragile, or what you're trying to build — no proposal, no pitch deck, just figuring out if this is a fit.
I look at your current system (or requirements, if it's new) and come back with a specific plan: what would move first, what stays put for now, and a realistic estimate.
Work happens in shippable pieces, alongside your existing system where possible, so you see progress and can change course early rather than at the end.
Get in touch
Send a few lines about your backend — what it does, what language it's in, what's not working — and I'll reply with honest thoughts on whether a migration or rebuild actually makes sense for you.