Kamra Pms
Open-source hotel & short-term rental PMS - front desk, booking engine, folios & GST/tax billing, housekeeping, POS, WhatsApp. Agent-ready via MCP (Claude). Built on Frappe. AGPL-3.0.
- Author: Kamra-PMS
- Repository: https://github.com/Kamra-PMS/kamra-pms
- GitHub stars: 38
- Forks: 19
- License: AGPL-3.0
- Category: Localization
- Maintenance: Actively Maintained
- Frappe versions: develop
Install Kamra Pms
bench get-app https://github.com/Kamra-PMS/kamra-pms
Tags
- agpl
- ai-agents
- booking-engine
- channel-manager
- erpnext
- frappe
- gst
- hospitality
- hotel-management
- hotel-pms
- india-gst
- mcp
- night-audit
- pms
- property-management
Add the Frappe Gems badge to your README
Maintain Kamra Pms? Paste this into your README:
[](https://frappegems.com/gems/apps/Kamra-PMS/kamra-pms)
About Kamra Pms
Kamra PMS
Open-source hotel & short-term rental PMS — front desk, booking engine,
folios & tax billing, housekeeping, POS, and an MCP tool layer so AI agents can run the property.
▶ Live demo · Docs · Install · AI / MCP · Contact
> **Try it in 30 seconds → [demo.kamrapms.com](https://demo.kamrapms.com)** > Tap any role to sign in (credentials are on the page). Guest booking: [/book](https://demo.kamrapms.com/book) · Housekeeping app: [/kamra/hk](https://demo.kamrapms.com/kamra/hk) **Kamra** is a full **property management system (PMS)** for hotels, resorts, and **short-term rentals / villas**. It runs on **Frappe** (the framework behind ERPNext), is **AGPL-3.0**, and is built so humans *and* AI agents share the same governed APIs — booking, check-in, folios, night audit, pricing — with deterministic money (never from an LLM). --- ## Contents - [What's new](#whats-new) - [Why Kamra](#why-kamra) - [What makes it different](#what-makes-it-different) - [Screenshots](#screenshots) - [Short-term rentals](#short-term-rentals) - [Features](#features) - [Documentation & API](#documentation--api) - [Install](#install) - [Quickstart (development)](#quickstart-development) - [Who it's for](#who-its-for) - [License & contributors](#license--contributors) --- ## What's new On **`develop`** (nightly) the product is the **2.6.2** train plus Unreleased work. The `v2.6.2` GitHub tag is still pending — latest published release is [v2.6.0](https://github.com/Kamra-PMS/kamra-pms/releases/tag/v2.6.0). - **Unreleased** — System Health, property time zone, **85 MCP tools** (role + module gated), AI provider presets, WordPress-easy `deploy/install.sh`, banquet Phase 1 (send quote, guest response, Sales/Finance/HK/F&B checklists) - **2.6.2** (in the changelog; not tagged yet) — Opera-style cashier till, folio ledger, cashier PIN, POS full-screen till Notes live in [`CHANGELOG.md`](CHANGELOG.md) — this list is a pointer, not a second release note. How we cut stables: [`RELEASING.md`](RELEASING.md). --- ## Why Kamra Most hotel PMS software was built twenty years ago: per-room SaaS rent, locked-in data, bolt-on chatbots, and screens that need a week of training. Kamra is the alternative we wanted: | Pain with legacy PMS | With Kamra | |---|---| | Per-room / per-module pricing | **Free forever** (AGPL) — cost doesn't scale with rooms | | Data lock-in | **You host it** — on-prem, VPS, or Frappe Cloud | | AI as a marketing slide | **MCP tools** — Claude (or any agent) books and audits with RBAC | | Opaque pricing & tax | **Deterministic engine** — GST / SST / VAT packs in code + CI evals | | New-hire training hell | Front desk UI a clerk can learn the same day | --- ## What makes it different - **Agent-ready, not agent-locked.** [MCP server](https://kamrapms.com/docs/ai-and-mcp) with **85** governed tools — role-scoped, module-gated, permission-checked, fully logged. Connect Claude; no bundled agent to trust. - **Bring your own key.** No AI markup or model lock-in. Optional [HeyKoala](https://heykoala.ai) for voice / WhatsApp concierge. - **Deterministic money.** Rates, tax slabs, availability, and no-overbooking guards come from code — never from a language model. - **Full audit trail.** Every human or AI action: who, what, why. - **Built on Frappe.** RBAC, multi-tenancy, Desk escape hatch, [frappe/payments](https://github.com/frappe/payments) gateways, ERPNext-adjacent ecosystem. --- ## Screenshots *From the [live demo](https://demo.kamrapms.com) — open it and click around.* | | | |---|---| |  |  | | **Today** — arrivals, departures, in-house, paid/due chips, room board | **Reservation 360** — billing, amend dates, check-in / out / cancel | |  |  | | **Tape chart** — rooms × dates, moves & stay amendments | **Reports** — occupancy, ADR, RevPAR, flash | |  |  | | **New booking** — live quote, multi-room, add-ons, cancellation policy | **Guest profile** — stay strip, merge & anonymize (DPDP) | |  |  | | **Folio & tax invoice** — per-line GST, splits, payment links | **Booking engine console** — gallery, policies, FAQ, SEO | |  |  | | **Restaurant POS** — table map, KOT / bill print, F-keys | **Dashboard** — occupancy, revenue, chain roll-up | |  |  | | **Laundry** — pickup → return → folio; guest self-service | **Self check-in** — ID capture, e-sign, retention policy | **Guest-facing booking page** — date range, **Check availability**, rates, gallery, policies, pay-at-hotel: [](https://demo.kamrapms.com/book) --- ## Short-term rentals Same PMS for **villas and multi-site STR portfolios**: sellable units (room / whole-place / package), competition groups, cleaning fees & deposits, Instant or Request-to-book, and a catalog that feels like a listing site. | | | |---|---| |  |  | | **Catalog** — check-in / out + Check availability | **Places to stay** — per-villa cards & from-rates | [](https://demo.kamrapms.com/book) Live example: [demo.kamrapms.com/book](https://demo.kamrapms.com/book). --- ## Features | Area | What you get | |---|---| | **Front desk** | Today board, check-in flow (GRC readiness + room suggestion), tape chart, ETA/ETD, guest profiles, blacklist | | **Booking engine** | Direct booking + SEO console; hotels = room grid; STRs = villa catalog | | **Short-term rentals** | Hotel vs STR property kind, sellable units, per-villa locations, Instant / Request-to-book | | **Booking** | Multi-room / group / corporate, returning guests, add-ons, vouchers, travel agents, day-use | | **Revenue** | Seasons, rate plans, guardrails, hurdle rates, overbooking allowance, cancellation & no-show policy in code | | **Billing** | Folios, corporate routing, group masters, charge splits, night audit, tax invoices, GSTR-1, payment links, cashier till (FO+POS cash, PIN pad), folio ledger | | **F&B** | POS table map, full-screen till and kitchen pass, split bills, thermal KOT, kitchen display, inventory & recipes, QR ordering, room posting | | **Operations** | Tickets + SLA, housekeeping `/hk`, guest laundry end-to-end, lost & found, banquet / events (send quote, guest response, dept checklists) | | **Guests** | Online pre-check-in, GRC + occupant register, **editable nationality**, ID retention modes | | **Messaging** | WhatsApp (Meta Cloud API) — confirmations, check-in links, inbox, desk tickets | | **Localization** | India GST, Indonesia PB1, Thailand VAT, Malaysia SST, UAE VAT — currency & locales follow the pack | | **Platform** | Multi-property RBAC, dark mode, property time zone, System Health, AI provider presets, CSV migration (eZee / Cloudbeds presets), eval harness in CI | --- ## Documentation & API Full manual: **[kamrapms.com/docs](https://kamrapms.com/docs/)** — quickstart, self-hosting, features, user guide, AI/MCP, FAQ. Going live? Use the **[go-live checklist](https://kamrapms.com/docs/go-live)**. ### REST & agents Kamra exposes **170+ REST endpoints** — the same governed layer the UI and AI use: - [REST API reference](https://kamrapms.com/docs/api-reference) - [Postman collection](https://kamrapms.com/docs/kamra.postman_collection.json) - [MCP tool reference](https://kamrapms.com/docs/mcp-tools) ```bash curl -X POST https:///api/method/kamra.api.get_quote \ -H "Authorization: token :" \ -H "Content-Type: application/json" \ -d '{"property":"Your Property","room_type":"Your Property-DLX", "check_in_date":"2026-08-01","check_out_date":"2026-08-03"}' ``` In-repo: [`docs/`](docs/) · [user guide](docs/user-guide.md) · [AI & API](docs/ai-and-api.md) · [self-hosting](docs/self-hosting.md) · [dev notes](docs-dev.md) · [branding](branding/README.md) --- ## Install **Hotels (WordPress-easy):** ```bash curl -fsSL https://raw.githubusercontent.com/Kamra-PMS/kamra-pms/main/deploy/install.sh | bash ``` Three prompts: site domain, admin email, admin password. Pulls `ghcr.io/kamra-pms/kamra:latest`. Then open `/kamra/setup`. Details: [deploy/](deploy/) · [docs quickstart](https://kamrapms.com/docs/quickstart). **Bench / Frappe Cloud:** ```bash bench get-app payments bench get-app kamra https://github.com/Kamra-PMS/kamra-pms --branch main bench --site your-site install-app kamra ``` After install: product UI at **`/kamra`**, booking at **`/book`**, housekeeping at **`/hk`**. Desk remains at `/app`. Sign in as **Administrator**, open `/kamra/setup`, create your property, add staff. | Channel | Branch / tag | Use for | |---|---|---| | **Stable** | `main` / `vX.Y.Z` | Production, [Frappe Cloud Marketplace](https://cloud.frappe.io/marketplace/apps/kamra), [demo](https://demo.kamrapms.com), `ghcr.io/kamra-pms/kamra:latest` | | **Nightly** | `develop` | Previews, `ghcr.io/kamra-pms/kamra:nightly` | Production installs should use `--branch main` (`develop` is the default GitHub branch for contributors). Releases are SemVer with a **patch-first** cadence — see [`RELEASING.md`](RELEASING.md) and [`CHANGELOG.md`](CHANGELOG.md). --- ## Quickstart (development) ```bash bench init --frappe-branch v16.25.0 frappe-bench && cd frappe-bench bench get-app payments bench get-app kamra https://github.com/Kamra-PMS/kamra-pms bench new-site kamra.localhost --admin-password admin bench --site kamra.localhost install-app kamra bench serve --port 8000 cd apps/kamra/frontend && npm install && npm run dev # hot-reload UI on :5173 ``` Rebuild the SPA with `npm run build` at the app root (emits `kamra/public/frontend`). Seed demo data: `bench --site … execute kamra.scripts.seed_demo.executRelated Localization apps for Frappe & ERPNext
- Wiki — Free and Open Source Wiki built on top of Frappe
- India Compliance — Simple, yet powerful compliance solutions for Indian businesses
- Nepal Compliance — Open source ERP for Nepal with HR, Payroll & Accounting compliance, based on ERPNext by Frappe Technologies.
- Erpnextswiss — ERPNext application for Switzerland-specific use cases
- Erpnext Germany — ERPNext customizations for German companies
- Ksa Compliance — KSA Compliance App for KSA E-invoice
- Zatca Erpgulf — Implementation of Zatca Phase-2 E-Invoicing - for FrappeCLoud
- Kenya Compliance — KRA eTIMS Tax Compliance Integration This app works to integrate ERPNext with KRA's eTIMS via the Online Sales Control Unit (OSCU) to allow for the sharing of information with the revenue authority.via OSCU with ERPNext