Name a site or draw an area. GeoBit watches it 24 hours a day and sends you what matters: corroborated alerts with the map, a digest every morning, a SITREP when something happens. A named GeoBit analyst takes the decisions. You buy the finished watch, at one price per site per month, agreed before it starts.
Illustrative watch view · not live data
Not a dashboard to staff. The system reads, sorts and drafts around the clock, and a named GeoBit analyst holds the decisions. You hear from it when something matters, and every morning either way.
Every event, alert and report, in every language, is measured against your area. Sweeps run as often as every 15 minutes, or hourly or daily if you want it quieter.
Not “protest in the region” but “protest forming two kilometers from your gate, two sources, medium severity.” By email, text, webhook or the field app.
What happened overnight, what is open and how it ended, written from the record. When nothing happened, it says “all quiet.”
Drafted when a case crosses the line or changes: the event, the place, the time, severity, confidence, who is exposed and what was done.
Anything consequential reaches a named GeoBit analyst already triaged, evidenced and drafted. Before anyone is paged, a claim must clear three unrelated source families.
What happened across your sites, what was escalated and why, and where the trend is going. Thresholds are tuned for the month ahead.
Also on the board: your sites ranked worst first, with the reason in plain words, and a threat matrix you can click through to the events behind each cell. Ask a question in plain English any time and get pins with sources back.
The unit is one site or area of interest, watched for one month. You pay one price per site per month, agreed before the watch starts. No seats, no hourly billing, and no charge for the number of people on the floor.
The system does the reading and the drafting. People hold the keys. What the system may do on its own is written down for each client and enforced in code.
Every consequential action reaches a named GeoBit analyst with the evidence attached and the draft ready. The AI recommends. A person decides, and their name goes on the record. Nobody is woken for a rumor.
A public statement, an evacuation recommendation or a mass notification to more than 50 people never fires on its own, at any tier. The heaviest actions need two named people. Every outbound action also passes a second-model review for accuracy and proportionality first.
Every action and decision goes into an append-only log. Each record carries the hash of the one before it, so an edit or a deletion breaks the chain at the exact line. Any decision can be rebuilt afterward, the AI's reasoning included.
You choose how much the system may do without asking. It starts at the most cautious tier. It moves up only after 30 days of measured accuracy and sign-off from two named people, and it drops back on its own if it gets things wrong.
It checks itself every hour. Feed freshness, audit-chain integrity, alert channels armed, loop heartbeat. Anything red goes to a person straight away. One master switch, held by a human.
Watching sites around the clock has meant a staffed room: operators on day and night shifts, often with sister centers following the sun. The Watch delivers what that room produced, without the room. It replaces the shifts, not your security team. You keep the standards and the decision.
| The job | A staffed room | The Watch |
|---|---|---|
| Who watches | Ten to fifteen operators per center, on rotating shifts | The system reads without a break. Named GeoBit analysts take the decisions |
| Handovers | Two or three a day, each one a place to drop the thread | None. The record is the handover |
| Languages | Whatever the people on shift can read | Every language, translated as it arrives |
| Adding sites | Effort grows with every site added | The same floor, ten areas or ten thousand |
| The record | Shift logs and memory | A hash-chained log. Every decision can be rebuilt with its reasoning |
| Standing it up | A room, a build-out and a hiring cycle | Send your sites. The watch starts the next business day |
That is the capacity the system adds. It carries the reading, the sorting and the drafting, so your people spend their hours on judgment and on the calls only they can make. And because you pay per site, you pay for coverage, not for the shift pattern behind it.
Send the sites or areas, what should trigger an alert and who receives it. We agree the list of units and one price per site per month, in writing.
Sites load from one file, up to 20,000. The watch starts the next business day after signature. We pick the starting autonomy tier with you.
Within three to five business days, the escalation tree is set up and the templates are agreed. Alerts arrive where you asked.
Run it next to the way you watch today for a week. Compare what it caught and how fast. Tune the thresholds.
What it caught, what it ignored and what was escalated, all from the record. Add or drop sites for the next month.
One month minimum, then month to month. Sites can be added or dropped at each review.
The full watch floor: the seven-step loop, the duty desk and the escalation chain. One worked example of the system.
Read more →How areas are drawn, swept and judged, and how an alert reaches you.
Read more →The threat picture around a single site, and how it is handed to the watch.
Read more →Everything behind the watch, in one system. Every engagement comes with all of it.
Read more →Send us the sites or areas you want watched and what should trigger an alert. We come back within one working day with the list of units, a start date and one price per site per month.