01About

A different kind of trust layer.

StaySignals is not a generic fraud vendor bolted onto hotel checkout. It is a trust layer built inside a hotel OTA, solving a problem we hit every day — bookings that aren’t real intent to stay.

02Origin

Built by team that has been there.

StaySignals was born from operating a hotel OTA that processes bookings across a global supplier network. After years of watching non-customer traffic slip through every off-the-shelf tool — bots running price discovery, automation draining inventory, checkouts with no intent to arrive — we stopped trying to force-fit generic anti-fraud and built what a hotel OTA actually needs.

That difference is in the taxonomy. Our signals are tuned for hotel booking patterns. Every signal exists because we saw the pattern in production first.

03Journey

Our story.

2021
Metasearch
Our team launched a hotel and vacation-rental metasearch across 15+ countries in the US, EU, LATAM, and SEA. It quickly became one of the largest metasearch sites in several markets.
2023
First-party booking
Moved from meta to our own checkout. Processed over $50M in bookings through a global supplier network of 10+ industry partners — and hit non-customer traffic at production scale for the first time.
2025
Trust tooling goes internal-first
What started as a shared config file — score thresholds, signal taxonomy, decision log — became a dedicated internal service. Every first-party booking started flowing through it.
2026
StaySignals ships
Spun out as a standalone trust layer any hotel OTA can adopt. One browser SDK, one POST /v1/risk call — the same protection against non-customer traffic.

04What we do

Score every checkout before fulfillment.

One browser SDK. One POST /v1/risk call. Back comes a risk score, a risk level, and a suggested action — allow, challenge, or deny. Every decision is logged with booking context and per-field risk, and every log is replayable against a different risk setting to project the impact of a change before shipping it.

01 / Principle

Signals, not alarms

The job is measurement, not spectacle. Every booking comes back as a score, a level, and a suggested action — calm instrumentation your stack can act on.

02 / Principle

Operators set the risk

You own the dial. Maximize protection, balance, or maximize revenue — and see projected impact on historical traffic before flipping a setting in production.

03 / Principle

Non-customer traffic is the frame

We catch bookings that aren't real intent to stay: automated bots, and humans without real booking intent. We are not a chargeback shield, a compliance badge, or a payments layer.

05Backed by