Rinosh A Stanley — Software Engineer and Founder
Engineer by training.
Founder by trajectory.
I'm Rinosh — a software engineer who treats every codebase like a company asset, and every company like a system to be engineered.
Five years in, my work spans the full arc: real-time messaging platforms people use daily, data pipelines that ingest millions of vehicle-registration records every night across AWS regions, and AI features — including MCP integration — shipping inside production systems.
In parallel, I founded Parawow, an AI automation studio, and I'm building Dent Intelligence, a vertical AI product for dental healthcare. The constellation you just flew through? Those are real structures. I'm still building them.
From first commit
to multi-region scale.
The Foundation
B.E. in Computer Science, Sri Siddartha Institute of Technology. Where curiosity about how things work became an obsession with how things scale.
Software Engineer · DeskFactors (BlueSecures)
Built the full UI of a production React chat application, then went deeper: XMPP real-time messaging on ejabberd + MongoDB, bidirectional WhatsApp API integration, offline-first sync with PouchDB and Dexie, and AI chatbots on Rasa and Botpress. Learned that "real-time" is a promise you keep at 3 a.m.
Software Engineer · LKQ
Expanded the stack into Golang and deep AWS. Architected and run a nightly batch system ingesting millions of RDW vehicle-registration records from the Netherlands, with an architecture scaling across multiple regions. In parallel, I work on MCP integration and AI feature development — operationalizing AI inside real production systems, not just prototyping it.
Founder · Parawow & Dent Intelligence
Running Parawow, an AI automation and software studio, while building Dent Intelligence — AI patient acquisition, engagement and reputation for dental clinics. Engineering by day, company-building always.
Full-stack means
the whole stack.
Tools change. The discipline of choosing the right one doesn't.
BACKEND & SYSTEMS
- Golang — services & batch at scale
- Node.js / Express — APIs & realtime
- Microservices architecture
- RESTful API design
CLOUD & DATA
- AWS — multi-region architectures
- Nightly batch pipelines, millions of records
- MongoDB / Mongoose
- Offline-first sync — PouchDB, Dexie
FRONTEND & EXPERIENCE
- React / Redux — production apps
- JavaScript / TypeScript, HTML, CSS, SCSS
- WebGL / Three.js — you're looking at it
- Performance optimization
AI & AUTOMATION
- MCP integration & LLM features
- AI agents & chatbots — Rasa, Botpress
- n8n workflow automation
- WhatsApp business automation
REAL-TIME
- XMPP — ejabberd messaging systems
- WebSockets & event-driven design
- Data synchronization
BEYOND CODE
- System architecture & technical strategy
- Agile leadership & code review culture
- Venture building, zero to one
Code that became
companies.
Parawow
Strategy, AI-integrated web development, and automation builds — with a partner network where clients become collaborators who bring the next project. Everything launches from here.
Dent Intelligence
Patient acquisition, engagement, and reputation management via AI and WhatsApp automation. First move in a longer game: a one-stop AI healthcare dashboard, starting with dentistry.
Scale Systems
The nightly RDW ingestion pipeline at LKQ — Golang and AWS moving millions of vehicle-registration records across regions, every night, silently. The infrastructure nobody notices because it never fails loudly.
How I decide.
Boring infrastructure wins.
The best systems run at 3 a.m. while everyone sleeps, and nobody ever tweets about them. Millions of records, nightly, silently.
Design for the failure first.
Anyone can architect the happy path. Multi-region exists because regions fail. Retries exist because networks lie.
AI-native, not AI-added.
Bolting AI on is a feature. Rebuilding the workflow around it is an advantage. I build the second kind.
Ship the company, not just the code.
Every technical decision is a business decision wearing a hoodie. I make both, on purpose.
The next structure
is still particles.
If you're building something that needs an engineer who thinks like a founder — or a founder who still ships code — let's talk.