गंतव्य
Palette
Mode
Motion

Calm stops smooth scrolling, moving art and the story’s music, and keeps everything still.

गंतव्य
Palette
Mode
Motion

Calm stops smooth scrolling, moving art and the story’s music, and keeps everything still.

Independent software engineer · IndiaOpen to new projects

I design and build calm software for complicated problems.

Independent software engineer in India. Products, AI agents and developer tools — built precisely, documented clearly, and handed over clean.

downloads of devDocs on PyPIAll-time, via pepy.tech — includes mirrors and CI.
6.1k
faster retrieval on a legal-AI platform
40%
heritage sites mapped in 3D
100+
hours teaching computer science
500+
The way I work

Software should feel quiet when it works.

Three habits behind everything on this page.

  1. Precise.

    Every number on this site traces to code, a public source, or work I can walk you through. The work runs the same way: measurable outcomes, written decisions, no hand-waving.

  2. Calm.

    Good software feels quiet — fast, predictable, easy to change. The aim is always the version that is boring to operate.

  3. Systemic.

    Draw the system before building it: data, boundaries, failure modes. The drawing becomes the plan, then the documentation.

Systems, drawn

Every build starts as a drawing.

Before code, the system: what flows where, what can fail, what the reader of the code will need. Here is devDocs v4, the documentation engine I’m rebuilding now — solid lines are built and tested, dashed ones are next.

How devDocs v4 documents a repositoryv4, in progress: it scans and parses the repository, a planner picks the files worth a model’s time, a router sends each job to the cheapest capable model under a budget — with a SQLite cache and run ledger, and retrieval for cross-file context — and one document model renders every format. Not built yet: devdocs (planned), Planner (planned), Retrieval (planned), DocModel (planned).top filescachechunkscontextdevdocsestimate · runScangitignore · rolesParseast + 5 languagesPlanner0 tokensTier routerbudget · limitsSQLitecache · ledgerRetrievalsymbol chunksDocModelmd · html · pdf
builtnot built yet
  1. planned“devdocs estimate” shows the requests and the cost first; “devdocs run” spends it, within a ceiling.

  2. A gitignore-aware walk classifies every file; parsers read Python and five more languages.

  3. plannedA zero-token score picks the files worth a model. The rest get accurate stubs from the parser.

  4. Each job gets the cheapest capable model under a hard budget; cached answers make unchanged files free.

  5. plannedRetrieval brings in the neighbouring code a prompt needs; one document model renders Markdown, HTML and PDF.

Read the devDocs write-up
Selected work

Five systems, each with a reason to exist.

Two open-source developer tools on PyPI and npm, a heritage platform that shipped and was later acquired, a desktop assistant with a memory, and a rules-first allocation engine.

With teams

Same instincts, with someone else’s users on the line.

Production work alongside product teams — measured by what changed, not by title.

2025 – now

Devslane

Client products across web, mobile and AI

  • Client-billable projects, wearing whichever hat the work needs: full-stack web, cross-platform apps in Flutter, AdonisJS back ends on PostgreSQL and Socket.io, RAG and AI features — and the system designs behind them.
  • CRM and ERP products, including owning the client-onboarding module of a live ERP.
  • A payments proof of concept that established production feasibility, and a Storybook component library now used across teams.

2025

Promptly AI

Vidhi 7.0 — a legal-AI platform

  • Cut information-retrieval latency by 40% with targeted query and architecture changes.
  • Refactored core Next.js and NestJS modules to simplify data flow and reduce coupling.
  • Rebuilt authentication end to end on Clerk — 50% fewer login failures and faster onboarding.
faster retrieval
40%
fewer login failures
50%

2024 – 25

Mero Braj

Grant-funded heritage platform

  • Wrote the proposal and secured grant funding.
  • Led a team of four to build a 3D map and 360° tours for 100+ heritage sites.
  • Held performance targets on low-end phones with lazy loading and a modular architecture; the platform was later acquired.
  • See the project

2024 – 26

Let’s Unbound

Teaching computer science

  • Delivered 500+ hours of live Python and Java instruction to US AP Computer Science students.
  • Designed project-based curricula, so students shipped working software rather than only passing exams.
  • Several students went on to competitive computer-science programmes.
hours of live teaching
500+

Odoo Combat Hackathon 2024 — Top 1% of 2,500+ teams in a 36-hour build.

Working together

How we’d build it, together.

Four kinds of work, one way of doing it. Every engagement ends with software your team can own.

  • 01

    Product builds

    Web products from first sketch to production — React and Next.js front ends, Node and Nest back ends, Postgres underneath.

  • 02

    AI & agent integration

    Assistants, retrieval and tool-calling agents that do real work inside your product, with guardrails and costs you can see.

  • 03

    Developer tooling

    CLIs, SDKs, middleware and internal tools your engineers will actually keep installed.

  • 04

    Rescue & scale

    Untangling slow or fragile code — profiling, refactors, auth and data-flow fixes — without stopping the product.

A calm way in

System review

A short, fixed-scope look at your architecture and codebase, ending in a written roadmap: what to keep, what to fix first, and what it would take. A calm way to start working together.

Ask about a review
  1. 1

    Listen

    Understand the problem, the people and the constraints before touching a line of code.

  2. 2

    Sketch the system

    Draw it first — data, boundaries, failure modes — and agree on it together.

  3. 3

    Build in the open

    Small, reviewable steps with a working version early and visible progress every week.

  4. 4

    Hand over cleanly

    Documentation, tests and a walkthrough, so your team owns it from day one.

Straight answers

Open to new projects. Replies within 24 hours. IST (UTC+5:30), working with teams in any time zone.

What does Gantavya build?

Web products, cross-platform apps, AI and agent features, and developer tooling — from open-source CLIs on PyPI and npm to client CRM and ERP products and a legal-AI platform.

Which technologies?

TypeScript, React, Next.js, Node, NestJS and AdonisJS for products; Flutter for cross-platform apps; Python for tooling, data and quantitative work; PostgreSQL, MongoDB and Redis for data; Gemini, Claude, retrieval (RAG) and the Vercel AI SDK for AI features.

Is he available?

Yes — for freelance and contract projects. The fastest way in is an email to gantavyaoo@gmail.com with the problem, timeline and a budget range.

How do projects usually start?

With an email and a short conversation. Larger or uncertain projects often start with a fixed-scope System review, so both sides know exactly what they are signing up for.

Which time zone?

IST (UTC+5:30). Working hours overlap comfortably with Europe and with US mornings or evenings.

Toolbox

Tools chosen for the job, not the résumé.

Products

  • TypeScript
  • React
  • Next.js
  • Flutter
  • Node.js
  • NestJS
  • AdonisJS
  • Socket.io
  • Storybook
  • Tailwind

Data

  • PostgreSQL
  • MongoDB
  • Redis
  • SQLite
  • GraphQL

AI

  • Gemini
  • Claude
  • RAG
  • Vercel AI SDK
  • Tool calling
  • Agents
  • Search grounding

Craft

  • Three.js
  • WebGL
  • GSAP
  • SVG
  • 360° media

Python & quant

  • Python
  • CLI design
  • Backtesting
  • NSE ETF data

Shipping

  • Vercel
  • CI/CD
  • PyPI
  • npm
  • Linux packaging
The person

Behind the work, a person.

Gantavya in silhouette at a scalloped palace window, looking out over a city

गंतव्यmeans “destination”.

I’m Gantavya — an engineer from the Braj region of India, the place Mero Braj set out to map. I like problems that arrive tangled and leave calm: a codebase nobody documented, a platform that has to run on a cheap phone, a rule that must hold through a market crash.

Off the keyboard it’s mountains, coffee experiments, reading the markets, and teaching — five hundred hours of it so far. This site is the path; if you have a project in mind, it could be the next stop.

Gantavya Bansal, smiling, arms folded, in a striped sweater

— Gantavya

Independent software engineer

Now

  • →devDocs v4 — a dependency-free engine that plans before it prompts
  • →Stuti — a desktop assistant learning to talk, and to act with permission
  • →This site — ink, paper and a pond

Off the clock

A desk at night: laptop, an open notebook of sketches, and sticky notes with diagrams on the wall
where systems get sketched first
Gantavya grinning on a mountain trail strung with prayer flags
happiest on a trail
Gantavya sitting on a grassy ridge with two mountain dogs
trail company
Gantavya in a beanie, laughing, with hills behind
cold air, clear head
A bulbul chick resting on a stone ledge
noticing small things
Gantavya in front of a temple with a golden statue
slow travel

Interlude

Take a breath.

Tap the water for a drop of ink. Hold still for a pebble.

Stay a while

The next destination

Your project could be the next stop.

Tell me what you’re building, where it hurts and when it needs to be calm. One email is enough to start.

Open to new projects · Replies within 24 hours · IST (UTC+5:30)

GitHubLinkedInPyPI