InnHub — Accommodation Management System

Management platform for hotels, hostels, residences, and room-based hospitality businesses.

---

InnHub is an academic/professional MVP focused on accommodation operations, clean architecture, and documentation that can be reviewed as a real product case study.

---

📄 Read this in: English | Español

---

Preview

---

Table of Contents

• What It Does
• Business Workflow
• Key Features
• Stack
• Getting Started
• Architecture
• Documentation
• Project Status
• Author

---

What It Does

InnHub centralizes the operational workflow of accommodation businesses: properties, rooms, guests, reservations, check-ins, housekeeping, maintenance, billing, payments, reports, and dashboard metrics.

It is designed as a configurable COTS-style MVP for room-based hospitality businesses such as hotels, hostels, residences, inns, and similar properties.

Before InnHub: reservations, room status, maintenance, cleaning, and billing can be scattered across spreadsheets, WhatsApp messages, notebooks, and informal processes.

After InnHub: staff can operate from one web application with clear room availability, reservation lifecycle, operational tasks, invoices, and occupancy indicators.

Business Workflow

Guest inquiry → Reservation → Check-in → Stay management
→ Housekeeping / Maintenance → Billing → Check-out → Occupancy reports

Key Features

Dashboard

• Occupancy rate, active reservations, available rooms, and revenue metrics.
• Operational alerts for cleaning, maintenance, check-ins, and check-outs.
• Selective realtime updates for operational visibility.

Reservations

• Reservation creation, cancellation, and lifecycle tracking.
• Date-range availability validation.
• Rule preventing overlapping active reservations for the same room.

Rooms

• Room and room type management.
• Physical room states: available, occupied, cleaning, maintenance, inactive.
• Availability is calculated from reservations, not stored as a physical reserved state.

Guests

• Guest/customer records per property.
• Contact and identification data required for reservations and invoices.

Housekeeping & Maintenance

• Cleaning tasks generated after check-out.
• Maintenance tickets that can block room availability.
• Operational task states for staff follow-up.

Billing & Payments

• Manual invoice generation for completed stays or services.
• Manual payment tracking.
• No external payment gateway in the MVP.

Stack

Category	Technology
Frontend	Vite + React + TypeScript
Styling	Tailwind CSS
Routing	React Router
Forms / Validation	React Hook Form + Zod
Charts	Recharts
Testing	Vitest
Backend / BaaS	InsForge
Database	PostgreSQL
Auth / Realtime	InsForge services
Deployment	Vercel or Netlify + InsForge

Storage is intentionally deferred until a scoped file workflow requires it, such as payment receipts, maintenance attachments, or invoice PDFs.

Getting Started

npm install
cp .env.example .env.local
npm run dev

Backend environment

InnHub uses InsForge as the MVP backend. Fill .env.local with the project values from InsForge settings or the connected backend metadata:

VITE_INSFORGE_BASE_URL=https://your-project.region.insforge.appVITE_INSFORGE_ANON_KEY=your-anon-key

Keep real keys in .env.local or deployment settings only. Issue #4 prepares the environment foundation; database tables and seed data are handled in later backend slices.

Useful checks:

npm run build
npm run lint
npm run test:run

Architecture

InnHub follows a pragmatic frontend architecture combining feature-based organization, lightweight Clean Architecture boundaries, and Atomic Design only for shared UI primitives.

Core rule: UI components should not talk directly to InsForge. Data access and business rules are encapsulated in services, hooks, schemas, and pure functions.

Documentation

Document	Purpose
Product Overview	Product idea, problem, users, and goals
MVP Scope	Included modules, limits, and success criteria
Domain Model	Main entities, relationships, and business rules
Tech Stack	Technologies, reasons, and trade-offs
Architecture	Internal structure, feature boundaries, and data flow
Git Workflow	Branch strategy, issues, PRs, and delivery rules
Functional Specification	Actors, requirements, business rules, and acceptance criteria

Project Status

InnHub is in active development. Core architectural layers, routing, state management, and the backend environment are configured. MVP modules (such as properties, reservations, and rooms) are currently being developed and integrated.

Author

Diego Vargas — Full-Stack Developer

• GitHub: @temps-code