Co-founder, FinMoon AI · Hyderabad, India

Technology leader who takes products from first commit to production scale.

I’m Vijay Sai Nandigam, co-founder of FinMoon AI in Hyderabad. I help teams ship AI, cloud platforms and decision systems they can trust, balancing speed and cost against reliability and how easy the system will be to maintain later.

Building production systems
10+ years
Infrastructure cost reduction
40%
Microservices moved to serverless
16

Track record

  • FinMoon AICo-founder
  • Google for Startups HubT-Hub, Hyderabad · selected
  • Zemoso TechnologiesPrincipal Software Engineer III
  • Amrita School of Engineering, BangaloreAlumnus · 2010–2015
  • AI systems
  • Cloud platforms
  • Kubernetes
  • Product engineering

Selected outcomes

Work with results you can measure.

From a founder’s bet to platform-scale infrastructure. Each one opens with the result, then shows how it was built.

All work

01Co-founder · AI product

FinMoon AI

Busy Indian professionals make tax, insurance, loan and investment decisions alone, against products built to confuse.

200

users in the first beta

An AI assistant that runs a structured version of the expert decision process, personalised to each user’s finances. It compares options, points out risks and hidden costs, and recommends next steps.

  • LLMs
  • Agentic workflows
  • Product strategy
Read the case study: FinMoon AI

02Principal Software Engineer I · Cloud platform

Cloud Infrastructure Migration

Sixteen web microservices ran on Kubernetes around the clock, paying for capacity even when nobody was using them.

40%

lower infrastructure cost

  • 16 web microservices moved from Kubernetes to Cloud Run

Moved 16 web microservices from Kubernetes to Cloud Run, Google Cloud’s serverless container platform. Each service now scales to zero when it has no traffic, so the bill follows actual use.

  • Google Cloud
  • Cloud Run
  • Kubernetes
  • Docker
Read the case study: Cloud Infrastructure Migration

Operating principles

Engineering decisions are business decisions.

The principles I bring to every team, product and architecture review.

  1. Architecture before AI

    Understand the constraints (cost, latency, trust, failure modes) before choosing a model. AI is one component of the architecture.

  2. Cost is a feature

    Every architectural decision is also a financial one. I design with the cloud bill open in another tab.

  3. Ship the MVP, earn the scale

    Build the smallest thing that proves the problem is real, with seams in the right places so it can grow without a rewrite.

  4. Platforms are products

    Internal platforms have users too. If developers route around your pipeline, the pipeline is wrong.

What I help solve

Where I’m most useful.

Three kinds of problem I take on, judged by what ships and what it costs to run.

  1. AI systems that reach production

    Take an LLM feature from a demo that impresses to something you can trust, measure and afford.

    • LLMs and RAG
    • Evaluation
    • Agentic workflows
    • Retrieval and latency
    • Observability and safety
    Discuss an AI system
  2. Cloud and platform architecture

    A reliable, observable platform that developers want to use, designed with the cloud bill in view.

    • Kubernetes
    • Distributed systems
    • Storage and networking
    • Deployment
    • Developer platforms
    Review a platform architecture
  3. Product-to-scale execution

    Ship the smallest thing that proves the problem is real, with seams that let it grow without a rewrite.

    • MVP architecture
    • Cost discipline
    • Engineering practices
    • Scaling strategy
    • Technical leadership
    Plan a path to production

The lab

Systems I build after hours.

Where I test ideas before betting a team on them: orchestration, storage and agents, on real hardware at home.

Explore the lab

Kubernetes on Raspberry Pi

Seven Raspberry Pi 5 boards running upstream Kubernetes, with every app deployed from Git by Argo CD. It runs the photo server, n8n, Postgres and this website.

  1. git
  2. Argo CD
  3. control plane
  4. workers
nodes
1 control plane, 6 workers
hardware
Raspberry Pi 5, 8 and 16 GB
runs
Kubernetes 1.35 (kubeadm)
  • Kubernetes
  • Raspberry Pi
  • Argo CD
  • Linux
Read the build notes: Kubernetes on Raspberry Pi

Agentic Home Automation

An n8n agentic workflow that reads email notifications and switches smart MCBs (miniature circuit breakers) accordingly.

  1. email
  2. n8n agent
  3. MQTT
  4. breaker
trigger
email notification
agent
n8n workflow
actuator
smart MCB over MQTT
  • n8n
  • Node.js
  • MQTT
  • IoT
Read the build notes: Agentic Home Automation

This site is served from the home-lab Kubernetes cluster, built and rolled out by Argo Workflows and Argo CD on every push.

Writing

Notes from the build.

Notes on production AI, platforms and leading teams, written down so the next person doesn’t have to learn the same lessons the hard way.

All writing

Leadership3 min read

Architecture before AI: a checklist for putting LLMs into production

Most teams choose a model first and discover their constraints later. Here is the order I work in instead, and the patterns that make GenAI systems production-grade.

TakeawayRank what an AI feature needs (accuracy, latency, cost per useful outcome, explainability, data sensitivity) before choosing a model.

Architecture7-part series4 min read

Enterprise MVP, end to end: from the first workshop to production

An enterprise MVP moves through six phases (requirements, architecture, database design, development, CI/CD and deployment), and each phase must end with a written artefact that someone signs off.

Portrait of Nandigam Vijay Sai (Vijay Sai Nandigam)
Hyderabad, India

About Vijay Sai Nandigam

I’m a millennial who thinks like a Gen Z hacker in a lab, always asking why, how, and what if.

I’ve spent a decade writing software, shipping it, running it in production and leading the teams that do that work. Today I co-lead FinMoon AI, an AI decision assistant for personal finance in India. Before that I was at Zemoso Technologies, where I grew to Principal Software Engineer III.

My path went from intern to software engineer, senior engineer, principal engineer and then founder. Each step widened the blast radius of my decisions, from a function to a service, then a platform, then a company. So I think about technology the way an owner would. I weigh risk, cost and speed, and I think about the people who have to live with the system after it ships.

Questions

Quick answers.

How Vijay Sai works, in a few short sentences each.

More answers on the About page

How does Vijay Sai approach AI projects?

Vijay Sai works out the architecture before choosing a model: cost, latency, trust and failure modes come first, and AI is treated as one component of the system.

How does Vijay Sai keep cloud costs down?

Vijay Sai treats cost as a feature, because every architecture decision is also a financial one. Moving 16 web microservices from Kubernetes to Cloud Run, where idle services scale to zero, cut infrastructure cost by 40%.

What runs in Vijay Sai’s home lab?

A 7-node Kubernetes cluster on Raspberry Pi 5 boards, a ZFS RAID-Z1 NAS on OpenMediaVault, Immich for family photos, and an n8n agent that switches smart circuit breakers. Vijay Sai tests ideas there before betting a team on them.

Where did Vijay Sai study?

At Amrita School of Engineering, Bangalore, from 2010 to 2015.

Contact

Building something difficult?

Let’s compare notes. I help teams turn an AI idea into a product that holds up, clear a platform bottleneck, or plan how the system should grow next.

Discuss an architecture challenge