AI-driven channel manager for short-term rental hosts
Don't want to read the manual? Paste this into any AI agent (Claude, ChatGPT, Cursor, etc.):
You are an expert DevOps engineer. Set up the Rental Buddy project from scratch.
1. Clone the repository: git clone <repo-url> && cd adv-ml-project
2. Copy environment variables: cp .env.example .env
3. Start Docker services: docker compose up -d
4. Install dependencies: cd APP && pnpm install
5. Set up the database:
- pnpm db:generate
- pnpm db:migrate
6. Seed local data: pnpm db:seed:local
7. Start development servers: pnpm dev
8. Confirm the web app is running at http://localhost:3000
Report back any errors you encounter.
Rental Buddy is an intelligent channel manager built for short-term rental hosts who list across multiple platforms. It merges Airbnb, Booking.com, VRBO, and Interhome iCal calendars in real time, uses AI to resolve double-bookings and scheduling conflicts, and lets hosts manage their entire portfolio from a single Telegram chat.
No more switching between tabs. No more manual calendar cross-checking. No more accidental double bookings.
- Real-Time Calendar Sync — Merges iCal feeds from Airbnb, Booking.com, VRBO, and Interhome into a unified timeline
- AI Conflict Resolution — Detects overlapping bookings and proposes resolutions automatically
- Telegram Bot Interface — Manage your portfolio, check availability, and receive alerts directly in Telegram
- Smart Scheduling — Visual window picker with overlap highlighting (red conflicts, grey upcoming)
- Printable Reports — Generate clean, host-ready schedule tables for cleaning crews or property managers
- Multi-Property Dashboard — View all your listings in one place with unified analytics
- Guest Form Automation — Auto-generate check-in forms and welcome packs
- AI Shopping Orders — Send "buy 6 cups for Triplex" via Telegram; AI extracts items, matches them to real IKEA products with live pricing, and tracks orders per property
- AI Repair Estimates — Message "repair bathroom door" via Telegram; AI generates a detailed cost breakdown (materials, labor, other) with Portugal-specific pricing
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Next.js │──────▶ tRPC │──────▶ Prisma │
│ Web App │◀─────│ Router │◀─────│ Postgres │
│ :3000 │ └─────────────┘ └─────────────┘
└─────────────┘
│
│ ┌─────────────┐ ┌─────────────┐
└─────────────▶│ Worker │──────▶ BullMQ │
│ (Node) │ │ (Redis) │
└─────────────┘ └─────────────┘
│
▼
┌─────────────┐
│ grammY │
│ Telegram │
└─────────────┘
- Web App: Next.js 15 with App Router serves the UI and tRPC API
- Worker: Background Node process polls iCal feeds and processes Telegram commands via BullMQ queues
- Database: Postgres 16 persists properties, bookings, and calendar events
- Cache/Queue: Redis powers BullMQ job scheduling and real-time state
- AI Layer: OpenAI-compatible client routes to the configured provider for overlap resolution and natural-language commands
| Layer | Technology |
|---|---|
| Frontend | Next.js 15 (App Router), tRPC, Tailwind CSS, shadcn/ui, Framer Motion, Spline 3D |
| Backend | Node.js, tRPC routers, Prisma ORM |
| Worker | Node.js, BullMQ (Redis), grammY (Telegram Bot API) |
| Database | Postgres 16 |
| AI | OpenAI-compatible client (swappable via AI_MODEL env var) |
| Tooling | pnpm workspaces, Turbo, TypeScript |
Prerequisites: Node 20.18+, pnpm 9+, Docker Desktop
# 1. Clone and enter the repo
git clone <repo-url> && cd adv-ml-project
# 2. Copy environment template
cp .env.example .env
# 3. Start Postgres + Redis
docker compose up -d
# 4. Install dependencies
cd APP
pnpm install
# 5. Generate Prisma client and run migrations
pnpm db:generate
pnpm db:migrate
# 6. Seed local data
pnpm db:seed:local
# 7. Start dev servers (web + worker)
pnpm devOpen http://localhost:3000.
The worker auto-reloads on file changes via tsx watch. The web dev server runs on port 3000.
Rental Buddy uses an OpenAI-compatible client for all AI operations — calendar conflict resolution, natural-language Telegram commands, and guest communication drafting.
The provider and model are fully swappable via environment variables. See docs/AI-INTEGRATION.md for configuration details, prompt architecture, and extending the AI pipeline.
- iCal URLs are secrets. They contain HMAC and session tokens that grant read access to your booking calendars. Never log them, never render them client-side, never commit them.
- Telegram bot tokens should be rotated via
@BotFatherbefore production use. - API keys live only in
.env(gitignored by default). Verify.envremains untracked after every clone. - Seed files containing real iCal access tokens are gitignored. Confirm this before committing.
All Rights Reserved.
This code may not be used, copied, modified, or distributed without explicit written permission from the author.
For licensing inquiries, please contact the repository owner.
docs/SETUP.md— Detailed installation and run instructionsdocs/TELEGRAM-BOT-SETUP.md— Creating and configuring your Telegram botdocs/ICAL-OVERLAP-RULES.md— How the merge engine resolves conflictsdocs/AI-INTEGRATION.md— Full AI pipeline: prompts, schemas, fallbacksdocs/GENAI-LOG.md— GenAI usage log and unit economics.agents/knowledge-base/ARCHITECTURE.md— System topology and data flow.agents/knowledge-base/DATA-MODEL.md— Prisma schema intent and entity relationships.agents/knowledge-base/ICAL-MERGE-SPEC.md— Technical specification for the overlap engine.agents/knowledge-base/DESIGN-LANGUAGE.md— Visual design system and UI conventions