“What smart home hub should I get?” is the question every homeowner hits once they have more than a few connected devices. The three names that come up in every thread are Home Assistant, Apple HomeKit, and Amazon Alexa. Google Home is a fourth, but it has converged so heavily with Nest that it’s functionally a Nest discussion at this point.
All three work. None of them are wrong. But they serve genuinely different homeowners, and the choice has downstream consequences for device compatibility, network design, privacy, and what happens when a vendor changes direction. Here’s the honest version.
Apple HomeKit: the simplest, most constrained option
What it is
HomeKit is Apple’s smart-home platform, built into every iPhone, iPad, Mac, Apple TV, and HomePod. It uses the Apple Home app as the single control surface and runs automations on an Apple TV or HomePod Mini acting as a home hub.
What it does well
- Setup is effortless. Scan the HomeKit code on the device, it appears in the Home app, it works. No YAML, no scripting, no debugging.
- Privacy-first architecture. HomeKit requires end-to-end encryption and processes automations locally on the home hub. No audio recordings sent to the cloud. No camera footage on Apple’s servers (unless you use HomeKit Secure Video with iCloud+, which is encrypted end-to-end).
- Siri integration. “Hey Siri, good night” runs a scene. It just works, within Apple’s ecosystem.
- Matter support. HomeKit was one of the first platforms to support Matter natively, which means the device selection is growing beyond the traditional HomeKit-certified list.
Where it falls short
- Limited automation logic. The Home app can do “when X happens, do Y.” It cannot do “when X happens, wait 5 minutes, check Z, and if Z is true then do Y, otherwise do W.” No conditionals, no variables, no templates.
- Device selection is narrower. Even with Matter, many popular devices (most UniFi gear, older Z-Wave devices, a lot of garage-door controllers) don’t speak HomeKit natively. Bridges exist (Homebridge, Home Assistant with HomeKit bridge) but add complexity.
- Apple-only household required. If anyone in the house uses Android, they cannot use the Home app at all. Shared households become awkward.
- No real dashboard. The Home app shows tiles. There is no floor-plan view, no energy dashboard, no history graph. You see what’s happening right now and nothing else.
Best for
All-Apple households that want simplicity, privacy, and a modest set of automations. Works great for lighting, locks, thermostats, and simple scenes. Struggles when the device count grows past 30–40 or the automation logic gets complex.
Amazon Alexa: the voice-first ecosystem
What it is
Alexa is Amazon’s voice assistant and smart-home platform, running on Echo devices, Fire TVs, and a huge range of third-party Alexa-built-in products. It has the largest device-compatibility list of any consumer platform.
What it does well
- Device compatibility is enormous. Almost every smart-home brand supports Alexa. If a device exists, it probably works with Alexa.
- Voice control is the best in class. Alexa understands more natural-language phrasing and handles multi-device voice commands better than Siri or Google Assistant for home automation.
- Routines are surprisingly capable. Alexa Routines can chain actions, add delays, include conditions (time, device state), and trigger from voice, schedule, motion, door sensor, or geolocation. More capable than HomeKit; less capable than Home Assistant.
- Multi-platform. Works on iOS and Android. No ecosystem lock-in on the phone side.
Where it falls short
- Cloud-dependent for almost everything. Alexa processes voice commands, routines, and most integrations in Amazon’s cloud. Internet goes down, Alexa goes dark. This is a meaningful difference from HomeKit (local) and Home Assistant (local).
- Privacy model is the opposite of HomeKit’s. Amazon records voice interactions, uses them to improve models, and has had well-publicized incidents of human review of voice recordings. Ring (Amazon- owned) has shared footage with law enforcement without user consent. If privacy matters to you, Alexa is the most exposed platform.
- The subscription layer is growing. Alexa Guard, Alexa Plus (announced 2025), Ring Protect — the free Alexa is getting thinner and the paid Alexa is getting more prominent. The vendor-dependency risk is real here.
- The app is a mess. The Alexa app has been widely criticized for years — slow, cluttered with shopping features, and hard to navigate for device management.
Best for
Voice-first households that want the widest possible device compatibility and don’t mind the cloud dependency or privacy trade-offs. Great for casual smart-home users who want “Alexa, turn on the lights” to work everywhere.
Home Assistant: the power tool
What it is
Home Assistant is open-source software that runs on a dedicated box (a Raspberry Pi, a Mini PC, or the official Home Assistant Green/Yellow hardware) in your house. It integrates with essentially everything — Z-Wave, Zigbee, Thread, Matter, Wi-Fi, Bluetooth, MQTT, and hundreds of cloud APIs — and processes all automations locally.
What it does well
- The most capable automation engine that exists. If/then/else, templates, scripts, state machines, time-based conditions, sensor thresholds, API calls, webhooks. If you can describe the automation, Home Assistant can run it.
- Local-first, vendor-neutral. No internet required for automations, no vendor cloud dependency, no subscription. Your data stays in your house.
- Dashboard flexibility. Custom dashboards with floor plans, energy monitoring, camera feeds, device history, and anything else you want to visualize. Wall-mounted tablets running the HA dashboard are a common install.
- Largest integration list in the industry. Over 2,500 integrations, most maintained by the community. If a product speaks any standard protocol, it works.
- Matter controller. Home Assistant is a full Matter controller, so any Matter-certified device works natively.
Where it falls short
- Setup complexity is real. Initial installation is straightforward, but building automations, debugging integrations, and maintaining YAML configurations takes technical comfort. It’s gotten dramatically easier in the last two years (the visual automation editor is genuinely good), but it’s still not “scan a code and done.”
- Updates can break things. Monthly releases occasionally change integration behavior. The community is good about documenting breaking changes, but you need to read the release notes before updating.
- Voice control requires extra setup. Home Assistant can integrate with Alexa, Google Assistant, or its own local voice assistant, but none of those are as polished out-of-the-box as native Alexa or Siri.
- No commercial support unless you pay for Cloud. Home Assistant Cloud ($75/year) adds remote access and voice assistant integration. Without it, remote access requires a VPN or manual setup.
Best for
Technically-inclined homeowners who want maximum control, privacy, and vendor independence. Also the right choice for installer-managed systems where the integrator handles the complexity and the homeowner gets a polished dashboard and reliable automations.
How they interact with the network
This is where our world intersects. All three platforms behave differently on a properly segmented network:
- HomeKit uses mDNS/Bonjour heavily. If your iPhones are on one VLAN and your HomeKit devices are on an IoT VLAN, you need an mDNS reflector between them. Same issue as Sonos.
- Alexa talks to everything through the cloud, so VLAN segmentation rarely breaks it — as long as the devices can reach the internet, Alexa finds them. The flip side is that everything routes through Amazon.
- Home Assistant lives on the local network and can be explicitly placed on any VLAN with firewall rules to reach IoT devices directly. It is the most network-architecture-friendly platform, because it was designed to be the local controller for everything.
Can you use more than one?
Yes, and many households do. A common combination:
- Home Assistant as the brain — runs all automations, manages all devices, serves the dashboard.
- HomeKit as a secondary interface — Home Assistant exposes devices to HomeKit via its built-in HomeKit bridge, so Apple users can use Siri and the Home app as a convenience layer.
- Alexa for voice — Home Assistant exposes devices to Alexa for voice commands in rooms with Echo devices.
This is the setup we install for clients who want the best of all worlds. Home Assistant is the single source of truth; the consumer platforms are convenience layers on top.
Our recommendation by household type
- All-Apple, wants simplicity, 20–30 devices: HomeKit. Done.
- Mixed household, voice-first, 10–50 devices: Alexa. Accept the privacy trade-off or don’t.
- Technical homeowner, 30+ devices, wants control: Home Assistant.
- Installer-managed, 50+ devices, cameras + access control + audio + lighting: Home Assistant as the brain, HomeKit and/or Alexa as voice interfaces.
Bottom line
HomeKit is the most private and simplest. Alexa is the most compatible and voice-friendly. Home Assistant is the most capable and vendor-proof. Most households pick one; the best installations layer all three with Home Assistant underneath. The right answer depends on the household, not the spec sheet.
Keystone Integration designs and installs smart-home systems across Highland and the rest of the Wasatch Front — Home Assistant deployments, HomeKit integration, network segmentation, and the infrastructure underneath. You can see the full list of what we do on our main site, or get in touch to scope the right platform for your house.