Skip to content
DOiNhub

We build apps, AI agents and automation.

One partner for all of it. A senior engineer reads your first message and replies within four hours.

WebsiteMobile appCRMAI agentAutomationsDashboards

Run by Pavan Gupta · Varanasi, India. Working with teams worldwide.

Who “one team” actually is.

One senior engineer stays on your project from the first message to the last deploy. Around him come the specialists who own their parts, briefed off the same drawing you approved.

  • Planning

    The system on one page before anyone writes code

  • Design

    Interfaces, brand and the pages that sell them

  • Engineering

    Apps, agents, integrations and the tests around them

  • Review

    Every line read by someone who did not write it

  • Infrastructure

    Deploys, containers and the monitoring that stays honest

Specialists come from a network Pavan has worked with for years. You work with him throughout, and he stays accountable for everything that ships.

One shop. Seven kinds of work.

Every line here is work already delivered. The number beside it counts the separate builds behind it.

  1. Marketing sites and funnels

    Landing pages, booking flows, campaign funnels and the tracking behind them.

    Built alongside the campaigns they serve, so the ad and the page come from one team and tell one story.

    24builds
  2. AI agents and LLM applications

    Agents that hold down a job in production. Retrieval, tools, permissions, and a cost per run you can predict.

    A relationship analysis engine, two knowledge systems in Python and Docker, an OCR pipeline, a stock analysis assistant, a transcript search MCP server built in four days.

    18builds
  3. Web, mobile and desktop apps

    Next.js, React Native and Electron, plus the servers and containers underneath them.

    Booking systems, sales platforms, dashboards, a social product, a mobile MVP, an Electron desktop app.

    16builds
  4. Media, streaming and transcription

    Pipelines that run unattended for more than a year and stay accurate.

    A teleprompter studio at 661 commits across 382 days. A broadcast automation system at 188 commits across 402 days. Both still being pushed to this week.

    11builds
  5. Custom CRM and internal tools

    The system your business actually runs on, shaped around how it already works.

    A production CRM in TypeScript at 1,365 commits over four months. A client onboarding process. A financial integration platform.

    10builds
  6. Data extraction and pipelines

    Scrapers, parsers and analyzers. Several are public, so you can read the code before you hire anyone.

    A maps scraper, an events finder, a property data analyzer, a bulk PDF extraction tool.

    8builds
  7. Workflow automation

    n8n and Make where they fit, plain Python where the workflow outgrows them.

    A Python automation suite maintained across 324 days. A firewall auto-login. A calendar automation.

    4builds

Early practice and coursework13

Counted in the total and named here rather than folded into the rows above, because a total is only worth quoting if it is honest.

Counted from the commit log, August 2026

You describe it. We draw it. We build it.

Nothing starts with a proposal document. It starts with a drawing you can argue with.

  1. You describe it

    A message, a call, a voice note at midnight. However it arrives, a senior engineer reads it and answers within four hours.

  2. We draw it

    You get the system on one page before anyone writes code. Boxes, arrows, what talks to what, and where the work actually is.

  3. We build it

    The drawing becomes the build. You hold the repository from the first commit, and you can watch it fill up.

The tools we reach for daily.

The bench we build on every day, from the design file to the deploy. If your stack lives here, we already speak it.

  • Claude
  • Cursor
  • Figma
  • GitHub
  • Next.js
  • React
  • TypeScript
  • Python
  • Supabase
  • n8n
  • Docker
  • Tailwind CSS

Proof you can run yourself.

Two libraries, both lifted straight out of client work, both MIT, both published. One command to install, and small enough to read end to end in an afternoon.

pghybrid

Hybrid search on the Postgres you already have

pip install pghybrid

npm install pghybrid

Vector similarity and full-text search, combined by Reciprocal Rank Fusion, on plain pgvector. The clause that answers a question is often second on both signals and first on neither, which is exactly the case fusion exists to fix.

It is not better search than the BM25 extensions. It is search you can install: pg_search is unavailable on RDS, Aurora, Cloud SQL, Azure, Supabase, Neon and Heroku. pgvector is on all of them.

  • MIT
  • Python and TypeScript
  • Zero runtime dependencies
  • v0.1.4
Read pghybrid on GitHub

turnchunk

Chunking that understands who is speaking

pip install turnchunk

Parses a transcript and chunks it without ever splitting a speaker turn, so a returned excerpt never cuts a sentence in half. Taken out of the system that made 2,600 recorded client calls searchable.

  • MIT
  • Python 3.9+
  • Zero runtime dependencies
  • v0.3.0
Read turnchunk on GitHub

Both came out of work we were paid to do, and both are the part that was general enough to give away. The rest of the record is on paper below.

Read the code on GitHub

Accountable for the work

Pavan Gupta

Founder and lead engineer

You will be working with Pavan.

Every project here is run by one senior engineer with a network of specialists he has worked with for years. When a project needs a designer, an ads person or a second pair of hands on infrastructure, they come from that network and he stays accountable for the whole thing.

The practical version of that: the engineer who scopes your project is the engineer who builds it. You are never handed from a salesperson to a stranger.

Based in
Varanasi, India
Working with
Teams in the US, UK, Europe and Australia
Shipping since
2022 on this account
Replies within
Four hours, always

Co-founder, commercial

Michelle Victoria David

Marketing, sales and client relationships. She runs everything that is not the build, which is what keeps the engineering time on the engineering.

Straight answers.

How fast can you start?

Usually the same week. The first drawing of your system lands within a few days of the first call, and you can react to it before anything is committed.

Who owns the code?

You do, from the first commit. Work happens in a repository under your account or one transferred to you at the end, and you have access throughout.

What does it cost?

It depends on what you are building, so we quote after we have drawn it. That drawing is what makes the number honest, and you get it before you commit to anything.

Can you take over something already half built?

Yes, and it is a large part of the work. We read the codebase, the data, the permissions and the deploy path, then give you a straight answer on what to keep.

How a takeover runs, week by week

Can I see previous client work?

Most of it sits under NDA, which is normal at this level and is also why the record on this site is measured in commits and durations rather than logos. Forty repositories are public and you are welcome to read them.

Is it really one person?

One accountable engineer, plus specialists from a network he has worked with for years. You work with him throughout, and he stays responsible for everything that ships.

Let us talk.

Tell us what you are trying to build. You will hear back from a senior engineer within four hours, including weekends.

A reply within four hours, including weekends.

Or reach us directly

Whatever it is, describe it in your own words. Working out the technical shape of it is our job, not yours.

Varanasi, India. Working with teams worldwide.