Available for select engagements · 2026

AI Architecture / Cloud Platforms / Agentic Workflows

Soumya Swaraj — AI & Cloud Architect: I build AI that works at scale.

I'm Soumya Swaraj — founder of Evergrow and a former JPMorgan Chase engineer. I help companies take AI from prototype to production: LLM agents, RAG and agentic workflows on AWS that stay fast, reliable and affordable as usage grows.

See the workSee the work
Architect
Soumya Swaraj
Now
Founder, Evergrow
Previously
JPMorgan Chase
Certified
6× AWS
Proven at
10M+ requests / day
Builds
LLM agents · RAG · AWS
Scroll
00 Introduction

Hi, I'm Soumya.

I design AI and cloud systems for companies that can't afford for them to break.

I learned the craft at JPMorgan Chase, building data platforms inside a bank that moves billions of dollars a day. Today I run Evergrow, where teams of AI agents research, write and fact-check content made for AI search.

Based in
Bengaluru, India
Now
Founder, Evergrow
Before
JPMorgan Chase
Clients
Worldwide

Available for select AI & cloud engagements in 2026.

Portrait of Soumya Swaraj
ChatGPT Claude Gemini Cursor Amazon EC2 Amazon S3 DynamoDB Bedrock

Platform engineering

Zero downtime, by design.

Decoupled, event-driven AWS platforms built to absorb traffic spikes and survive the loss of a zone without dropping a request. Run either scenario below.

Pick a scenario to watch the platform respond.

Throughput

10M+

requests a day, routed with zero downtime

Efficiency

1.5M+

compute hours saved across 400+ batch feeds

Stack

  • Aurora Serverless
  • Kinesis
  • Firehose
  • Lambda
  • S3
  • ECS
  • Bedrock

Self-healing data pipelines

  1. Detect the anomaly
  2. Diagnose the cause
  3. Resolve it automatically
  4. Before anyone downstream notices

80% fewer daily production tickets

01 Philosophy

Scale isn't something you add later.

Back in high school, I built a gaming community that grew to 15,000 members, then watched it collapse on shared hosting. The code was fine. The system around it wasn't.

Every project since has started with one question: what happens when this works? More users, more data, more agents, more money moving through it. I design for that day first, so growth shows up as revenue instead of an outage.

  1. Principle 01

    Design for the day it works.

    Capacity, cost and failure modes get planned before the first user arrives, not after the first outage.

  2. Principle 02

    Make failure boring.

    Good systems detect, diagnose and fix the common problems themselves. People handle the rare ones.

  3. Principle 03

    Measure what changed.

    Revenue earned, hours saved, tickets closed. If it can't be measured, it isn't finished.

02 The Three Pillars

What I build.
How I think.

I

Enterprise Scalability

Designing robust, highly-available cloud infrastructures capable of processing massive data throughput — without friction or failure.

AWSTerraformDistributed SQL
→
II

Applied AI & Agentic Workflows

Moving beyond basic LLM wrappers to engineer intelligent, multi-agent ecosystems that automate deep research and complex, multi-step problem-solving.

RAGMulti-AgentLangGraph
→
III

Founder's Execution

Approaching engineering through the lens of a founder. Every architectural decision driven by product-market fit, user growth, and actionable business metrics.

PMFRevenueVelocity
→
0M+
Daily requests routed
0M+
Compute hours saved
0K
Revenue in 60 days
0×
AWS certifications
03 Selected Work

Proof, not promises.

Five case files, from a bank-scale data platform to an AI content engine. What was broken, what I built, and what changed, with the numbers.

EvergrowFounder2025 — now Live

Making brands the answer AI gives.

$200K revenue in 60 days for a B2B SaaS client
7× organic traffic in 100 days for tourism agencies
The problem
Search is moving from ten blue links to one AI answer. Most brands aren't in that answer, and generic AI content won't put them there.
What I built
An AI content OS: a multi-agent system where adversarial AI personas research, challenge and fact-check every piece before it ships. We run it as a done-for-you service for startups and established brands.
The result
Content that ranks on Google and is written to be recommended by ChatGPT, Gemini and Perplexity, with revenue to show for it.
Written for OpenAI Claude Perplexity Gemini DeepSeek Google
  • Multi-agent
  • Adversarial review
  • RAG
  • GEO
Visit Evergrow

JPMorgan ChaseSoftware Engineer2022 — 2024 Shipped

Freeing a bank's reports from its most expensive hardware.

10M+ requests routed every day, with zero downtime
$1M+ in yearly savings the platform work contributed to
The problem
Thousands of accounting, settlement, regulatory and risk reports lived on in-memory clusters built for real-time trading. Fast, but costly, and some datasets ran to terabytes.
What I built
A decoupled, cloud-native replica on AWS that took over every workload that didn't need microsecond latency. I designed the streaming pipelines, the consumer SDK and the migration tooling, plus anomaly detection and self-healing.
The result
10M+ requests a day with zero downtime, in an environment that moves billions of dollars daily.
  • Aurora Serverless
  • Kinesis
  • Firehose
  • Lambda
  • S3
  • SNS
  • Athena

JPMorgan ChaseAgentic LLMs2022 — 2024 Shipped

AI agents inside a bank, before most banks tried them.

10 min to answer data questions that used to take analysts 10 days
100M+ trade requests a day on the platforms the agents watched
The problem
Data anomalies in financial reporting were caught late, often by the teams downstream who relied on the numbers. And every new data question cost days of analyst time.
What I built
LLM monitoring agents that detect, diagnose and resolve anomalies on their own. Plus on-demand natural-language-to-SQL agents, grounded with RAG and few-shot prompting.
The result
Anomalies resolved before they reached anyone downstream. Ten-day analyst requests answered in ten minutes.
  • LLM agents
  • RAG
  • Few-shot prompting
  • Text-to-SQL
  • Self-healing

JPMorgan ChaseAutomation Shipped

400 batch feeds, tuned until they fixed themselves.

1.5M+ compute hours saved
80% fewer daily production tickets
The problem
More than 400 batch feeds carried millions of transactions a day across fixed income, commodities, derivatives and regulatory reporting. Every failure became someone's morning ticket.
What I built
End-to-end optimization of the feeds, then automated self-correction so the common failures repair themselves.
The result
1.5M+ compute hours saved, and 80% of daily production tickets gone.
  • Batch processing
  • Self-correction
  • Cost optimization
04 Track record

Built things. People showed up.

Long before the enterprise work, I was shipping products that found real users. Each building in the model is one of them, sized to the audience it reached.

Building height shows audience size, on a log scale.

  1. 2014

    Mobile game guide app

    30K gamers

    Walkthroughs, tools and community Q&A for players.

  2. 2014 — 2015

    Gaming social network

    15K members

    A clan-based network for the RPG games I played, built in a ten-day PHP marathon in high school. It grew to 15,000 members, then collapsed on shared hosting. The lesson stuck: scale has to be designed in.

  3. 2015

    White-label hosting service

    ~100 sites

    Free hosting and provisioning for about a hundred sites, run before I knew the word multi-tenant.

  4. 2019

    University counseling system

    30K students

    An on-site management system that cut processing time by 70%.

  5. 2019 — 2021

    Campus ticketing & apps

    10K+ users

    The go-to builder for campus societies: ticketing and apps used by more than ten thousand students.

  6. 2019 — 2020

    Movie recommendation site

    15M organic hits

    A community-driven recommendation site that spread across 20+ colleges in India and reached 15 million organic hits through search and word of mouth.

  7. 2020

    COVID-19 tracker

    800K+ users

    Live case counts, regional breakdowns and trusted public-health guidance, shipped during the pandemic.

  8. 2020

    CMS for Virginia Tech & TIET

    2 universities

    Content platforms for two universities, alongside leading web and mobile at the Google Developer Club.

  9. 2020

    College blogging community

    50K reads

    A co-built publishing community with 50K reads and 20K social reach.

Nine launches since 2014. Most of them shipped before graduation.

05 The Backstory

Origin story.

Scalability limits everything.

SEC 01Origin
2010

A Small Town, a Slow Modem

Growing up in Dhanbad — a 25 Mbps modem and an audacious dream. Fuelled by the desire to communicate across the globe, I coded my first social network from scratch.

SEC 02Init
2014 — 2015

The RPG Gaming Era

After a 10-day PHP coding marathon, I launched my clan based gaming social network that hit 15,000 members. The site collapsed under its own weight on shared hosting. That failure taught me a lesson I've used every day since: scalability limits everything.

SEC 03Scale
2018 — 2020

Student. Builder. Lead.

Built a movie recommendation site to 15M organic hits. Shipped a counseling system used by 30K university students. Built CMSes for Virginia Tech and TIET. Ran web & mobile for the Google Developer Club. Became the campus's go-to engineer for anything that had to scale.

SEC 04Enterprise
2022 — 2024

Enterprise — JPMorgan Chase

Re-architected legacy data platform into a cloud-native platform on Aurora Serverless, Kinesis, Firehose, S3, Lambda, SNS and others. Routed 10M+ daily requests. Built some of the earliest enterprise-grade LLM monitoring agents with self-healing capabilities. Contributed to $1M+ in annual savings.

SEC 05Future
2025 — Now

Founder — Evergrow

Building the AI Content OS — a multi-agent system with adversarial personas producing rigorously-researched, authoritative content for the age of generative search. Platforms that don't just scale — they actively drive revenue.

06 The Human Element

Beyond the
architecture.

Building scalable systems requires intense focus — but the best ideas often happen away from the screen.

When I'm not architecting AI ecosystems or optimizing cloud infrastructure, I'm usually resetting my competitive drive on the badminton court or diving into a good fiction novel. I prefer "chill" travel — finding quiet hill stations or beaches over high-intensity trekking — and I am perpetually on the hunt for the perfect cup of Adrak Chai.

Badminton Fiction Chill Travel Adrak Chai