AI Otel, OtelCiro and TRBNB: how the ecosystem’s arms fit together

AI Otel is building the Tourism Brain of Türkiye: the technology and intelligence layer that connects hotels, travelers, tourism businesses and distribution channels. OtelCiro is the ecosystem's hotel growth and consultancy arm and is Live, working with paying hotel clients today. TRBNB is the sales and distribution arm and is in development. They are arms of one ecosystem, not subsidiaries, and each keeps its own brand, customer and status word.

Three names appear on the same site, in the same voice, sometimes in the same paragraph. A hotel owner reading them has one practical question: who does what, and which of these can I actually use this month? This article answers that question arm by arm, explains why the names stay separate, and gives you a routing rule so you know which door to use before you write the first email.

What is AI Otel building, in one sentence?#

AI Otel is building the Tourism Brain of Türkiye: the technology and intelligence layer that connects hotels, travelers, tourism businesses and distribution channels across Türkiye. That sentence is a fixed definition, and the verb is always "building", never "is". Treat it as a statement of direction, not a claim that the work is finished.

Why a layer, not another app#

A hotel already runs several systems: a reservations system, a channel manager, an accounting program, maybe a spa or restaurant tool. A layer does not replace them. It connects them, and it serves the same operations to three different audiences at once: the hotel team, partner systems, and the AI assistants people already use.

The word "layer" also matters because of what it implies about work. Software that behaves the same way for every hotel can be built once and shipped. But before any system can be configured to help a specific hotel, someone has to sit with that hotel and look at how it actually sells today: where its demand comes from, who answers an inquiry, what happens to the bill. That is people work, and it is the reason the ecosystem has two arms rather than one product.

What the layer has to hold#

The layer has three jobs. First, define each hotel action once, so that a reservation, a rate change or a housekeeping task means the same thing whether a person does it, a partner system does it, or an AI assistant does it. Second, hold the rules about who may do what, and which steps need a person's confirmation before anything happens. Third, keep a record of every change that can be read later, so the hotel can answer the question "who changed this, and when".

The status is honest and checkable. The shared core is built and runs in a public demo environment on a fictional hotel. The Hotel Brain is architected and entering training, the Platform Brain is architected, and the Industry Brain is on the roadmap. There is no trained model yet. What you can check today is the demo, the facts page and the status words, not a promise about a future release. For the wider picture, see The Tourism Brain of Türkiye: what AI Otel is building.

What does OtelCiro do, and how far along is it?#

OtelCiro is the ecosystem's hotel growth and consultancy company, and it is the one part of the ecosystem that is Live: it works with paying hotel clients today. "Live" here has a precise meaning: people doing paid consultancy work with hotels now. It is not a statement that the software is in production, and the two claims should never be merged into one sentence.

What the independent review covers#

OtelCiro starts with an independent review of how a hotel sells today, before any recommendation is made. The reason is simple: a recommendation that arrives before the diagnosis is a guess with a price attached. The review asks a set of questions the hotel has to answer about itself.

The work that follows the review is consultancy work: judgment delivered by named people on a piece of work, over time. A fuller version of the question set is in How does your hotel sell today? An independent review checklist.

What OtelCiro does not publish#

OtelCiro publishes no client counts, no client names, no testimonials, no case studies and no uplift figures. The approved sentence is the whole claim: "OtelCiro works with paying hotel clients today. The hotel operating system is built and working, ahead of launch." Anything stronger than that sentence, anywhere, is not from us.

The line between the two arms is one sentence: OtelCiro sells judgment and work; the platform sells software. A hotel can take either, or both.

What is TRBNB, and what can you expect from it today?#

TRBNB is the ecosystem's sales and distribution arm, and it is in development: there is nothing to sign up for today. The role line is the whole description: sales and distribution. Features, prices, terms and launch dates are deliberately not sketched here, because those decisions are not made, and an article that guessed at them would be inventing them.

Why we publish no launch date#

A status word describes what exists now, not what is hoped for. "In development" is a description of the present state of the work. "Coming soon" is a marketing phrase, and it belongs to a different vocabulary. A date would be a promise the work cannot yet support, so no date is published.

What does exist on the distribution side today is a platform capability, not a TRBNB product: a B2B distribution hub where hotels publish contracted rates to travel agencies on their own terms, and every quote shows its working, meaning the hotel's net rate, each pricing rule that fired, and the final price. It is built with seed data, and no agency is connected yet. In the meantime, a hotel or an agency has nothing to sign and nothing to migrate. Ask for a briefing, and the answer will describe the state of the work, not a date.

One thing will not change at launch: the status word changes only when the thing itself works and is in customers' hands.

Why do the three keep separate names?#

Because each arm makes a different promise to a different customer, and folding them under one name would make every promise vague. The promises are not interchangeable, and they fail differently.

Three promises, three failure modes#

A product promise is that the software behaves the same way for every hotel. It fails if the system breaks or behaves inconsistently. A consultancy promise is judgment delivered by named people on a piece of work. It fails if the work is generic or the people are not accountable. A distribution promise is reach and terms. It fails if the inventory does not reach buyers or the terms are not honored.

The customers differ too: a hotel owner buying advice, a hotel buying software, a travel agency buying inventory, an institution buying a briefing. One brand speaking to all four ends up speaking to none.

The correct word for the relationship is arms, "kol" in Turkish. Never subsidiaries, never "sister companies", and never "one brand". The benefit of the structure is the status discipline: one status word per name means a reader can tell in a single line which part of the ecosystem is Live, which is Built and which is in development.

What stays shared is the vocabulary, the same underlying system, and a designed loop: the consultancy sees how hotels actually sell, and the platform turns that into software other hotels can use. Every part is designed to feed the others. For how the shared system works, see AI Otel Core: how hotel teams, partners and AI share one system.

A rule of thumb for the reader: if the offer is people and work, it is OtelCiro; if it is software, it is the platform; if it is inventory reaching a buyer, it is TRBNB.

Which status word applies to which name?#

OtelCiro is Live, the hotel operating system is Built, and TRBNB is in development; the brains are architected and there is no trained model yet. The vocabulary is small and strict. Live means operating today. Built means working software ahead of launch, not in customers' hands. In development means being built. Architected means designed. Roadmap means planned.

The same five words are used in English and Turkish (Faaliyette, Geliştirildi, Geliştiriliyor, Tasarlandı, Yol haritasında), and the word "canlı" is never used for anything. A common misreading to avoid: a Built product is not a Live one, and a demo is not a customer. The demo hotel is fictional, and every mention of the demo says so. The status words are the reader's protection: they are the one part of the page that cannot be read generously. The full vocabulary is explained in Built or live? The five status words AI Otel uses.

Which door should you use?#

Hotels go to OtelCiro; institutions, partners and investors ask for a briefing. The routing depends on what you want, and the fastest way to decide is to match your sentence to the list below.

What to bring to the first conversation#

Bring your current channel mix, last month's numbers, and the one question about your own hotel that you cannot answer today. That question is the most useful thing in the meeting: it tells the people on the other side where to look first. For the vocabulary used in any answer, the AI Otel glossary covers the terms.

What to do next#

Pick the door that matches your question. A hotel that wants a hard look at how it sells today talks to OtelCiro, and the conversation starts with the independent review. An institution, partner or investor requests a briefing through https://ai-otel.com/contact. The three names fit together because each one carries a single promise and a single status word, so you never have to guess how far along the work is.