Rohit Singh
Senior software engineer. Founder of Sushraj Ventures.
I build the systems companies actually run on. Sushraj Ventures is my group: Sushraj Pharma, a pharmaceutical manufacturing consulting practice, the craft studio Arthmala, and the DCodeIntellect product line. Outside the group I am the senior software engineer behind Fundrev, an AI operating system for private capital, and co-founder and tech lead at Tunegram.
13+ years building enterprise systems in production. 3 businesses of my own under Sushraj Ventures, 6 products shipped under DCodeIntellect, and 87 technologies I have actually put my hands on.
Three businesses I own and operate, and two platforms outside the group.
Pharmaceutical manufacturing consulting, Indian craft and enterprise software, under Sushraj Ventures. Three trades held to one standard: find where the process loses money, build the system that closes the gap, then run it.
Sushraj Pharma
Pharmaceutical manufacturing consulting, from first quote to dispatch.
A consulting practice that helps pharma brands choose the right WHO-GMP and ISO certified manufacturer, rate and pack, and follows the work through to dispatch.
- Quotes and rates, compared
- The right manufacturing unit
- Packaging, artwork and documents
अर्थ Mala
Art that Heals. Patterns that Speak.
A boutique studio preserving four living Indian crafts: Lipan art, mandala, embroidery and crochet. Every piece made by hand, on commission.
- Four living crafts
- Commission-first
- One deployable unit
DCodeIntellect
The studio behind the product line.
My engineering brand and the product line under it: ERP, CRM, pharmacy management, commerce and the tooling around them.
- Six systems shipped
- Enterprise shape by default
- Built to hand over
Two platforms that do not sit under Sushraj Ventures. I co-founded Tunegram and lead its engineering. At Fundrev I am the senior software engineer, and the company belongs to its founders.
Eight layers I design, ship and keep running in production.
Durable orchestration, transactional and analytical data kept apart, infrastructure defined in a repository, and tracing that spans all of it. Every technology below is one I have taken into production and operated, and each layer names the systems it runs in.
Client
01Rendered on the server wherever it can be, hydrated only where the page is genuinely interactive.
Edge and ingress
02TLS, caching and the first authorisation decision, before anything reaches a service.
API
03One typed boundary. Every request is schema-validated and traced end to end.
Orchestration
04Long jobs outlive the process that started them, so a deploy mid-run is survivable.
Intelligence
05Model calls routed and costed through one gateway, every trace captured for evaluation.
Data
06Transactional and analytical stores kept apart, with a semantic layer over the top.
Platform
07Defined in a repository and reconciled continuously. Nothing is clicked into existence.
Observability
08Traces, logs, metrics and model spend on one pane, so an incident has one timeline.
Six systems shipped under DCodeIntellect.
ERP, CRM, pharmacy management, commerce and the tooling around them. Each built to the standard a business would need to actually run on it: authentication, role-based access, modular services and a deployment path that does not depend on me.
Five things I hold to, and what they cost when I don't.
Not a philosophy. These are the decisions that turned out to matter, learned on systems that are still running.
- 01
Model the business, not the screens
A system built screen-by-screen needs a new table for every requirement by year two. I start from the domain, what owns what, which boundaries are real, and let the interface follow. Modules expose contracts to each other instead of reaching into each other's data.
EvidenceD-ERP: inventory, payroll and finance reconcile against one ledger.
- 02
AI has to show its work
A generated number nobody can trace is worse than no number, because someone will act on it. Extraction ties back to the source document, and the lineage is part of the data model rather than a citation stapled to the output.
EvidenceFundrev: every figure tied to its source before it reaches an IC.
- 03
Access control is a migration, not a middleware
Role-based access added late is a filter over data the caller already fetched. Designed in, it is a property of the query. I put roles in the schema on day one, when it is the cheapest it will ever be.
EvidenceSingle-tenant isolation with RBAC across the portfolio systems.
- 04
Ship to the edge, cache honestly
Most pages are content and should cost nothing to serve. Static where static works, edge where latency is the product, dynamic only where the data genuinely changes per request, with the security headers set rather than assumed.
EvidenceTunegram on Cloudflare's edge; this site static-exported with a real CSP.
- 05
Build it to be handed over
The measure of a system is how well it runs when I am not the one running it. Typed contracts, modular structure, and documentation written for the person who inherits it, which across four ventures is usually someone I hired.
EvidenceSix systems shipped and maintained under DCodeIntellect since 2018.
What I reach for, and why it is that one.
Chosen per problem rather than per habit, which is why there is both a document store and a relational one on this list, and why .NET is still here.
Languages
Typed where it earns its keep, and .NET still earning its place.
TypeScriptJavaScriptHCLSQLPythonC#VB.NET
Frontend
Server components where the page is content, client state only where it is earned.
Next.jsReact 19Tailwind CSSReact Hook FormZodPlotly.jsGlide Data Gridreact-grid-layoutVue 3Vite
Backend
REST contracts a second team can pick up without a handover call.
Node.jsExpress 5REST APIsZodKoaASP.NET
Data
Transactional, analytical and cached, each chosen for the job it actually does.
PostgreSQLClickHouseRedisCubeAirbyteMongoDBSQL Server
AI systems
Agents that cite their sources, because an unsourced number is not an answer.
LiteLLMArize PhoenixClaude Agent SDKRAG and retrievalAWS TextractAgentic workflows
Orchestration
Long-running work that survives a restart, a deploy and a bad afternoon.
TemporalRabbitMQArgo CDGitHub Actions
Cloud and infrastructure
Everything reproducible from a repository, nothing clicked into existence.
AWSKubernetesTerraformDockerKustomizeVPC and VPC endpointsS3ECRCloudFrontHPA and PDBsSealed SecretsCloudflareVercelNetlify
Observability
Traces, logs and metrics from one story, including what the models cost.
OpenTelemetryGrafanaLokiTempoGrafana FaroPrometheus
Security and identity
Built for an audit, because in this domain there is always going to be one.
WebAuthnSAML SSOArgon2JWTTOTPIAM and IRSANetwork policiesHelmet and rate limitingCloudTrailSOC 2 controls
Document processing
Finance runs on PDFs and spreadsheets, so the parser is a first-class concern.
pdf.js and pdf-libSheetJSExcelJSofficeparserCheerioIMAP and MIME parsing
Tooling
The unglamorous half that decides whether anything ships twice.
Git and GitHubPlaywrightESLintPrettierPostmanVS CodeVisual StudioAtlassianTrelloSlack
Verified, where verification exists.
Every certificate links to the issuer's own record rather than an image of a PDF. Degrees and schooling are on the CV.
2025
2024
2017
O Level
National Institute of Electronics and Information Technology (NIELIT)
Tell me what you're building and where it's stuck.
Open to founding-engineer, staff and advisory conversations
- Phone
- +91 82196 22638
- Based in
- Daulatpur Chowk, Himachal PradeshIST · UTC+05:30