🌿Animal Room
Open by design

What runs, where data stays, and how changes are tested.

Animal Room handles care records and habitat data. These are the boundaries, checks, and limits you can verify for yourself.

Read the sourceTry the sample demo
Data boundaries

Local first, by default.

Core monitoring and care records need no Animal Room account or cloud service.

🏠

Records stay on your machine

Shed stores its database in its local data directory. Bask stores local settings and readings. Neither app contains product analytics or telemetry.

📡

The Bluetooth scanner only listens

Bask reads supported sensor broadcasts. It does not make a sensor a network gateway, pair with phones, or accept Bluetooth commands.

🔐

Haven uses a limited feed

The room display reads token-protected care totals and unfinished work. It has no write access and excludes household identities and access codes.

Outside connections

Nothing extra connects unless you enable it.

Installation, updates, and optional integrations are the exceptions to normal local use.

Normal operation

  • Care records, schedules, readings, and the Haven display stay on the local network.
  • The public website has no analytics, advertisements, account system, or third-party embeds.
  • The interactive demo runs only in the page and sends no demo actions anywhere.
  • Exports and backups are created for the keeper to store where they choose.

Deliberate outside connections

  • Installation and updates download scripts or container images from the public project repositories.
  • Optional phone alerts and smart-device integrations contact the provider the keeper configures.
  • GitHub, Instagram, and Ko-fi links leave this site only when clicked.
  • Remote access is not enabled by the installer; do not expose app ports directly to the internet.
Public evidence

Code and tests you can inspect.

These links open the current source, test runs, releases, and security pages. Passing checks reduce risk; they do not prove software is defect-free.

Development process

AI-assisted, human reviewed.

AI tools help draft, investigate, and test. A human keeper chooses the behavior, reviews the changes, runs the real system, and decides what gets published.

This is not formal certification or an independent audit. It is a transparent development process with public source and test history.

✓
Automated project checksEach repository runs its own checks on proposed and published changes. The exact workflow and result history are public above.
✓
Installer failure testingThe unified installer exercises selection, memory limits, health failures, broken integration, custom ports, repeated updates, and rollback without deleting data.
✓
Privacy scanningThe public repository checks for private identities and known secret-like material before its site deploys.
✓
Real-room useBask, Shed, and Haven began as tools for the keeper’s own animal room and continue to be exercised there between releases.
✓
Correctable public recordSource, issues, releases, and change history stay visible so concrete reports can be reproduced and fixed.

Known limits and responsible use

No self-hosted app can make an unsafe network safe, and monitoring software is not a substitute for looking at the animal or checking equipment directly.

  • Use the apps on a trusted home network unless you maintain your own secure remote-access layer.
  • Keep the host operating system and Animal Room containers updated.
  • Treat sensor data as an aid; verify surprising or safety-critical readings with another instrument.
  • Keep backups somewhere other than the machine running the apps.
  • Species targets and schedules still need reputable husbandry sources and veterinary guidance where appropriate.

Found a concrete security problem? Read the security policy and report it privately. Ordinary bugs belong in the affected project’s issue tracker.