R
Currently building Engageo

I build web apps,
mostly backend.

Full stack developer focused on the backend — APIs, auth, databases, and how everything fits together.

View my workGitHub
ravi@dev — zsh
$ ▋
system / topologyv1.0
hover a node to inspect
CURRENT BUILDENGAGEO / 2026
View repository

Currently building — Engageo

A SaaS app for managing leads, running WhatsApp campaigns, and automating customer conversations.

architecture
platform
Engageo
CRM
Leads
WhatsApp
Campaigns
AI Engine
Qualification
Webhooks
Inbound / Outbound
Messages
Template / Session
stack
ReactNode.jsExpressMongoDBWhatsApp Cloud API
what I'm working on
  • Authentication
  • Authorization
  • Campaign workflows
  • WhatsApp templates
  • Message handling
  • Webhook processing
  • Backend APIs
  • Multi-tenant architecture
01About

Developer, not just a stack.

I started with frontend and web development during my BCA at Manipal University Jaipur — building interfaces, learning how the browser works, and shipping small things end to end.

Over time I moved deeper into the backend. I got interested in how APIs are designed, how login and permissions actually work, how databases shape what you can build, and how the whole system behaves when you add more users and integrations.

I'm not a senior developer. I'm someone actively learning the backend — APIs, architecture, networking, databases — while shipping real features along the way.

focus
  • BCA — Manipal University Jaipur
  • Full Stack Development
  • Backend Development
  • SaaS
  • APIs
  • Databases
  • Networking
02Experience

What I'm working on.

CurrentInnovatex Media

Software Development Intern

  • Working on Revenue OS, the company platform.
  • Building the WhatsApp panel — campaigns, templates, and message handling.
  • Writing backend APIs and integrating the WhatsApp Cloud API.
03Selected Work

Things I've built.

A few projects, each focused on a real problem.

01Project

Engageo

A SaaS app for managing leads, running WhatsApp campaigns, and automating customer conversations.

GitHub
Problem
Businesses juggle separate tools for leads, messaging, and campaigns. Engageo puts it all in one place.
How it works
Express routes call controllers, controllers call services for business logic, services talk to MongoDB through Mongoose. A separate layer handles the WhatsApp API.
What I did
  • Login and permissions with JWT and roles
  • Multi-tenant setup so each business has its own data
  • Campaign builder and WhatsApp template management
  • Sending, receiving, and processing messages
  • REST APIs with Express and MongoDB
Stack
ReactNode.jsExpressMongoDBWhatsApp Cloud API
04Engineering

How I think about systems.

The concepts I actually use when building.

Keeping routes, logic, and database access separate so things stay manageable.

flow
Route
Controller
Service
Repository
Database

Each part does one thing. Routes map URLs to handlers. Controllers validate input. Services hold the logic. Repositories talk to the database. When something changes, you only touch one layer.

05Technology

What I use.

The tools I reach for when building.

Frontend01
Backend02
Database03
Infrastructure / Networking04
Security05
Integrations06
06Journey

From building apps to understanding how they work.

Web Development
HTML, CSS, JavaScript basics
MERN
MongoDB, Express, React, Node
Backend
APIs, auth, data modeling
SaaS
Multi-tenancy, integrations
System Design
Services, boundaries, scale
Networking
DNS, TCP/IP, HTTP, proxies
Distributed Systems
Currently learning

Right now I'm moving from building apps to understanding how they work underneath.

07GitHub

My GitHub

A few of my public repositories.

08Contact

Have an idea?

I'm open to work, interesting projects, and good conversations.

Email meLinkedInGitHub