Available for new work

I ship the whole thing.

Live now: a Hindi newspaper, a dental clinic, an AI reading tool. Next.js, Python, and code you own.

  • Homepage for Dr. Ashisha Singh, a prosthodontist in Rajnandgaon

    doctorashishasingh.com

  • PDF Lens workspace showing a document open with a highlighted sentence

    pdflens.in in testing

  • SAT PATH homepage with a Hindi masthead and the day's local stories below it

    satpath.in

Three things running in production.

Real domains, real users, no mockups. I built the interface, the server and the deployment for each one. Under every screenshot is exactly what shipped.

doctorashishasingh.com

Dr. Ashisha Singh

A prosthodontist in Rajnandgaon. Patients were finding her in directory listings. Now they find her on her own domain, in language they can read.

What shipped

  • Custom Next.js site, no page builder and no template
  • Treatments in plain words: crowns, bridges, dentures, implants
  • Maps for the clinic and for training at GDC Raipur and CDCRI
  • A contact path that works with one thumb on a phone
  • Structured data and meta so the practice surfaces in local search
  • Next.js
  • React
  • TypeScript
  • Tailwind
  • Vercel
Open doctorashishasingh.com
The clinic homepage introducing Dr. Ashisha Singh and her practice
A practice page that reads like a person, not a brochure

pdflens.in

PDF Lens

Reading a dense document normally means leaving the page to ask a chatbot. PDF Lens keeps the answer beside the sentence you highlighted.

What shipped

  • Highlight any sentence, then pick Explain, Teach, Example or Code
  • Answers open nested, so the thread never disappears mid-read
  • Chat scoped to the document, with each answer tied to its page
  • Embeddings run locally, so the file does not leave the machine
  • In testing now. The repository stays private until it ships
  • React
  • Express
  • pdf.js
  • RAG
  • Local embeddings
Preview PDF Lens
PDF Lens with a document open and the answer panel beside the text
The reading surface, before a question is asked

satpath.in

SAT PATH

A weekly Hindi newspaper in Durg and Bhilai, in print since 2008. They needed a desk that files seven days a week, not a page that waits for Thursday.

What shipped

  • Hindi first, with a full English edition at /en
  • Thursday e-paper, unlocked by a paid subscription
  • Razorpay checkout at 49 rupees for 30 days and 499 for a year
  • Weather, Sensex and Nifty across the masthead
  • Advertise, donate, grievance and legal pages
  • Sections, search and an editor desk for daily filing
  • Next.js
  • TypeScript
  • i18n
  • Razorpay
  • Vercel
Open satpath.in
The SAT PATH masthead with the daily web desk and local reporting below it
The masthead, and the desk that now files every morning

What I take on.

One person across the whole build, from the first screen to the server it runs on.

Product surfaces

Interfaces built for real people on real phones, not just demoed on a laptop. Fast, readable and responsive down to 360 pixels.

  • Next.js
  • React
  • TypeScript
  • Tailwind
  • Vite

AI that stays grounded

Retrieval, embeddings and streaming answers that stay tied to the source instead of inventing one.

  • RAG
  • Embeddings
  • Agents
  • OpenAI
  • Gemini

Python behind the scenes

APIs, queues and scrapers that run on a schedule with nobody watching.

  • FastAPI
  • Django
  • Flask
  • Celery
  • Scrapy

Deploy and keep alive

Ship it, wire the database, put it behind a domain with TLS, then hand over the keys and the repository on the way out.

  • AWS
  • Vercel
  • Docker
  • Linux
  • Nginx
  • Postgres
  • Redis
  • CI/CD

Tools I reach for.

Frontend
Next.js · React · TypeScript · JavaScript · Tailwind · HTML5 · CSS3 · Vite
Backend
Node · Python · FastAPI · Django · Flask · Celery · REST APIs · Jinja2
AI
RAG · Embeddings · Agents · OpenAI · Gemini · Streaming · Prompt design
Data
PostgreSQL · MySQL · Redis · Supabase · Schema and system design
Runtime
AWS · Vercel · Docker · Linux · Nginx · Git · CI/CD
Automation
Scrapy · Telethon · Tesseract · Scheduled jobs · Third-party APIs

Seven days, start to live.

A fixed scope and a fixed price before any code is written, and a real preview URL from the second day.

  1. Day 1

    Scope it

    One written page: what is in, what is out, what it costs, when it lands.

  2. Days 2 to 5

    Build it

    Working screens on a preview URL you can open any time, not a status update.

  3. Day 6

    Harden it

    Mobile pass, SEO, structured data, analytics and a speed check on real hardware.

  4. Day 7

    Hand it over

    Your domain, your repository, your keys and a walkthrough of how it runs.

Tell me what
needs building.

Send the scope. If it fits, you get a fixed price and a date before any code starts.

Engagement
Fixed price, 1,500 to 4,000 USD
Escrow
Half up front, held through Upwork
Hourly
60 to 80 USD when the scope cannot be fixed
Timezone
IST, with an overlap across US mornings
Capacity
About 30 hours a week, a few clients at a time
Handover
Repository, domain and keys are yours