Estevano.

The context

A hotel's day is made of small requests. A towel, a late breakfast, a broken air conditioning unit, a table at eight. In most hotels none of that is written down anywhere a manager could read later: it travels by voice, gets noted on paper or in a staff chat group, and is either done or forgotten. The tools the industry sells are built around the conversation with the guest before and after the stay, through email campaigns and WhatsApp. The hours in between, the ones the guest remembers, are left to memory.

Estevano is Polargate's answer to that, and it is our own product rather than a client's: we build it, we run it and we sell it. That is also why it is on this site. It is the longest running proof of what we build.

What it is

Three pieces that only make sense together.

• A guest app, and a web version for hotels that prefer no install, where the guest orders room service, reports a problem, books an outlet or asks a question.
• An AI assistant that reads the request in the guest's own language and turns it into the right kind of ticket, with retrieval scoped to that hotel and nothing else.
• A staff console where every department, room service, housekeeping, maintenance, reception, IT, restaurant and security, sees its own queue, takes ownership and closes with a state, with the alarm sounding on the phones of whoever is on shift.

Behind them, the hotel's own data: the Opera Cloud connector has been in production for months and syncs every five minutes. A hotel without that connector can still start on day one, because reception can register a guest by hand or send a link with an expiring token by email, SMS or WhatsApp.

What the numbers say

Santo Domingo Bay has been running it with real guests for months. Over a four-month window it handled around 2,500 requests, about twenty a day, and effectively all of them were closed.

• Median resolution: 16 minutes. Mean 25.
• Median first response: 3 minutes. Mean 8.
• 93 percent of requests were created by the guest through the app or the assistant, with no queue and no phone call.
• 90 percent were resolved inside the hour, with a p90 around 59 minutes.
• Room service is 37 percent of the volume and housekeeping 28 percent, so two thirds of everything a hotel is asked for lands in those two departments.

That last line is the one general managers stop at, because it is the first time the hotel can see where its staff hours go.

How it is built

The product started as a React application packaged with Capacitor. Scaling audits pushed us to native hybrid apps in React Native: a global guest app for hotels on the standard plans, a branded guest app for hotels on the top plan, and a single staff app that works across every hotel a person belongs to. Postgres, Storage, Auth and Edge Functions run on Supabase, with the data hosted in the EU.

Security was reviewed by an external consultant against 23 points. Row-level security is enabled on all 68 tables, staff authenticate with a server-side JWT, the guest PIN is hashed with bcrypt and locks out after repeated attempts, the AI retrieval layer fails closed when no hotel is identified, and CORS is allow-listed across 39 functions. Isolation was tested between two real hotels, with no cross-leak. Eleven of the 23 points are resolved and twelve, a WAF, an immutable log, a penetration test and MFA among them, belong to the scale roadmap rather than to daily operation.

What it does not do yet

Online check-in, identity verification and the digital room key are not in the product. They are on the roadmap and they are not written, so we do not present them as features. The same goes for PMS coverage: Opera Cloud is in production, and any other PMS needs its own connector written against that vendor's API.

Why it belongs on this page

Everything Polargate sells to a hotel, the app, the operational plumbing, the AI that has to be right rather than chatty, the security posture a chain's IT team will ask about, exists here in production with real guests and measured numbers rather than as a promise.