Care that stays close.
Protection built in.

A base unit with backup power.

The main application runs on your base unit. A base unit with a built-in battery can keep running if its charger loses power. Models without a built-in battery need a separate backup power supply for the same protection.

The base unit's battery does not power enclosure controllers, heaters, lights, or network equipment. Those need their own power, and backup power where required.

One controller per enclosure.

Each enclosure has its own microcontroller receiving readings from its assigned wireless sensors. Heat and light targets, limits, and schedules are saved on the base unit and in persistent storage on the enclosure controller. The controller confirms new settings only after saving them.

Control continues locally.

If the base stops communicating, the individual enclosure controller takes over heat and light decisions, using its saved settings and locally received wireless sensor readings.

Built in Redundancy and Hardware Monitoring

Safety and reliability are at the core of every part of the system. Local sensor checks and over-temperature cutoffs remain active even if the base fails to send commands. Timed heater commands prevent the heater from running forever if temperature sensors fail, and in the unlikely event that every sensor fails an alarm is generated and heat will turn off within 30 minutes to prevent overheating. Power monitoring can identify an outlet that is on but drawing no power, prompting a check of the bulb, heating element, or connection with an in-app alert.

Local storage. Local operation.

Habitat settings, sensor history, and animal care records are stored locally on the base unit. Core temperature control, lighting schedules, and humidity readings work without an internet connection.

Remote access, weather data and syncing, and cloud-delivered notifications need internet access, and a subscription is required. Local Wi-Fi is still required between devices in order to connect the base station and enclosure controllers, as well as to connect the iOS or Android apps. Location matching can be configured to either hold the most recently available weather information or fall back to a schedule you configure if the online connection fails and updates become unavailable.

A private identity for each base.

Each provisioned base has its own private key and device certificate for HTTPS connections from the client app over the local network. The app validates that certificate before sending credentials or habitat data.

The same-device development connection uses loopback. Sensor-controller links and camera protocols have their own security characteristics.

Protected remote access.

Remote access uses a Cloudflare Tunnel authenticated with that tunnel's own secret credentials. These are separate from the base unit's HTTPS certificate. Cloudflare provides the public HTTPS connection and carries requests through the tunnel to your base. Each device uses a unique private key and provisions its own tunnel; nothing is shared between units, to provide maximum security.

Your habitat database stays on the base, though requests and responses pass through Cloudflare when you connect remotely.