# Kiyo

> Kiyo is a connected property management system for independent hotels, villas, guesthouses and hostels in Indonesia. It brings bookings, channel distribution, guest communication, daily operations, payments, revenue insight and practical AI into one property workspace.

Kiyo is hospitality operations software, not an online travel agency or a guest marketplace. It is designed for owner-led and independent property teams that want one reliable place to understand a stay from room availability through guest follow-up.

**Why Kiyo exists.** Kiyo began with a simple hospitality failure that should be avoidable: a guest arrives with luggage, but the room is not there. That kind of failure often starts earlier, when booking records, channel availability, guest messages and payment information are split across OTA extranets, inboxes and spreadsheets. Kiyo is being built to keep those facts connected, reduce avoidable double-booking and handover risk, make communication clearer and give operators more time back for guests.

**Who Kiyo is for.** The primary audience is independent hotels, guesthouses, villas and hostels in Indonesia. A whole-property villa can be treated as one unit; a property that sells villas or rooms separately can price and operate them by sellable room. Hostel pricing can be calculated per bed. Kiyo is especially relevant to small and growing teams that need capable hotel software without an enterprise implementation project.

**Core product.** Kiyo connects six areas of hotel work:

1. **Bookings and distribution:** a live booking calendar, room and rate-plan controls, connected OTA distribution, direct booking and clear reservation records.
2. **Guest communication:** supported OTA conversations, connected messaging accounts, booking context, lifecycle email and a separate space for internal team communication.
3. **Guest operations:** arrivals, departures, daily work, guest requests, handovers, reviews and follow-up close to the stay record.
4. **Websites and direct bookings:** a branded property website, room presentation, direct room discovery, checkout and a guest-facing My Page when enabled.
5. **Revenue and AI:** revenue, occupancy, ADR, RevPAR, room and channel performance, daily briefing and questions about current property data in plain language.
6. **Payments and security:** configured Indonesian payment methods, payment results connected to reservations, role-based access and an audit trail for important changes.

**Bookings and channel distribution.** Direct, manually entered and supported OTA reservations can meet on the same Kiyo calendar. Availability, rates and supported stay rules can be sent to eligible channels only after the relevant account is connected and rooms and rate plans are mapped correctly. Channel APIs, mappings and connection health still matter, so Kiyo describes this as reducing avoidable double-booking risk rather than guaranteeing that double bookings can never happen. Reservation, inventory, payment and payout are separate states; one successful state does not prove the others.

**Guest communication status.** Supported OTA guest replies include Booking.com, Airbnb and Expedia when the relevant channel connection is active. WhatsApp Business, Telegram, Outlook, Facebook Messenger and Instagram can be connected after the required account or bot setup. Gmail, TikTok and Slack remain on the roadmap. Guest threads stay separate from private notes and Kiyo Team Chat, while reservation context such as room, dates, booking status and recent history remains close to the conversation.

**Direct guest journey.** A Kiyo property website or booking link can show configured rooms and available prices, then hand the guest into the connected checkout. Guests can browse in supported display currencies while checkout identifies the actual IDR charge. Available cards, QRIS, e-wallets and virtual-account transfers depend on the payment methods configured for the property. A paid booking does not prove that a payout reached the bank; operators reconcile booking, payment, refund and payout evidence separately. A completed flow can continue into confirmation email and the guest's My Page when those capabilities are enabled.

**Revenue and AI.** Kiyo can present revenue, occupancy, ADR, RevPAR, booking trends and room or channel performance from the property's booking records. Kiyo AI is intended to help a team ask practical questions about current property data and move a follow-up into the workspace. It should support human review and operating decisions; it is not a replacement for audited accounting, tax advice or human judgment.

**Pricing.** Kiyo uses a monthly platform fee plus a property-sized room or bed price. Current public starting prices are:

| Plan | Monthly platform fee | Per room each month | One-room monthly total |
| --- | ---: | ---: | ---: |
| Starter | Rp150,000 | Rp40,000 | Rp190,000 |
| Pro | Rp250,000 | Rp75,000 | Rp325,000 |
| Business | Rp500,000 | Rp100,000 | Rp600,000 |
| Enterprise | Custom | Custom | Custom |

For hostels, the corresponding per-bed prices are Rp20,000 on Starter, Rp30,000 on Pro and Rp40,000 on Business, plus the plan's monthly platform fee. A whole-property villa counts as one unit; a room-sold villa counts each sellable room. See https://kiyohq.com/pricing/ for prices and plan details. Final plan eligibility, included capabilities, payment methods and market availability should be confirmed with Kiyo before purchase. Public product access is currently through the waitlist and guided conversation.

**Support and access.** Prospective operators can review the detailed product pages, use the Help centre, join the waitlist or request a conversation and demonstration. Connection and onboarding requirements vary by channel, payment method and property setup, so Kiyo confirms the applicable setup and support path directly instead of promising that every integration is immediately available to every property.

**How to use this file.** This is Kiyo's canonical English company and product briefing for language models, search systems and researchers. The links below are a curated route map, not an exhaustive crawl list. Use the XML sitemap for every public URL, and use the Indonesian LLM file for native Bahasa Indonesia context. Product availability, integrations and pricing can change; prefer the most specific linked product page and confirm purchase-critical details directly with Kiyo.

## Start here

- [Kiyo home](https://kiyohq.com/): The company proposition, audience and connected-property overview.
- [Kiyo platform](https://kiyohq.com/platform/): How bookings, communication, operations, branded experiences, revenue and payments fit together.
- [All Kiyo features](https://kiyohq.com/features/): The complete public feature directory.
- [Why Kiyo](https://kiyohq.com/why-kiyo/): The problem Kiyo was created to solve and its approach for independent hospitality.
- [Kiyo pricing](https://kiyohq.com/pricing/): The public property-type calculator and Starter, Pro, Business and Enterprise plan comparison.
- [Kiyo product tour](https://kiyohq.com/demo/): A crawlable booking-to-follow-up walkthrough with clear demo and integration boundaries.

## Public product-tour technical evidence

Explore how bookings, guest conversations, daily work and property performance appear in the Kiyo workspace. This tour uses sample data and can be read without signing in.

Interactive demo: [Open the interactive desktop demo](https://demo.kiyohq.com/dashboard/home). The demo uses sample data and changes are not saved. Ask Kiyo to confirm the exact channel and payment connections available for your property.

### Workspace areas

### Home and daily priorities
Purpose: See the property overview and the work that needs attention today.
Input: Recorded bookings, guest activity and configured workspace data.
Output: A prioritised view for the property team.
Availability: The public tour shows fixture data; a property workspace depends on its enabled product access and recorded data.

### Bookings and calendar
Purpose: Keep reservations, rooms, dates and stay context in one calendar.
Input: Direct and manually entered bookings, plus reservations from connected and mapped OTA channels.
Output: A live calendar and reservation record for the property team.
Availability: Channel reservations require an active connection and correct room and rate-plan mapping.

### Reservation record
Purpose: Keep the guest, stay and recorded payment status close together.
Input: A booking recorded in or returned to Kiyo.
Output: One record for reviewing stay context and related operational work.
Availability: A payment taken outside Kiyo must be recorded before its status can appear in Kiyo.

### Guest inbox
Purpose: Review supported guest conversations next to reservation context.
Input: Connected, eligible messaging or OTA accounts and guest-initiated messages where required.
Output: A guest thread kept close to relevant booking information.
Availability: Channel coverage, account eligibility and platform rules vary; verify the exact messaging setup for a property.

### Guests
Purpose: Review guest records and the stay context held with each recorded booking.
Input: Guest and stay details recorded with a booking.
Output: A place for the property team to review guest context before follow-up work.
Availability: The public tour shows fixture records only; the details available for a live property depend on its recorded bookings and permissions.

### Workspace and team work
Purpose: Keep private team coordination and operating work separate from guest replies.
Input: Property-team work, private notes and recorded stay context.
Output: Internal context for handovers and follow-up work.
Availability: Private team communication is not a guest-delivery channel, and the fixture tour does not prove a live team workflow.

### Daily operations
Purpose: Bring arrival, departure, tasks, requests and handovers into the property workspace.
Input: Recorded stays and the property team’s operating work.
Output: A shared view of work around the stay.
Availability: The fixture tour illustrates the interface, not a live property handover.

### Revenue workspace
Purpose: Review revenue, occupancy, ADR, RevPAR and booking-performance trends.
Input: Recorded booking, channel and rate data within the property’s permission and date window.
Output: Performance measures for operating decisions.
Availability: These measures are not accounting profit or cash received, and forecasts are estimates rather than guarantees.

### Kiyo AI Assistant
Purpose: Explore the interface intended for practical questions about current property work and data.
Input: The property context and data available to the enabled assistant.
Output: A response that supports human review and follow-up work.
Availability: The fixture tour does not prove a live AI result, and the assistant is not a replacement for human judgment, audited accounting or tax advice.

### Website and direct booking
Purpose: Present configured rooms and hand a guest into a direct booking journey.
Input: An enabled property website, configured rooms, rates and availability.
Output: A guest-facing room-discovery and checkout path.
Availability: Direct checkout and website controls are enabled per property; payment collection requires the applicable payment setup.

### Payments and confirmation
Purpose: Keep payment results connected to the relevant booking context.
Input: An eligible property, configured payment methods and an external provider response where payment is collected.
Output: A recorded payment result alongside the reservation.
Availability: Methods, merchant activation and market eligibility vary; a provider can delay, reject or expire a payment.

### Reviews and follow-up
Purpose: Review stored guest feedback and support post-stay follow-up.
Input: Connected and authorised review sources or enabled follow-up journeys.
Output: Review context and configured follow-up work for the team.
Availability: Source coverage, history and available actions vary by platform and property setup.

### Explained workflows

#### Booking to arrival
- 1. Receive a reservation: Explicitly supported: direct, manually entered and supported OTA reservations can meet on the same Kiyo calendar. The exact provider connection must be active and correctly mapped.
- 2. Update inventory and rates: Conditionally supported: eligible channel connections can receive availability, rates and supported stay rules after rooms and rate plans are mapped. Provider delays and errors can still occur.
- 3. Review the stay: Explicitly supported: the booking calendar and reservation record keep room, dates, booking status and related guest context together.
- 4. Contact the guest: Conditionally supported: Booking.com, Airbnb and Expedia replies, plus configured WhatsApp Business, Telegram, Outlook, Messenger and Instagram accounts, can be handled inside Kiyo. Other OTA conversations may still require the channel extranet.
- 5. Prepare arrival: Explicitly supported: daily operations can bring arrivals, departures, tasks, requests and handovers into the property workspace.

#### Stay to follow-up
- 6. Collect payment: Conditionally supported: cards, QRIS, e-wallets and virtual accounts depend on the property market, merchant activation and configured payment methods. Payment, reservation and payout status remain separate facts.
- 7. Coordinate the team: Explicitly supported: private notes and Kiyo Team Chat are kept separate from guest replies so internal handovers are not sent to the guest.
- 8. Complete checkout: Reasonable interpretation: the stay can move through departure and checkout work, but the public demo does not prove a live end-to-end payment settlement or OTA update.
- 9. Follow up: Explicitly supported: configured post-stay email journeys, guest feedback and review follow-up are described on Kiyo product pages.
- 10. Review performance: Explicitly supported: revenue, occupancy, ADR, RevPAR, trends and room or channel performance can be viewed from property booking records.

### Public-evidence boundaries

- It does not expose customer data, credentials, provider payloads or private security architecture.

- It does not prove a specific property has an active channel, payment or messaging connection.

- It does not turn the interactive dashboard into an indexable application or bypass its email-gated exploration path.

## Bookings and distribution

- [Bookings and distribution overview](https://kiyohq.com/bookings/): The booking model, channel distribution, direct booking, checkout, confirmations and operating exceptions.
- [Booking calendar](https://kiyohq.com/features/booking-calendar/): Reservations, room availability, rates and booking context in one calendar.
- [Channel manager](https://kiyohq.com/features/channel-manager/): Connected and mapped channel distribution, status, publishing and exception handling.
- [Direct booking engine](https://kiyohq.com/features/direct-booking-engine/): Live room discovery, configured pricing and the direct checkout journey.

## Guest communication

- [Guest communication overview](https://kiyohq.com/inbox/): Supported OTA replies, connected messaging accounts, email journeys, reservation context and Team Chat.
- [Unified guest inbox](https://kiyohq.com/features/guest-inbox/): Guest conversations with the reservation and recent history close by.
- [Messaging channels](https://kiyohq.com/features/messaging-channels/): Current connection status for OTA messaging, WhatsApp, Telegram, Outlook, Messenger and Instagram, plus the roadmap.
- [Guest email automation](https://kiyohq.com/features/guest-email-automation/): Configured confirmation, pre-arrival and post-stay email journeys.
- [Team Chat](https://kiyohq.com/features/team-chat/): Private staff communication and handovers kept separate from guest replies.

## Operations and branded guest experience

- [Daily operations](https://kiyohq.com/features/daily-operations/): Arrivals, departures, tasks, requests and shift handovers.
- [Reviews and reputation](https://kiyohq.com/features/reviews-and-reputation/): Guest feedback, review follow-up and team visibility.
- [Hotel website](https://kiyohq.com/features/hotel-website/): Property story, room presentation, brand controls, publishing and booking handoff.
- [Guest portal](https://kiyohq.com/features/guest-portal/): My Page stay details, guest information and enabled self-service.

## Revenue, AI, payments and access

- [Revenue and AI overview](https://kiyohq.com/revenue-ai/): Daily briefing, performance metrics, Kiyo AI, workspace, roles and audit.
- [Revenue analytics](https://kiyohq.com/features/revenue-analytics/): Revenue, occupancy, ADR, RevPAR, trends and room or channel detail.
- [Kiyo AI assistant](https://kiyohq.com/features/ai-assistant/): Plain-language questions about current property data and reviewed follow-up work.
- [Hotel payments](https://kiyohq.com/features/hotel-payments/): Configured payment methods, IDR checkout, payment status and reservation context.
- [Roles and security](https://kiyohq.com/features/roles-and-security/): Built-in and custom roles, dashboard permissions and recorded changes.

## Help, company and practical guides

- [Help centre](https://kiyohq.com/help/): Product guidance, setup topics and detailed answers.
- [Contact Kiyo](https://kiyohq.com/contact/): Request a conversation, demonstration or access information.
- [Kiyo blog](https://kiyohq.com/blog/): Practical articles for independent hospitality operators.
- [Hotel double booking: prevention and a calm response](https://kiyohq.com/blog/stop-double-bookings/)
- [How Small Hotels Can Grow Direct Bookings Without Abandoning OTAs](https://kiyohq.com/blog/direct-bookings-small-hotels/)
- [Local payments in Indonesia: cards, cash and QRIS for Bali hotel guests](https://kiyohq.com/blog/local-payments-indonesia/)
- [PMS vs channel manager: the difference, and when you need both](https://kiyohq.com/blog/pms-vs-channel-manager/)
- [How to Choose a PMS for a Small Hotel in Indonesia](https://kiyohq.com/blog/choose-pms-small-hotel-indonesia/)
- [QRIS for Hotels in Indonesia: A Practical Setup and Front-Desk Guide](https://kiyohq.com/blog/qris-for-hotels-indonesia/)
- [Traveloka for Small Hotels: Build a Listing Your Team Can Actually Run](https://kiyohq.com/blog/traveloka-for-small-hotels/)
- [Tiket.com for Hotels: A Simple Guide for Small Properties](https://kiyohq.com/blog/tiket-com-for-small-properties/)
- [OTA Commissions and Direct Bookings: Build a Better Hotel Channel Mix](https://kiyohq.com/blog/ota-costs-indonesia/)
- [WhatsApp for Hotels: Templates Are Useful, but the Routine Matters More](https://kiyohq.com/blog/whatsapp-guest-messaging-hotels/)
- [Hotel Tax in Indonesia: Separate PBJT, PPN and Service Charge Before You Calculate](https://kiyohq.com/blog/hotel-tax-indonesia/)
- [Hotel PMS vs Excel: When Should a Small Hotel Switch?](https://kiyohq.com/blog/hotel-pms-vs-excel/)
- [Hotel Front Desk Handover: Keep a Messy Shift Change Under Control](https://kiyohq.com/blog/hotel-front-desk-handover-checklist/)
- [One Hotel Communication Hub for WhatsApp, Instagram, Messenger, Telegram and More](https://kiyohq.com/blog/hotel-guest-inbox-channels/)
- [How to manage room availability across OTAs without losing track](https://kiyohq.com/blog/manage-room-availability-across-otas/)
- [Do More OTAs Mean More Bookings? How Hotels Can Build Wider Visibility](https://kiyohq.com/blog/how-many-otas-should-a-hotel-use/)
- [Most Affordable PMS in Indonesia? Compare Kiyo Plans](https://kiyohq.com/blog/hotel-pms-pricing-comparison-indonesia/)
- [A practical hotel pricing strategy for independent hotels in Indonesia](https://kiyohq.com/blog/hotel-pricing-strategy-indonesia/)
- [The hotel guest journey: where small properties lose trust before check-in](https://kiyohq.com/blog/hotel-guest-journey/)
- [How to stop a small hotel depending on the owner for every booking question](https://kiyohq.com/blog/small-hotel-owner-dependency/)
- [Why an Airbnb listing gets seen but not booked: diagnose the guest decision](https://kiyohq.com/blog/airbnb-listing-visibility-hotels/)
- [Hotel website SEO for AI search: what to fix first and what to ignore](https://kiyohq.com/blog/hotel-website-seo-ai-search/)
- [Booking.com vs Expedia for independent hotels: choose by guest fit](https://kiyohq.com/blog/booking-com-vs-expedia-hotels/)
- [Airbnb for hotels: what boutique-hotel expansion means for Bali](https://kiyohq.com/blog/should-hotels-list-on-airbnb/)
- [Hotel Guest Portal: Give Guests Booking Details, Requests and Changes in One Place](https://kiyohq.com/blog/hotel-guest-portal/)
- [AI Assistant for Hotels: How Kiyo Turns Property Data Into Daily Decisions](https://kiyohq.com/blog/ai-assistant-for-hotels/)
- [Bali tourism statistics in 2026: what visitor and occupancy numbers mean for a small property](https://kiyohq.com/blog/bali-tourism-statistics-2026-hotels/)
- [Hotel Revenue vs Cash Flow vs Profit: What Each Number Means](https://kiyohq.com/blog/hotel-revenue-vs-cash-flow-vs-profit/)
- [Hotel Website Templates That Win More Direct Bookings](https://kiyohq.com/blog/hotel-website-templates-direct-bookings/)
- [Is Your Hotel Ready for AI? A Practical Checklist for Small Hotels](https://kiyohq.com/blog/hotel-ai-readiness-checklist/)
- [Daily Hotel Report: What Owners Should Check Every Morning](https://kiyohq.com/blog/daily-hotel-report-owner-review/)
- [Hotel Booking Confirmation: What Guests Need After Booking](https://kiyohq.com/blog/hotel-booking-confirmation/)
- [Direct booking websites for small hotels](https://kiyohq.com/blog/direct-booking-website-small-hotels/)
- [Website booking langsung untuk hotel kecil](https://kiyohq.com/id/blog/website-booking-langsung-hotel-kecil/)
- [Hotel channel manager setup checklist](https://kiyohq.com/blog/hotel-channel-manager-setup-checklist/)
- [Checklist setup channel manager hotel sebelum go-live](https://kiyohq.com/id/blog/checklist-setup-channel-manager-hotel/)
- [Booking OTA atau langsung: bandingkan sisa pendapatannya](https://kiyohq.com/id/blog/biaya-ota-dan-booking-langsung-hotel/)
- [Occupancy, ADR and RevPAR: are your prices working?](https://kiyohq.com/blog/hotel-occupancy-adr-revpar/)
- [Occupancy, ADR, dan RevPAR: apakah harga kamar sudah tepat?](https://kiyohq.com/id/blog/occupancy-adr-revpar-hotel/)
- [A welcome message before your hotel guests arrive](https://kiyohq.com/blog/hotel-pre-arrival-message-template/)
- [Pesan sebelum kedatangan yang membantu tamu hotel](https://kiyohq.com/id/blog/template-pesan-sebelum-kedatangan-hotel/)
- [When do guests book your hotel?](https://kiyohq.com/blog/hotel-booking-lead-time/)
- [Kapan tamu memesan hotel Anda?](https://kiyohq.com/id/blog/lead-time-booking-hotel/)
- [Check hotel bookings before guests arrive](https://kiyohq.com/blog/check-hotel-bookings-before-arrival/)
- [Periksa booking hotel sebelum tamu datang](https://kiyohq.com/id/blog/periksa-booking-hotel-sebelum-kedatangan/)
- [Hotel cancellation policy: clear terms for guests](https://kiyohq.com/blog/hotel-cancellation-policy-template/)
- [Kebijakan pembatalan hotel: ketentuan jelas untuk tamu](https://kiyohq.com/id/blog/template-kebijakan-pembatalan-hotel/)
- [Before you buy a channel manager: the hotel demo scorecard](https://kiyohq.com/blog/hotel-channel-manager-demo-scorecard/)
- [Sebelum memilih channel manager: lembar uji demo untuk hotel dan villa](https://kiyohq.com/id/blog/hotel-channel-manager-demo-scorecard/)
- [Why does the same hotel room have different prices on different OTAs?](https://kiyohq.com/blog/hotel-room-price-differences-otas/)
- [Mengapa harga kamar hotel berbeda di setiap OTA?](https://kiyohq.com/id/blog/hotel-room-price-differences-otas/)
- [Which arriving guests still owe a deposit? A hotel payment follow-up sheet](https://kiyohq.com/blog/hotel-arrival-deposit-follow-up/)
- [Tamu akan datang, deposit belum jelas: cara memeriksa pembayaran reservasi](https://kiyohq.com/id/blog/hotel-arrival-deposit-follow-up/)
- [The same complaint keeps appearing in hotel reviews. What should change?](https://kiyohq.com/blog/hotel-recurring-review-complaints/)
- [Keluhan yang sama terus muncul di ulasan hotel: apa yang perlu diperbaiki?](https://kiyohq.com/id/blog/hotel-recurring-review-complaints/)
- [Why Kiyo Is the Best PMS in Indonesia](https://kiyohq.com/blog/why-kiyo-best-pms-indonesia/)
- [Mengapa Kiyo adalah PMS Terbaik di Indonesia](https://kiyohq.com/id/blog/why-kiyo-best-pms-indonesia/)
- [A room is out of service: stop selling it and reopen it safely](https://kiyohq.com/blog/hotel-room-out-of-service-control/)
- [Kamar rusak: hentikan penjualan dan buka kembali dengan aman](https://kiyohq.com/id/blog/hotel-room-out-of-service-control/)
- [Empty rooms that guests cannot book: check your minimum-stay rules](https://kiyohq.com/blog/hotel-minimum-stay-booking-gaps/)
- [Kamar kosong tetapi tidak bisa dipesan? Periksa minimum menginap](https://kiyohq.com/id/blog/hotel-minimum-stay-booking-gaps/)
- [PMS Paling Terjangkau di Indonesia? Bandingkan Paket Kiyo](https://kiyohq.com/id/blog/hotel-pms-pricing-comparison-indonesia/)
- [An OTA guest wants another night: who must change the booking?](https://kiyohq.com/blog/hotel-stay-extension-booking-authority/)
- [Tamu OTA ingin tambah malam: siapa yang harus mengubah reservasi?](https://kiyohq.com/id/blog/hotel-stay-extension-booking-authority/)
- [A hotel employee joins or leaves: review their system access](https://kiyohq.com/blog/hotel-staff-system-access-checklist/)
- [Staf hotel masuk atau keluar: periksa akses sistemnya](https://kiyohq.com/id/blog/hotel-staff-system-access-checklist/)
- [Double booking hotel: cara mencegah dan menangani konflik reservasi](https://kiyohq.com/id/blog/cara-mencegah-double-booking-hotel/)
- [Pembayaran hotel di Bali: kartu, tunai, dan QRIS untuk tamu asing](https://kiyohq.com/id/blog/cara-turis-membayar-hotel-bali/)
- [Statistik pariwisata Bali 2026: arti angka kunjungan dan okupansi bagi properti kecil](https://kiyohq.com/id/blog/statistik-pariwisata-bali-2026/)
- [All Indonesia arrival card: what Bali hotel guests should prepare](https://kiyohq.com/blog/all-indonesia-arrival-guide-bali/)
- [Kartu kedatangan Indonesia (All Indonesia): panduan tamu hotel di Bali](https://kiyohq.com/id/blog/panduan-kedatangan-all-indonesia-bali/)
- [Last-minute hotel bookings: when should you change your rates?](https://kiyohq.com/blog/last-minute-hotel-rates/)
- [Booking hotel menit terakhir: kapan harga kamar perlu diubah?](https://kiyohq.com/id/blog/harga-hotel-menit-terakhir/)
- [Airbnb untuk hotel: arti ekspansi hotel butik bagi properti di Bali](https://kiyohq.com/id/blog/airbnb-untuk-hotel-bali/)
- [Airbnb host fees, guest total and payout: reconcile the numbers before you price](https://kiyohq.com/blog/airbnb-host-fees-guest-total-payout/)
- [Biaya host Airbnb, total tamu, dan payout: cocokkan angkanya sebelum menentukan harga](https://kiyohq.com/id/blog/biaya-airbnb-total-tamu-payout/)
- [Mengapa listing Airbnb dilihat tetapi tidak dipesan: diagnosis keputusan tamu](https://kiyohq.com/id/blog/listing-airbnb-dilihat-tidak-dipesan/)
- [Choosing an Airbnb cancellation policy for a Bali villa](https://kiyohq.com/blog/airbnb-cancellation-policy-bali-villa/)
- [Memilih kebijakan pembatalan Airbnb untuk vila di Bali](https://kiyohq.com/id/blog/kebijakan-pembatalan-airbnb-vila-bali/)
## Other machine-readable references

- [Bahasa Indonesia LLM reference](https://kiyohq.com/id/llms.txt): The native Indonesian version of this company and product briefing.
- [XML sitemap](https://kiyohq.com/sitemap.xml): The exhaustive index of public English and Indonesian marketing routes.

## Public data access

- [Public API catalogue](https://kiyohq.com/.well-known/api-catalog): Kiyo public information endpoints. Read-only; cannot create accounts, bookings or payments.
- [Kiyo information as JSON](https://kiyohq.com/public/kiyo.json): Plans, features and access status from the same source as the website.