Aisha
Free
Users seeking culturally grounded AI responses
Ask your smart speaker who's picking the kids up from football, and you get silence — it has no notion of two calendars, no memory that this question comes up every Tuesday. Teya exists because that amnesia is the actual problem.
Teya is an open-source, Android-based home agent that listens, holds context across conversations, and acts across apps — running on a spare phone mounted on a wall. There is no cloud subscription, no hosted API, and no vendor to call when it stops working: you own the stack. The README describes skills, a memory layer, and the ability to coordinate family schedules rather than just execute one-off commands. That self-contained architecture is also the ceiling — setup requires Android build tooling, and any skill that doesn't exist yet is yours to write. Families comfortable with a Gradle build and a spare Android device will find this fits a gap no commercial product fills; families who are not will hit a wall before the first reminder fires.
Bottom line: Teya is the right call for a technically confident household that wants a persistent, context-aware shared agent without a cloud dependency — and the wrong call the moment someone needs to add a skill and has never touched an Android project.
Find your fit
More options in Personal Assistants. Compare pricing, platforms, and features side by side.
Free
Users seeking culturally grounded AI responses
Freemium
Users of Claude, ChatGPT, or similar coding agents
Every home assistant on the market treats each request as a fresh start. Teya’s premise is that a home agent should carry context: knowing that Tuesday means football pickup, that two calendars need reconciling, that ‘did anyone call the plumber’ has history behind it. Built as a native Android application and deployed on a spare phone, Teya listens for household input, retains memory across sessions, and executes tasks across apps — without a server, a subscription, or an intermediary cloud. The core workflow is install-on-Android, configure via environment variables, and mount the device somewhere central.
The differentiating architecture is the absence of any hosted layer. The repo is Apache-2.0 licensed, self-hosted by definition, and the vendor states no paid offerings exist anywhere in the project. That means your household data stays local, the agent keeps running if a SaaS company pivots, and there is no API rate limit throttling your Tuesday-morning calendar check. It also means every operational decision — model choice, skill additions, updates — falls on whoever set it up.
Teya fits a specific household profile: one person who is comfortable with Android build tooling, Gradle, and reading a README that is honest about its DIY nature. For that person, the gap it fills is real — shared calendar coordination, voice-driven family task management, and a single always-on device that remembers context across the week. For a household without that person, setup does not complete. And for any use case that requires a skill Teya does not ship with, the path forward is writing it yourself, which means maintaining a fork rather than configuring a setting.
The repository shows 164 commits, an Apache-2.0 license, a THIRD_PARTY_MODELS.md indicating the model layer is configurable, and a skills directory that the docs describe as extensible. There is no last-commit timestamp visible in the scraped content, so recency of maintenance cannot be confirmed from available sources.
Sign in to rate this tool or suggest an edit.