Skip to content
All work

Founder / Product

VRRentals.in

A VR hardware rental business, and the platform that runs it

Organisation
VRRentals.in
Role
Founder — operations and engineering
Period
2025 – Present
Visit vrrentals.in

Context

What the system is

Businesses want immersive experiences for a specific date and a specific room — not a permanent hardware purchase. That gap is the business.

VRRentals.in supplies VR hardware and immersive setups for events, exhibitions, product launches, demonstrations and training. It is also a real product: catalogue, booking, payments, dashboards and admin workflows.

Problem

What needed solving

Renting headsets manually does not scale past a handful of bookings. Availability, payments, customer accounts and order history all needed to become software.

  • Physical inventory — availability is a real constraint, not a database flag
  • Single operator, so admin workflows must be fast
  • Payments and authentication had to work correctly from day one

Architecture

How it's structured

  • 01

    Next.js front end and application routes

  • 02

    PostgreSQL for catalogue, bookings, orders and availability

  • 03

    Firebase Authentication for customer accounts

  • 04

    Razorpay for payments

  • 05

    Deployed on Netlify

Founder journey

  1. One headset

    A rental experiment

  2. Customer validation

    People kept asking again

  3. Expanded inventory

    Quest 2 / 3 / 3S

  4. Corporate rentals

    Events and activations

  5. Multi-device deployments

    Throughput and logistics

  6. Exhibitions & demonstrations

    Product launches, trade floors

  7. Immersive development enquiries

    Can you build the experience?

  8. XR development capability

    Unity, Quest, industrial training

Approach

What I worked on

Operations first

The business ran before the platform did. Early bookings were handled manually, which is what made the eventual data model match reality.

Inventory grew in response to demand: single-headset demos, then corporate rentals, then multi-device deployments for exhibitions.

The platform

Product catalogue, booking flow, authentication, customer dashboard, orders, device availability, reviews and admin workflows.

Availability logic is the core of it — hardware cannot be double-booked and turnaround between events is real.

Where it led

Customers on-site kept asking a different question: can you build the experience, not just supply the headsets.

That pulled the business toward immersive development — industrial training, product demonstrations, guided walkthroughs.

Outcome

What changed

  • An operating VR rental business serving events, exhibitions and corporate activations
  • Direct customer exposure to industrial, training and demonstration use cases
  • A working booking platform built, deployed and maintained solo

Learnings

What I took from it

Running the business changed how I engineer. Customer discovery is faster than speculation, and the constraints that matter usually come from the physical side.