Security cameras are now standard equipment on American homes, and observant households in Brooklyn, Lakewood, Monsey, Los Angeles, and Miami buy them for the same reasons everyone else does. The complication arrives on Shabbat. A conventional doorbell camera is built to do exactly the thing the design needs to avoid: detect a person approaching, wake up, start recording, light an LED, and push a notification. Every one of those steps is triggered by the visitor.
Projects House approaches this as an engineering problem. Halachic rulings belong to a qualified posek; a manufacturer's role is to build a mechanism whose causal behavior is documented precisely enough that a posek can evaluate it. What follows describes design constraints and the architectures that address them.
Continuous Recording Versus Motion Triggering
This is the central architectural fork, and it drives nearly every other decision in the product.
A continuously recording system runs its sensor, encoder, and storage pipeline at a constant rate from before the observance period begins until after it ends. A person entering the frame changes the content of the recording but does not start, stop, or alter any process. Nothing wakes; nothing triggers. The system was already doing what it is doing.
A motion-triggered system does the opposite by design. It idles at low power, a passive infrared element or a low-resolution vision pipeline detects change, and that detection starts the recording chain. The efficiency that makes this attractive commercially is exactly the causal directness that makes it difficult here.
| Aspect | Continuous recording | Motion triggered |
|---|---|---|
| Causal chain from visitor | None; recording is already running | Visitor starts the recording process |
| Power | Mains or PoE effectively required | Battery operation practical for months |
| Storage per camera | High; continuous stream at chosen bitrate | Low; only event clips |
| Retrieval | Requires timeline search or later analysis | Events are pre-segmented |
| Typical fit | Homes and institutions with wired infrastructure | Retrofit and rental installations |
In practice, products serving this market are built around continuous capture with mains or Power over Ethernet, and any analytics that classify or tag events are run later, off the live path, or after the period ends. That is a meaningful hardware decision: it rules out most battery doorbells and pushes the design toward wired cameras and a local recorder. It is the same architectural instinct described in alarm and security systems on Shabbat, where always-armed beats event-armed.
Doorbell Cameras Specifically
The doorbell is the hardest product in the category because it bundles four triggered behaviors into one device: a mechanical or capacitive button, a chime, a camera stream, and a phone notification. Design approaches that show up:
- Decouple the button from everything. A wired doorbell button that closes a mechanical contact is a separate question from the camera. Some products simply disable the electronic chime path during the period and leave a mechanical chime.
- Continuous stream, no event logic. The camera streams to a local recorder at all times. Pressing the button does not start, stop, or change the stream. The stream exists whether anyone comes to the door or not.
- Scheduled notification. If any notification is generated at all, it is emitted by a scheduler on a fixed interval that reports state, rather than pushed the instant an event occurs.
- Interior viewing station. An always-on monitor inside the house showing the live feed, with no user interaction required to see who is at the door. Continuous-monitor design of this kind is closely related to baby monitors for Shabbat observant homes.
Indicator LEDs Are Part of the Design
An easy detail to miss. Most camera modules ship with a status LED that changes when recording starts, when a person is detected, or when the link goes up. Infrared illuminators switch on when ambient light falls below a threshold, which is a light source turning on. Both need explicit treatment: either the emitter runs continuously for the whole period, or it is disabled for the period, or its state is governed only by the free-running schedule. Leaving it on the default automatic behavior means the product has an undocumented trigger path.
The same applies to infrared cut filters. Many cameras mechanically swap an IR-cut filter in and out based on measured light level, and that mechanism produces an audible click when it actuates. If the product uses one, decide whether it is locked in position for the period and say so in the specification. The general principles for status indication are covered in LED indicator design, and they apply here with an extra constraint.
Sensor and Optics Choices
Continuous recording changes the component calculus. Because the imager never sleeps, thermal behavior and sensor lifetime matter more than idle current. Rolling-shutter CMOS sensors with good low-light performance and a wide dynamic range handle a doorway lit by a porch light and daylight behind it better than a cheaper sensor with an aggressive auto-exposure algorithm that hunts. Fixing exposure and white balance to a stable configuration also reduces the number of things that visibly change during the period. Our guide to choosing an image sensor covers the tradeoffs in general terms; for this application, weight continuous-duty thermal performance heavily.
Storage, Retention, and Privacy
Continuous capture generates a lot of data. A single 1080p stream at a moderate bitrate runs roughly 15 to 30 GB per camera per day. A six-camera institutional installation recording continuously through a long weekend needs meaningful local storage, and that storage has to be sized for the worst case, not the average.
Retention policy is a design input, not an afterthought. Decide how long footage is kept, whether it is deleted automatically, who can retrieve it, and whether anything leaves the building. Cameras in senior living communities, schools, and hospital wings sit under state recording laws and institutional policy, and any cloud path brings in the obligations described in privacy compliance for connected product data. Many institutional buyers in this market specifically require local-only storage with no cloud dependency, which simplifies the halachic review and the privacy review at the same time.
Institutional Installations
The larger opportunities are institutional. Hotels running Shabbat programs, hospitals with observant patient populations, schools, and senior living facilities all need coverage that works seven days a week without asking staff or residents to trigger anything. Two requirements come up in almost every one of these projects.
First, integration with the existing building system. The camera system rarely stands alone; it ties into access control, elevators, and emergency lighting, and those subsystems have their own behaviors during the period. Second, a clearly documented override for emergencies. Life safety takes precedence, and a system that cannot be operated normally during a genuine emergency will not be accepted by any facility. Both of these mirror the requirements in Shabbat technology for hotels and institutions.
Adjacent to security, the same always-recording architecture is what makes remote kosher supervision with cameras and IoT workable in food production facilities, where a mashgiach needs continuous coverage rather than event clips.
Building It So It Can Be Reviewed
Document the pipeline end to end: what runs continuously, what is scheduled, what is disabled during the period, and how each of those is enforced in firmware rather than by a user-facing setting. Provide measured evidence, including captures showing that the encoder bitrate and frame cadence do not change when a person enters the frame. Then let a qualified posek evaluate the mechanism.
Projects House designs camera and security products for observant households and institutions, covering imager selection, continuous-capture firmware, local storage architecture, and the documentation package the review requires. Send your requirements through our contact form.