A platform that runs a home, or ten thousand.
The same product on two routes: hosted by ALYT with nothing in the house but the hub, or self-hosted on a box you own with your name on it.
Two ways to run it
Hosted by ALYT
For a household, or a partner's customers
- Nothing in the house but the hub
- The hub holds its own outbound link, over TLS
- No container per home: a session, not a server
- Updates and new connectors arrive centrally
- Measured with 5,000 devices on one host while a live home answered in 50 ms
Self-hosted
For an installer, an operator or a household that asks for the box; on request, with approval
- A home agent on a machine on site, with local connectors and an optional local voice stack
- White label: on your hardware, the brand is yours
- Mirrors the public connector catalogue hourly, outbound only
- Export a tenant as one document and import it elsewhere in one transaction
- The property keeps working with the internet down
Homes, rooms and people
More than one home
A person can belong to several homes. The phone opens the nearest one, decided in the foreground from a coarse position that is never stored.
Rooms are the pairing
A hub and a speaker in the same room are bound automatically. No dropdown, no pairing screen, for any device that ever joins.
Owner, Resident, Guest
Owners configure. Residents control and read history. Guests are pinned to one home and always have a checkout that revokes their access first.
Invitations only
A verified account is added at once; anyone else gets a single-use link that lives seven days. A booking API lets a short-let platform invite a guest by reservation.
Presence without a geofence
A resident can be admitted only while their phone is on the home's own Wi-Fi. No location ever reaches the platform.
Routines you can read back
When any of these happens, only if all of these hold, do these in order. Triggers include a phrase, a time, sunrise or sunset, a thing's state and presence. Steps include rooms, things, spoken lines, waits, notifications and music. Every run is a row you can read: what fired it, why it was skipped, and what each step did.
Planned, then done: one end state per thing, only the difference is sent
Runs on the hub when the internet is away
Templates offered only when the house can actually do them
Exported to Alexa as scenes
Music without holding a single service token
Every service the household already pays for is a row in the Sonos favorites list. ALYT plays any of them from a tile, a routine or a word. Spotify and Plex add your own library on top, with read-only scopes. One media screen on web, phone and TV: search first, every source searchable alone, never empty before you type.
Cameras through a relay, not a port
Live view runs through a media relay with no published port. Watch and talk share one WebRTC session, capped at ten minutes, closed within twenty seconds of a lost heartbeat. A stored picture is not a video frame, so a battery camera is never woken by a thumbnail.
The dashboard is the home's, not the viewer's
Weather from the home's own address, the home's own clock and timezone, and up to forty pinned tiles shared by every screen. Units follow the person, converted at every edge. Light and dark are both first class. The console never fabricates: a figure the API cannot answer reads "unknown".
Measured, not estimated
Measured 2026-09-08 on one host. The first bound at 5,000 devices is the MQTT bridge at 1.45 cores; 10,000 is a second bridge on a shared subscription, supported and not yet run.
Give your things a home that thinks.
Register your home, connect what you already own, and put the hub in the room where you talk the most.