Kamra PMS

The open-source, agent-ready hotel PMS.
Bring your own AI — Claude over MCP, or HeyKoala for voice/WhatsApp — on infrastructure you own.

▶ Live demo · Docs · Source · Contact

🏨 Try it now → demo.kamrapms.com

A live sandbox pre-loaded with a sample hotel. Tap any role to sign in — the demo usernames and passwords are listed right on the page. The guest booking engine is at /book and the housekeeping phone app at /kamra/hk.

Why we built this

Most hotel PMS software was built twenty years ago and has barely moved since. Dozens of options, almost no innovation: the same click-heavy screens, the same nightly rituals, the same walls around your own data.

Hotels deserve better than:

• Per-room, per-module rent. Your software bill grows every time your hotel does. Night audit is an add-on. Reports are an add-on. The booking engine is an add-on.
• Your data held hostage. Guest history, rate history, your books — locked in a vendor's cloud, with an export fee if you ever try to leave.
• Waiting for AI that never ships. Legacy vendors bolt a chatbot onto 2005-era software and call it innovation. Real agentic operations need a system designed to be operated by AI, not just chatted at.
• Integration purgatory. Every connection is a paid interface, a certification queue, a quarter of waiting.
• Trained-staff-only software. If a new hire needs a week of training to check someone in, the software failed — not the hire.

Kamra is the answer we wanted to exist: a full property management system where every operation — booking, check-in, folios, night audit, pricing — is a governed action, exposed over a real tool layer, so you can bring the AI you trust to run it.

What makes Kamra different

• Agent-ready, not agent-locked. Kamra ships an MCP server with governed tools, role-scoped and permission-checked like any user. Connect Claude (or any MCP client) and say "book Mr. Rao a deluxe for the weekend with breakfast" — it quotes, books, and every action is logged. No bundled agent personas to trust or configure — bring your own.
• Bring your own key. No bundled AI markup, no model lock-in. Point your own LLM at Kamra's tool surface, or connect HeyKoala for a phone/WhatsApp AI concierge.
• Deterministic money. Prices, taxes, availability come from a pricing engine — never from a language model. GST slabs, multi-rate invoices, and the no-overbooking guard are code, verified by an eval suite in CI.
• Full audit trail. Every action — human or AI — is logged with who did it, what changed, and why. Accountability comes from the ledger, not from hoping the model behaves.
• Truly free. AGPL-licensed. No per-room pricing, no per-user seats, no license audits, no "premium" tiers. Self-host on-prem or on any cloud.
• Built on Frappe. The framework behind ERPNext — one of the world's largest open-source ERPs — with its mature ecosystem: RBAC, audit trails, multi-tenancy, the frappe/payments gateway app, and a huge developer community.

See it

Screens below are from the live demo — open it and click around.

Today — arrivals, departures, in-house with paid/due chips, room board, hours-saved ledger	Reservation 360 — one panel with live billing, inline date amend, guest journey, and the right check-in/out/cancel actions
Tape chart — rooms × dates, booking bars, room moves & stay amendments	Reports — occupancy/ADR/RevPAR, MTD, collections, 14-day trend, printable flash
New booking — returning-guest typeahead, live quote, sell message, multi-room, add-ons, cancellation policy in plain words	Guest profile — the stay strip, lifetime stats, upcoming stays, merge & anonymize
Folio & GST invoice — per-line GST, splits/transfers, payment links, multi-rate breakup	Booking Engine console — manage your direct-booking page: hotel profile, photo gallery, policies, FAQ, map & directions, and SEO
Restaurant POS — area-wise table map with live states (running / in kitchen / reserved / cleaning), concurrent bills, thermal KOT & bill printing, F-key shortcuts	Dashboard — occupancy, movement, revenue and collections with department slices, chain-wide roll-up

The direct booking page your guests see — photo gallery, live per-date rates, hotel policies, an FAQ, map & directions, and pay-at-hotel — commission-free, and yours to brand.

What's inside (today)

Documentation

kamrapms.com/docs is the full manual —
quickstart, per-provider self-hosting guides, features tour, user guide,
AI/MCP setup and FAQ.

REST API

Kamra exposes 148 REST endpoints — the same governed layer the UI and
the AI use:

• REST API reference —
  every endpoint with method, required roles, parameters and description,
  generated from the source so it never drifts
• Postman collection
  — import it, set base_url (your Kamra URL), api_key and api_secret
  collection variables, and every request is ready to try
• MCP tool reference — the 32 tools
  AI agents get

# the calling convention
curl -X POST https://<your-kamra>/api/method/kamra.api.get_quote \
  -H "Authorization: token <api_key>:<api_secret>" \
  -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 markdown lives in docs/:
user guide · AI & API setup ·
self-hosting · email setup ·
developer notes · brand assets

Install

bench get-app payments
bench get-app kamra https://github.com/Kamra-PMS/kamra-pms --branch main
bench --site your-site install-app kamra

Kamra ships its built front-end, so after install the product UI is live at
/kamra (the booking engine redirects in at /book, housekeeping at
/hk) — no Node server in production. The Frappe Desk stays available at
/app as an admin escape hatch. A fresh install creates its own roles and
permissions; sign in as your Administrator and open /kamra/setup to create
your property, then add staff users.

Compatibility & channels

develop is the repo's default branch (for contributors), so production
installs should keep the explicit --branch main. Releases follow
SemVer; see RELEASING.md.

Quickstart (development)

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 production UI after front-end changes with npm run build at the
app root (emits into kamra/public/frontend, served at /kamra). Seed a demo
property, roles and users via bench --site … execute kamra.scripts.seed_demo.execute
(this also enables the demo-account buttons on the login screen). Full dev
notes: docs-dev.md.

Connect an AI agent:

claude mcp add kamra -e KAMRA_URL=... -e KAMRA_API_KEY=... \
  -e KAMRA_API_SECRET=... -- python mcp/kamra_mcp.py

For hotel owners

You own the software, the server, and every byte of your data. Costs don't scale with your room count. Connect your own AI and it works from day one — and if you ever want managed hosting or an AI concierge (voice, WhatsApp) on top, those are choices, not ransoms.

For IT teams

Standard Python (Frappe) + React. Real RBAC, real audit trails, documented REST + MCP surfaces, an eval suite in CI, no black boxes. Fork it, extend it, ship your own modules — that's the point.

License

AGPL-3.0 — free forever. Anyone offering Kamra as a hosted service must share their modifications back, which keeps the ecosystem honest.

Contributors

Kamra is built in the open — PRs welcome. Thanks to
@Mohammed-Muneef (guest laundry
self-service, the desk laundry console, house & complimentary orders).

Links & contact

• Live demo: demo.kamrapms.com — credentials are on the page
• Documentation: docs/
• Source & issues: github.com/Kamra-PMS/kamra-pms
• Email: [email protected]

Built by HeyKoala.

Kamra means "room". The door in our logo is open on purpose.