Get This Tool
Teya
Pricing
- Model
- Free
Summary
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.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Persistent household memory across conversations, so the agent knows that Tuesday means football pickup without being re-briefed every week — which is the specific failure mode of every commercial smart speaker.
- Fully self-hosted on a spare Android phone with no cloud dependency, which means household calendar data does not leave your network and the agent does not stop working when a vendor's pricing changes.
- Apache-2.0 licensed with a configurable model layer per THIRD_PARTY_MODELS.md, so swapping the underlying LLM is a configuration change rather than a platform migration.
- Skills architecture described in the repo allows the agent's capabilities to grow, so a household that starts with reminders can extend to home-control tasks without replacing the platform.
- Zero infrastructure cost beyond the Android device, so there is no monthly bill eroding the case for keeping it running long-term.
Cons
Sign in to edit- Setup requires Android build tooling and Gradle configuration — there is no APK download or one-tap install described in the README. Any household member who is not the person who built it cannot recover from a broken state, which means a single point of failure sits between the family and their morning reminders.
- Any capability the agent does not already have requires writing a new skill, which means extending Teya for a genuinely new use case — say, integrating a specific calendar API or a home-automation system — puts you in the position of maintaining a fork. When that maintenance burden compounds across two or three extensions, teams move to a platform with a plugin marketplace rather than a skills directory they authored themselves.
- No API surface is available, per the project page, which means Teya cannot be called programmatically from other household tools or automation scripts. Households that want bidirectional integration with an existing Home Assistant setup or a third-party calendar service hit a dead end and either build a custom bridge or switch to a platform that exposes an API.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Android 8.0+
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-07-20T03:16:48.019Z
Best For
Who it's for
- Users with spare Android phones
- DIY home automation without servers
What it does well
- Household reminders and calendar coordination
- Voice-based family task management
- Shared home control via a single wall-mounted device
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare Teya
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is Teya free?
- Yes — Teya is fully free to use. There is no paid tier.
- Is Teya open source?
- Yes. Teya is open source.
- Can I self-host Teya?
- Yes. Teya supports self-hosting on your own infrastructure.
- What platforms does Teya support?
- Teya is available on: Android 8.0+.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
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.