I build intelligent systemsthat move beyond the screen.
I design and ship production-focused software where intelligent interfaces, secure backends, realtime infrastructure, and physical hardware work as one system.
ENGINEERING RANGEInterface → API → Realtime → Device
SELECTED WORK
Products with real architecture behind the interface.
Each project is presented through the decisions that make it usable in production: identity, persistence, transport boundaries, failure handling, deployment, and long-term maintainability.
01
MONIKA / AI SESSION
M
MEMORY ONLINE
How can I help you today?
Summarize my current project plan.
Ask Monika…↗
FEATURED SYSTEM / 01
Monika AI
Multimodal AI companion platform
A production-oriented AI companion with persistent conversations, editable memory, multimodal input, device sessions, reminders, quotas, and administrator controls.
Persistent AI memory
Multimodal interaction
Revocable user sessions
Architecture
Node.js and Express coordinate authentication, MongoDB-backed conversation state, Firebase services, and a dual-path Gemini workflow for immediate responses and asynchronous memory updates.
A full-stack messaging application with contacts, persistent conversations, media sharing, profile controls, server-backed preferences, and browser audio/video calls.
Persistent realtime chat
WebRTC audio/video
Production security controls
Architecture
Spring Boot owns security, REST operations, MongoDB persistence, GridFS media, and STOMP messaging. WebRTC carries peer media while WebSocket signaling coordinates call state.
I turn ambitious ideas into systems that can actually be operated.
I’m an Artificial Intelligence and Data Science student based in Nagpur, focused on building deployable software and tangible hardware. My work spans secure sessions, realtime communication, AI memory, backend APIs, responsive interfaces, and ESP32-driven physical feedback.
I prefer explicit architecture over hidden magic. I evaluate projects through security, latency, observability, failure recovery, deployment, and maintenance—not only whether the happy path works locally.
Identity, authorization, validation, secret handling, and abuse controls are planned as request-flow concerns—not added after the interface is complete.
Boundaries before features
Clear ownership between client, API, realtime transport, persistence, AI, and hardware keeps systems maintainable as they evolve.
Operate what you ship
Health checks, failure states, rate limits, logs, graceful degradation, deployment configuration, and recovery paths are part of the product surface.
START A CONVERSATION
Have a product, platform, or intelligent device worth building?
I’m open to full-stack engineering, AI integration, realtime platform, and hardware-connected work.