Why open source

Don't take a vendor's word for it. Check it.

Your PMS holds your guests' details, your money and your daily operations. With closed software, you trust what you are told. With Kamra, you or anyone you hire can read the code, see the fixes and leave with your data.

Promise or proof

The difference is what you can verify

Many closed PMS vendors are honest and do good work. The question is what you can confirm for yourself when it matters.

 Closed softwareOpen source (Kamra)
How rates and taxes are worked outYou compare the bill with the vendor's explanation.The calculation is in public code that your accountant or developer can read.
How guest data is handledYou rely on the vendor's policy and contract.You choose the server and the country, and can read what the software does with the data.
How security problems are handledYou find out what the vendor chooses to tell you.Fixes are visible in the code, and published advisories stay on the record.
What the AI is allowed to doYou take the vendor's description of it.The permission checks and the masking of guest details are in the code.
If prices rise, or the company is soldYou negotiate, or start a migration under pressure.The licence lets you keep running the software, with any developer you choose.
For your role

The question you are really asking

Owner or general manager

What happens if this company is sold, raises its prices or disappears?

The code stays available whatever happens to us. Your hotel keeps running, and another developer can take over. Apache-2.0 lets you use and change it. Our promise of no per-room pricing is written down in public.

Read the Open Pledge →
Finance head or accountant

Can I explain every number on this bill to an auditor?

Rate and tax rules sit in readable code, not a black box. The AI never sets a price or a tax: those always come from the pricing engine, and actions are logged.

Read the pricing code →
IT lead

Can we review this, run it and connect it without asking anyone's permission?

Review the code before you install it. Run it on your own server or cloud, keep your own backups, and use the REST API, webhooks and MCP tools with no interface fee.

Read the access checks →
Data protection lead

Where does guest data live, and who can see it?

You decide where the database sits. Staff can be limited by role and by property. Guest contact and ID fields are masked before tool results reach an outside AI provider, or you can run a local model.

Read the masking code →
Head of a hotel group

Can we standardise on one system without being tied to one vendor's roadmap?

Your cost does not rise with each property. A change made once can serve the whole group, and your own team, a local partner or any Frappe developer can make it.

See Enterprise and partners →
No sales call needed

Check it yourself, today

Every line here links to the evidence. Send this page to whoever signs off on software at your hotel.

People outside our team have reported real security problems in Kamra. We fixed them, credited the people who found them and published the advisories. That record is public, including the parts that are not flattering.

Straight answer

What open source does not do for you

  • Open does not mean audited. The code can be checked, but that does not mean anyone has checked the part you care about. Kamra makes no SOC 2 or ISO 27001 claim today. If your policy needs one, ask us before you commit.
  • If you host it, you keep it safe. Updates, backups and access are your job, or the job of whoever you pay. Security fixes go to the latest stable release only, so you need to stay current.
  • Kamra is young. Version 1.0 shipped on 5 July 2026. Try it with your own room types and tax rules before you move a live hotel.
  • Free software still needs people. Budget for a server, and for setup or support if you do not have your own team. See what you pay for.

Kamra is built by HeyKoala (Koala AI Solutions Private Limited, Bangalore, India). See what is free and what is not.

Questions

What buyers ask about open source

Is open-source hotel software safe?

It can be, but being open does not make it safe by itself. Open code can be checked, by you or by someone you hire, and fixes are visible. You still need to keep it updated, control who has access and keep backups, or pay someone to do that.

If anyone can read the code, can attackers read it too?

Yes. That is why Kamra should not depend on hidden code for its security. Your data, passwords and keys are not in the code. They stay on your server. What matters is whether problems are found, fixed and installed quickly.

What happens to my hotel if the company behind Kamra stops?

Your installation keeps running. The code is licensed Apache-2.0, so you or another developer can continue to run, maintain and change it. Your data stays in your own database.

Do I have to publish my hotel's data or changes?

Your data, guest records and settings are never covered by the licence. Apache-2.0 lets you change Kamra and keep those changes private, including when you host them. You keep the attribution and patent terms that come with the licence.

Who do I call when something goes wrong?

Community help is free and has no guaranteed response time. For someone accountable, take an annual support contract from the team that builds Kamra, or work with a partner.

Talk to us

Send us the questions your team needs answered

Owner, finance or IT: tell us your rooms and what must be true before you switch. We will answer in writing, within one working day. [email protected]

No spam, no drip campaigns. A person replies.

Ask an AI about Kamra

Open your assistant with the question already typed. It answers from our public pages, not our marketing copy.

Open source on GitHub

If Kamra is useful, star the repository. Stars are how hotels and partners find software they can own, inspect and keep running. Community stays complete and free; Kamra Cloud is optional.

Star on GitHub 111