About

Built on a real house, by the person you will work with.

I am Max Goshay, a systems engineer in San Rafael. Headland began as the interface I wanted for my own property: one place for lighting, solar and battery, water, cameras, climate, and everything that keeps the house running.

Max Goshay, founder and builder of Headland.

It started with the lighting

My house had a 1990s Lutron system with 157 loads and 50 keypads. The hardware still worked, but the dealer and programming tools were long gone. For about fifteen years, nobody could meaningfully change it.

I recovered the system through its documented serial protocol and brought it onto a modern console without replacing the equipment in the walls. Then the rest of the property joined it: Sol-Ark solar and battery, Flume water, cameras, climate, and vehicles.

That console became Headland. The public demo uses sample data, but the architecture and integrations come from the real system running at my home. Explore the live console, no login required.

The work behind Headland

I trained in sound engineering, where every problem begins with signal flow: what enters, what changes it, where it goes, and what depends on it. I later worked with controlled-environment systems at Plenty and have managed complex properties and the digital systems behind them since 2018.

The common thread is not "smart home" hardware. It is systems work: documenting what exists, understanding the dependencies, making the state visible, and building controls that fail predictably.

Headland is new. The systems work is not.

Headland does not have decades of company history or a national support desk. It has a working property, completed rescue work, active field engineering, and one accountable builder in Marin.

When you write, I read it. When the project needs engineering, I do it. If the right answer is an electrician, plumber, alarm contractor, or a manufacturer's dealer, I will tell you before you spend money in the wrong direction.

Why ownership is the company

Property systems should not become unusable because a subscription changed, a dealer retired, or the original builder stopped answering.

Owned, not rented. That one word is the whole company.

Every Headland build runs on hardware and accounts the client owns. You receive the device library, diagrams, configuration, and access. Core functions continue locally. Care is optional.

If Headland disappeared tomorrow, the property would keep working. Another capable engineer could understand the system and continue the work. That is not a contingency plan added later; it is the design requirement from the start.

Start with a walkthrough

Show me what the property runs on and what is currently invisible, fragmented, or impossible to change. I will map the useful next step and give you a written scope and price before work begins.

Written by Max Goshay in San Rafael, California. The Lutron lighting, Sol-Ark solar and battery, Flume water monitoring, cameras, and vehicle integrations described here run on the property behind Headland. The public console uses sample data modeled on that system. Text text Headland or email email Headland.