A lighthouse, not a wall
The Pharos of Alexandria stood for centuries and never stopped a single ship. It stood over dark water and told captains what was there, early enough to matter. That is the whole design brief for this company.
Why this exists
Hotels are attacked in a way that most security tooling is not looking for. Nobody breaks into the property management system on a Tuesday afternoon. Somebody copies the booking page, puts it on a domain one character away from the real one, buys a little search advertising, and takes deposits for three weeks.
The hotel finds out when a guest arrives holding a confirmation number that does not exist. By then the money is gone, the guest is furious, and the only people who can help are a registrar and an abuse desk who both want evidence the hotel does not have.
Nothing in a firewall sees that attack, because the attack never touches the hotel. It runs entirely on someone else’s server, out of the hotel’s own markup.
PharosHub was built for that specific gap, and then extended to the adjacent one — the reconnaissance that happens before an intrusion, which every access log records and nobody reads.
What we will not do
A security vendor is bought on trust and can only spend it once. These are commitments, not aspirations, and each of them is enforced somewhere in the code rather than in a policy document.
We will not invent telemetry
No demo attack is ever shown as real. Seeded data carries a banner that cannot be dismissed, and it runs through the same scoring engine as live traffic — a demo that bypasses the engine proves nothing about the engine.
We will not claim completeness
Someone who strips our beacon from their copy will not appear. We say so on the landing page, in the docs, and in the terms. A monitoring product that implies total coverage is worse than none, because it tells everyone to stop looking.
We will not touch your guests' data
The package does not read cookies, sessions, form fields, or request bodies from your real routes. It cannot leak what it never collects.
We will not act against a third party for you
Not the clone, not its host, not its registrar. We help you assemble evidence they can act on. Taking action against someone else is your decision and your legal footing, not ours.
We will not alert twice about one thing
Enforced by a unique index in the database rather than remembered by a flag. An alerting system that gets filtered has negative value — it consumed attention and returned nothing.
How we work
We are a small, fully remote team. There is no office to visit and no sales department to get past — the person answering support@pharoshub.cloud is someone who has read the code.
We publish what the product cannot do alongside what it can, we price it on the pricing page rather than behind a call, and the install is a single npm package you can read in your own node_modules. Nothing is minified and nothing is obfuscated. You are installing this in front of a booking flow; you are entitled to read every line of it first.
Support runs 09:00–18:00 SGT, and we answer within one working day. If you are mid-incident, put URGENT in the subject and we will move.
See it on your own site
Five minutes to install. Nothing charged until you choose a plan.