The most useful AI companion is also the most sensitive one. If it can react to your presence, webcam, gestures, voice, focus patterns, foreground apps, and desktop context, then privacy cannot be an afterthought.
That is why AIPET is built around a local-first promise. Your desktop companion should live on your machine first, process personal signals locally when possible, and avoid making cloud dependency the default cost of intelligence.
Why desktop AI is different
A chatbot only sees what you type. A true desktop companion can understand richer context: whether you are present, whether focus is slipping, whether a stranger is near the desk, whether you are speaking, and whether the system itself needs to slow down.
That extra awareness is exactly what makes the product useful. It is also what makes a cloud-first design feel wrong for many users.
The AIPET privacy stance
Webcam and face signals should be processed locally. Voice and chat should work without a required API key. Focus and activity insights should belong to the user. The business model should be the product, not surveillance.
Local AI, local presence, local control
AIPET is planned around local models, local computer vision, local focus data, and a companion that reacts where your work actually happens. Optional integrations may exist later, but the default experience is built to stand without a mandatory cloud account.
Who this is for
This page is for people who are excited by ambient AI, but skeptical of always-online products that collect more than they need. Developers, researchers, writers, consultants, creators, and privacy-sensitive users should not have to choose between useful context and basic trust.
AIPET starts with macOS early access because a careful first desktop release matters. The long-term product direction is broader than one operating system.