Home/Technology
Field lab
Every environment we are asked to protect has a shape that no vendor anticipated: a 1920s shul with three entrances and one camera, a leased office floor with a shared riser, a yeshiva where four hundred children arrive within eleven minutes. The lab exists to make tools for that shape.
01/ WHY WE BUILD
A cheap multi-tool in a volunteer's pocket proves one thing: the door was never really secured. That is useful as a demonstration and useless as a programme. What a community actually needs is a repeatable procedure, a device that survives a South Florida summer, and a person who knows what to do with the reading.
So we build the boring version: documented, repairable, field-serviceable, and cheap enough to deploy in quantity across a campus rather than in a single showcase.
Illustrative rendering of a sweep display. Live readings are taken on site with calibrated equipment.
02/ PIPELINE
Nothing leaves the lab because it is interesting. It leaves because an operator in the field asked for it and could not buy it.
A recurring gap shows up across at least three engagements. One client's problem is a custom job, not a product.
Bench build with off-the-shelf modules. Ugly, cheap, wrong twice, working on the third iteration.
Run in a live environment with a named operator. If it needs an engineer to interpret, it is not finished.
One-page operating card, failure modes, maintenance interval, spare parts list, legal limits.
Installed, trained, handed over. Your staff own it; we maintain it under the programme.
03/ CAPABILITY SET
Rogue access points, unauthorised transmitters, jammer signatures and the wireless inventory nobody documented. Sub-GHz, 2.4 and 5 GHz, plus the bands your alarm and access systems live on.
Whether the badge, fob, keypad or phone credential on your door is doing what the integrator claimed. Cloning tests, reader placement, fail-safe behaviour under power loss.
Technical and physical sweep of offices, boardrooms, residences and vehicles for recording devices, trackers and unauthorised network implants.
Radio plans, encrypted messaging rollout, fallback paths when the cell network is congested or down, and a comms card small enough to live in a wallet.
Low-power mesh sensors for doors, gates, cabinets and perimeter zones, reporting to a phone-based console that works for a volunteer staff and an on-call director alike.
Detection and documentation of consumer drone activity over campuses and events, including flight-path logging and a response procedure that stays inside federal law.
04/ FIELD KIT
Kits are assembled per environment. These are the four shapes most engagements land on.
| Kit | Contents | Built for | Status |
|---|---|---|---|
| Sweep kit | Portable spectrum receiver, probe set, physical inspection tools, sweep log | Boardrooms, residences, vehicles | Deployed |
| Access rig | Credential reader, cloning bench, door-hardware test set, inventory app | Facility access review | Deployed |
| Campus mesh | Door and gate sensors, mesh gateway, alert console, drill script | Schools, yeshivas, campuses | Deployed |
| Event pack | Radio plan, credentialed staff comms, incident log, command post kit | Gatherings of 100–2,000 | In build |
05/ DISCIPLINE
The same tools that find a rogue transmitter can be used to build one. We are deliberate about which side of that line we operate on, and we put it in writing.
Every device, frequency and system we touch is named in a signed scope. We do not test what we were not asked to test.
Receive first. Transmission only where the scope permits it and the law allows it.
We do not sell jammers, interceptors, credential harvesters or anything whose only use is attack.
Collected material is hashed, logged and stored under a documented chain of custody from the first minute.
Lab intake
Describe the environment and the constraint. If it is a build we can take on, we will say so with a scope and a date.