leecycle · platform↗
Leecycle
Multi-tenant ERP platform↗01
Platform · Access control
Leecycle
Multi-tenant ERP platform
One platform, many businesses — with access rules that hold across all of them.
Explore the story ↗Full-stack engineer. System builder.Architecture first · AI next
Full-Stack Engineer
Hankish Lohia
I build platforms that hold their shape — ERP, workflows and the access control between them.
Scroll to discoverBuilding in production since 2023Systems, not screens
3+
years building production software
3
platform systems built at work
3
independent products, built end to end
the work↗
01 / The person behind the workA systems perspective
Fig. 01Systems in motion
Building systems,
not just applications.
Around three years building production software. The work started as features and became systems: multi-tenant ERP modules, schema-driven workflow builders, and the access control that decides who may do what, where.
I care about the parts that don't show in a demo — data models that stay correct, rules that can be audited, and architecture that still makes sense a year later.
01
Interfaces
React, Next.js and TypeScript — screens that make complex rules feel simple.
02
Systems
Node.js services, workflows and access control that hold under real use.
03
Data
PostgreSQL and MongoDB, modelled so the data stays right as it grows.
02 / Selected work4 featured · 6 total
Systems that run
the real world.
Platforms built at work and products built on my own — each one shaped by its rules before its screens.
Multi-tenant ERP platform
Independent product · in progress
Learning platform · bilingual03 / How I workFrom domain to deploy
Understand the rules.
Then build the system.
Most of the work happens before the first screen: the domain, the data and the rules that must never break.
- 01
Understand the domain
Who uses it, what can go wrong, and which rules must never break.
- 02
Model the data & the rules
Schemas, constraints and access policies first — the parts everything else stands on.
- 03
Build it to last
Explicit boundaries, decision records and tests, so it still makes sense a year later.
Professional Working knowledge Learning
Frontend
Frontend
Interfaces that make complex rules feel simple.
- React — Professional
- TypeScript — Professional
- Redux — Professional
- Tailwind CSS — Professional
- Next.js — Working knowledge
- React Native — Working knowledgeRoadPulse
Backend
Backend
Services, APIs and the rules that guard them.
- Node.js — Professional
- Express — Professional
- REST APIs — Professional
- GraphQL — Working knowledge
- NestJS — Working knowledgeRoadPulse
- Auth & authorization — Working knowledgeCentral focus of Ramion
Database
Database
Data that stays correct as it grows.
- MongoDB — Professional
- PostgreSQL — Working knowledgeDeepest current focus
- SQL — Working knowledge
- Data modelling — Working knowledge
- Redis — Working knowledge
- PostGIS — Working knowledgeRoadPulse
Engineering
Engineering
Architecture, delivery and the systems between modules.
- ERP systems — Professional
- Architecture — Working knowledgeADRs & explicit boundaries
- Workflow engines — Working knowledge
- Docker & CI/CD — Working knowledge
- System design — LearningStudying deliberately
AI engineering
AI engineering
What separates a demo from something people depend on.
- LLM APIs — Learning
- Transformers — Learning
- RAG & retrieval — Learning
- Embeddings — Learning
- LangGraph — Learning
04 / The journey2023 — 2026
From features
to systems.
MERN Stack Developer → Full-Stack Engineer · company name
- 2023
MERN in production.
Shipping React and Node features to real users, learning what production asks of code.
- 2024
ERP modules & workflow builders.
From single features to modules: schema-driven services, forms and validation as data.
- 2025
Platform: tenancy & access control.
Tenant registry, ABAC policies, data scopes and audit — the foundations other modules stand on.
- 2026
Architecture first · AI engineering.
Designing systems deliberately, and studying how to build AI that people can depend on.
05 / Beyond the workAlways asking
I don't stop at How?
I ask Why?
Knowing how gets it working. Knowing why is what keeps it working.
- Systems
What breaks first as it grows?
- AI
What separates a demo from something people depend on?
- Machine Learning
What is the model actually learning?
- Transformers
Why does attention work as well as it does?
- Mathematics
What is the smallest idea that explains this?
- Space
How do you engineer for a place you cannot debug?
- New technologies
Which of these will still matter in five years?
06 / The next chapterLet's build it right
Open to meaningful workWant to build
something?
Let's talk ↗
Open channel. Systems, platforms, and the hard parts in between.