What we build
One app for the whole house. Not one app per vendor.
Everything is quiet.
Two doors are unlocked and the rest are shut. All 24 cameras have a live picture. Music is playing in the family room, and inside it is 74 degrees.
- Dining Room Hallway
- Patio Hanging Lights
- Chandelier
- Kitchen Foyer
- Under Cabinet
- One sign-in
- for every system in the house
- 78 loads
- of lighting mapped across 17 rooms
- 24 cameras
- two separate systems, shown on one wall
- In the house
- on its own hardware, reached privately
- Every system behind one sign-in: lighting, cameras, climate, locks, gates, music, the televisions, and the robot vacuum
- Lighting mapped load by load and room by room, so a light is named for the room it is in and not for the channel it sits on
- Both camera systems on one wall, the cloud cameras and the recorder on site, instead of one app each
- Runs on a small machine in the house and is reached over a private network, with nothing forwarded to the open internet
- The network watched on the same screen: every access point, anything on the wire that belongs to nobody, and every power cut on record, four of them in the first fourteen days
- Handed over documented, on hardware and credentials that are yours, and kept running after the install
Inside the house
Six apps, four remotes and a keypad nobody understood, replaced by one screen.
Lighting
Named for the room, not the channel
A lighting processor knows loads and channels. A person knows the kitchen. Every load in the house is read off the processor and mapped to the room it actually lights, so the list reads like the house instead of like the panel. Dim it from a phone, and the keypads on the wall keep working exactly as they did.
Doors, gates and cameras
One wall, and a straight answer
Cameras from both systems land on one wall. The locks and the gates sit beside them with their battery levels and a log of what opened when. The front page answers the question people actually ask at night, which is whether anything is still open, and it answers it in a sentence.
The network underneath
On the same screen as the lights
Access points, devices on the wire that belong to nobody, and every power cut on record. It sits on the home screen because in a house this size the network is what fails, and noticing on the day is the whole difference between a short fix and a lost weekend.
- Family Room
- Pool
- Terrace
- Kitchen
Why a software company
On this build, almost nothing that broke was the smart part.
The cameras stopped recording because the network was renumbered underneath them. The lights stopped answering because a firmware update quietly reset a bridge. An installer hands over a working house on the day. Nearly everything after that is network and systems work, which is the same discipline we bring to a business. That is why this sits next to the automation and security practices instead of in a showroom, and why the network sits on the home screen rather than in a controller nobody opens.
Beyond one house
Different building, same shape of work.
The page above describes one build, so it is told in rooms and gates. The work underneath is not specific to a home. It is the same job wherever a building has grown a separate app for every system it bought, and nobody owns the whole picture.
A building with an app per vendor
Lighting, access, cameras and climate bought from four companies over ten years, each with its own login and its own idea of what a room is called.
Things that fail quietly
A camera that stopped recording in March and got noticed in June. Monitoring that says so on the day it happens, in language a person can act on.
No lock-in, and no kill switch
The documentation and the credentials are yours, and the system runs on hardware in your building. There is no account we hold that can switch it off. We stay because the management is worth paying for, not because leaving would break something.
Someone to call afterwards
Standing management once the install is done, including the vendor firmware updates that arrive unannounced and change how a device behaves.
Let's talk
Tell me what your team does by hand, or what you want to build.
Or email nicholas@papacorporation.com directly.