Vanrays
HUB
Operations platform for Vanrays’ property management business in Madrid. Bookings, cleaning, maintenance, and owner settlements in one place, replacing a pile of spreadsheets, forms, and AppSheet automations.
Vanrays is a property management company in Madrid with a growing portfolio of short and long-term rentals. Day-to-day operations ran on AppSheet, a no-code tool that worked fine at first but started showing its limits: reservations, cleaning schedules, maintenance tickets, and owner payouts ended up scattered across spreadsheets, forms, and email threads.
Vanrays HUB replaces all of that with a real application built around how the team actually works: admins and bookers run day-to-day operations from a central console, while owners, cleaners, and maintenance techs each get a portal scoped to their role.
Updated by hand, 3–4 hours a week.
Live in the app, updated as it happens.
A full day at month-end, done by hand.
Generated automatically, in minutes, an hour at most.
Reservations
Create, edit, and cancel bookings. Log payments by transfer, card, or cash, and track every status from tentative to checked out, cancelled, or no-show.
Properties & owners
Full catalog with tourist and corporate pricing, commissions, and security deposits. Properties link to one or more owners by ownership share.
Cleaning
Schedule and assign cleanings by type (checkout, check-in, midstay, deep clean, extra, owner) with live status tracking.
Maintenance
Ticket system with priority levels and a full workflow from reported to closed, including materials used and their cost.
Settlements
Monthly owner settlements generated automatically, broken down per booking by gross income, commission, and net. Draft, issued, paid.
Team & audit
Manage admins, bookers, cleaners, and technicians. Admins and bookers work from the main console; owners, cleaners, and techs get scoped portal access. Full audit trail of every action.
Owners, cleaners, and maintenance techs each get a login scoped to exactly what they need to see, no access to the main console. Admins and bookers work from the console directly, with full visibility across reservations, cleaning, maintenance, and settlements.
Owner
/portal/ownerTheir properties and active bookings, an occupancy calendar, and monthly settlements they can view and download.
Cleaner
/portal/cleanerAssigned jobs sorted by date. Mark a job as started or completed, flag an issue, and upload before/after photos.
Maintenance
/portal/maintAssigned tickets by priority, status updates, materials used, and photos of the problem and the fix.
Built so QA never has to worry about breaking anything real.
Isolated PR previews
Every pull request deploys to its own preview environment on Railway, each with its own isolated Postgres database seeded independently of production. QA runs against real flows, bookings, cleanings, settlements, without ever touching live data.
Auth & access control
Supabase Auth handles login and session management across the ops console and every portal. Role checks run server-side on top of it, so an owner, cleaner, or tech only ever sees data scoped to them.
PDF exports for owner settlements, splitting bookings into tourist vs. corporate with their own commissions, a consolidated owner profile view, and automated booking emails.