8 yrs in prod · 50+ projects shipped · 5 Frappe marketplace apps
2 certified Airbyte connectors · 1 offline-first Flutter SDK on pub.dev
Not a "passionate developer." Not "results-driven." Just someone with 8 years of evidence:
- Frappe/ERPNext systems running in state governments and across multi-state NGO programmes — the kind that can't have downtime, can't lose data, and have to work for non-technical users in the field
- Offline-first mobile via Flutter — wrote the SDK because the problem wasn't solved; field workers in zero-connectivity zones needed ERPNext on their phones and nothing existed for it
- Data pipelines that give analytics teams warehouse-fresh HR data daily, without custom ETL code — two certified Airbyte connectors in the official catalogue as proof
- AI/RAG systems that turned 10,000+ pages of government policy documents into a chatbot that answers in seconds, cited and accurate
- Multi-tenant SaaS on Kubernetes/ECS where new tenants provision in under 20 minutes — used to take days
The through-line: I find the problem that everyone is working around, and build the thing that removes it.
Before this existed, Frappe/ERPNext had no offline story for mobile. Field workers either needed internet or they didn't use it.
An offline-first Flutter SDK built around the realities of rural India deployments — intermittent connectivity, cheap Android devices, and field workers who can't retry a failed submit and walk away.
What it handles so you don't have to:
- Local SQLite persistence with schema migrations
- Mutation queue — writes survive app restarts and network loss
- Background sync when connectivity returns — no manual trigger
- Conflict resolution — server wins by default, configurable per DocType
- Full Frappe REST API abstraction — same API whether online or offline
If you're building a Frappe mobile app, this is where to start.
| App | What it actually does | Link |
|---|---|---|
| 🎨 Frappe Desk Theme | Upgraded visual hierarchy and typography — zero core modifications, drop-in installation | → Marketplace |
| ☁️ Multi Cloud Storage | Routes file attachments to S3 / Azure Blob / GCS with per-DocType rules — unlocked data residency compliance without touching app code | → Marketplace |
| 💬 MSG91 Integration | SMS, OTP, and WhatsApp from Frappe workflows natively — no middleware, no webhook plumbing | → Marketplace |
| 📝 PCAT Exam | Timed assessments, auto-scoring, and digital certificate issuance inside Frappe — no external exam platform needed | → Marketplace |
| 🔗 Shortnr | Short links with click analytics managed inside your Frappe instance | → Marketplace |
| Connector | Outcome | Docs |
|---|---|---|
| Greythr Source | HR analytics teams get daily-fresh payroll, leave, and attendance in Redshift/BigQuery — no custom ETL | → Airbyte Docs |
| Keka Source | Same for Keka — incremental sync, schema auto-detection, certified and listed in the official catalogue | → Airbyte Docs |
Patches merged that fixed production-affecting bugs for the global community — the kind that appear in real deployments, not toy repos. Active in issue triage and code review.
Languages
Frontend & Mobile
Backend & Platform
Cloud & Infra
Data & AI
I'm open to:
- Collaborating on Frappe, ERPNext, or offline-first mobile tooling
- Consulting on cloud architecture, data pipelines, or AI/RAG systems
- Reviewing complex system design problems — drop an issue or reach out
If you're using the Frappe Mobile SDK or any of the marketplace apps and hit something broken: open an issue. If it's a production blocker, say so — I prioritise accordingly.
The best abstractions are invisible. The best systems are the ones nobody talks about — because they just work.