Bronit documentation
Bronit is a hotel platform built in Uzbekistan. Staff — an owner across every hotel in a business, or an admin scoped to one — take bookings, manage services (spa, pool, conference hall, transport), track payments, and get a Telegram feed for each. Around that sit the modules a business buys separately: a QR guest menu, an in-room television launcher, and a content-order tracker.
These pages describe how it works. They are written for people integrating with Bronit or working on it, not as a user manual — for that, start with the guide.
Start here
| What is Bronit | The product, in one page |
| Getting started | Setting up a business, a hotel and its first bookings |
The platform
| Architecture | The three layers, and why a module may import core but not the reverse |
| Auth and roles | Who a request is, what it may do, and which records it may touch |
| Data models | The collections and how they relate |
| Bookings and availability | How a slot is held, sold and released |
| Dashboard and calendar | The screens staff spend their day in |
| Pricing | Plans, modules and what a business is charged |
| Module lapse | What happens when a business stops paying for a module |
Integrations
| Bronit PMS integration | Talking to Bronit from another system |
| Menu integration | The guest menu and its orders |
| Telegram | Forum topics, booking and order notifications |
| Company bots | A bot per business, and how one is connected |
| Mini App setup | BotFather and the environment it needs |
| Website builder | The site a hotel gets with its account |
Shared
| Internationalisation | Three languages, one dictionary, and the rule that keeps them in step |
| News | What has changed recently |
Not everything Bronit has written down is here. Operational runbooks, deployment procedures and integration internals are kept internally; a document appears on this site only if it is explicitly marked for publication.