01 — AI engineer · six years shipping software

AI systems for
businesses that
haven't met AI yet.

I design and build the agents and back-end systems that quietly do the work — for distributors, founders, and teams who'd rather see results than slide decks.

Currently
Bluehost · agents framework
Building
Neev · VeriCite · curat.money
Shipped
12,434 commits · last 12mo
Based in
India · working globally
scene.liveagent-graph · three.js
four agents · cursor-reactive · reduced-motion safescene/agent-graph.v2
02

About

Portrait of Abhishek Kaushik

The short version

I'm Abhishek — an AI engineer who builds agent systems that businesses can actually run.

For the last six years I've been shipping software — AI and platform engineering for the past stretch of it, most recently on the agents framework behind Bluehost's AI products. Outside of that, I'm building Neev, a modular operations platform for Indian MSMEs starting with textile distribution — because the most exciting place for AI right now isn't another consumer chatbot. It's the 63 million businesses still running on WhatsApp messages and paper ledgers — 6.34 crore, per the National Sample Survey Office's 2017 Key Indicators of Unincorporated Non-Agricultural Enterprises.

My way into AI was Neural Networks: Zero to Hero, Andrej Karpathy's video course on building neural networks from scratch in code. I didn't just watch it — I built micrograd and makemore from scratch to understand what I was watching. That habit, going to the foundations rather than the abstractions, is how I work on most things. Including this site.

  • NowBluehost · agents framework backend
  • BuildingNeev · MSME operations platform
  • Co-founder / CTOVeriCite · curat.money
  • Writesagent systems · AI for traditional business
03

Selected work

Five case studies, ordered by strategic weight. Each is a problem in the client's words, an approach, what shipped, and honest scope on what was and wasn't included.

  1. 01Hero case · MSME thesis2026 — now

    Neev

    Bringing AI to an industry that still runs on WhatsApp.

    A modular operations platform for Indian textile distributors — built to be boring where boring matters, and quietly smart where it counts.

    Role
    Co-founder & CTO — product, architecture, build
    Stack
    Next.js · Postgres · multi-tenant monolith
    Evidence of
    MSME depth · systems & product discipline
    Read the case study
  2. 02AI systems depth2026 — now

    VeriCite

    A retrieval stack an institution can actually trust with its own words.

    Multi-tenant institutional RAG, migrating from Fastembed ONNX to Hugging Face TEI for BAAI/bge-reranker-v2-m3. Qdrant as the backbone, Ory for identity.

    Role
    Co-founder & CTO — retrieval pipeline
    Stack
    HF TEI · Qdrant · Ory · k8s · Vercel
    Evidence of
    Institutional AI-systems sophistication
    Read the case study
  3. 03Production scale2025 — now

    Bluehost · agents framework

    The foundational platform behind Bluehost's agentic AI products.

    Where AI agents meet web-hosting reality — customer scale, production uptime, and real users with real bills. A major hand in maintaining and continuously improving the platform.

    Role
    Platform engineer · ongoing
    Stack
    Agent runtime · tool-calling · observability
    Evidence of
    Operating at scale · team context
    Read the case study
  4. 04Product breadth2026 — now

    curat.money

    A fair-comparison tool for crypto cards, built like a real product.

    Custody checks, provider coverage, multi-environment deploys — the boring-but-important scaffolding most crypto product sites skip.

    Role
    CTO · Tech Lead
    Stack
    High-throughput data pipeline · K8s · RBAC · CI/CD
    Evidence of
    Data pipeline to web product
    Read the case study
  5. 05UAT platform engineering2026 — UAT

    ClusterBid

    From monorepo checks to a real-host k3s UAT, with every mock and boundary named.

    A Go-service and Next.js platform taken through root-level validation, Helm deployment, and a mock-inference metering-to-billing smoke — pre-production proof, not a production or customer outcome.

    Role
    Engineering advisor · process & platform
    Stack
    Go · Next.js · TypeScript · Helm · k3s
    Evidence of
    Pre-production delivery · platform discipline
    Read the case study
04

Writing

First-principles notes on agent systems and AI for traditional businesses. New posts land here without a redesign.

All writing
05

What I can build for you

Three engagement shapes. Each with what's in scope, what's not, and a realistic timeline. If something sounds close but not quite, tell me what you're actually trying to do.

S/01

Agent MVP

4 — 6 weeks

A working agent system, in production, doing one thing your business needs done. Tool-use, memory, observability from day one.

  • InProblem framing, agent design, production deploy, handoff docs
  • OutBrand work, non-AI product surface area
  • FitTeams with a clear repeated workflow and real data
S/02

AI enablement for an MSME operation

8 — 12 weeks

For businesses that run on WhatsApp and spreadsheets. A layer that removes typing and memory load — not one that replaces judgment.

  • InOperator interviews, a narrow AI surface, training & rollout
  • OutFull ERP replacement, ledger migration
  • FitOwner-operators who want software that survives the day
S/03

Production-hardening a POC

3 — 6 weeks

You have a prototype that works in a demo. It needs to work on a Tuesday at 3pm with 200 users. I take it the rest of the way.

  • InObservability, eval harness, rate limits, error budgets, on-call runbook
  • OutNew features during hardening
  • FitTeams who've shipped a POC and lost a night's sleep to it
06 · feature wall

Built in the open.

This site uses the same process I'd bring to a client engagement — PRD, ADR, ROADMAP, EPM progress log, CHANGELOG, process-gate scripts. Public on the repo; linked from here.

The portfolio is itself a case study in what I build.

07

In the open

live from github · @Zireael26
Contributions, last 12 months12,434private repos included · refreshed 9 days ago
52 weeks · oldest → newest
08

Let's talk about your project.

Email is best. Tell me what you're trying to do in plain language — the industry, who uses it, what's getting in the way. I read every one.