Frequently Asked Questions

Does Selora Homes have access to my customer’s Home Assistant?

No. Selora Homes does not have automatic access to customer installations. All remote access must be explicitly requested and approved by the homeowner through a secure workflow. See our Request Remote Access documentation for details on how the request-and-approve process works.

Can Selora Homes see devices on the customer’s network?

No. Selora Homes has no access to cameras, sensors, or any other devices on the customer’s local network. Selora Hub communicates only with Selora Homes infrastructure for health monitoring, configuration updates, and backups. We cannot view, control, or access any devices connected to the customer’s smart home system.

Can Selora Hub run inside a virtual machine?

Yes. Bare metal on dedicated hardware is still the recommended deployment, but Selora Hub runs fine as a guest VM on any hypervisor that can boot a UEFI NixOS image and expose nested virtualization to the guest. The inner Home Assistant VM needs KVM (or the ARM equivalent) for acceptable performance, otherwise it falls back to slow software emulation.

Both architectures are supported:

• x86_64 hosts: Proxmox VE, Unraid, ESXi, Hyper-V, libvirt/QEMU. Enable nested KVM (kvm-intel nested=1 / kvm-amd nested=1) and use a host-type CPU.
• aarch64 hosts: UTM or Parallels on Apple Silicon, libvirt/QEMU on ARM Linux. Use the -aarch64 installer ISO .

Plan for at least 8 GB RAM and 4 vCPUs. None of these configurations are formally tested by Selora Homes yet. Proxmox VE and Unraid are the most common community choices.

For Selora AI Local , run Ollama or llama.cpp in a sibling VM with GPU passthrough rather than stacking it inside Selora Hub.

See the Virtualized Environments page for the full host and guest configuration.