Personal AI Ecosystem
Not another chatbot. Not another collection of subscriptions. I wanted an AI that could know me, remember, work beside me, attend meetings, help build software, use compute I control, and eventually share both work and life with me.
The narration could not be loaded. Open the audio file.
0:00 / 10:12
Why this exists
Chat, meeting notes, coding, planning, calendars, knowledge, voice, avatars, and model access often live in separate products. Each company owns another slice of context, charges another subscription, and stores another piece of identity. I want something different.
“The pieces already existed. The difficult part was making them behave like one system.”
System architecture
HomePilot holds the center: identity, memory, knowledge, policy, and orchestration. The other projects give that intelligence a workplace, a presence, compute, and a way to help build itself—with me in control.
Different surfaces
I do not want a DayPilot AI, an Avatar AI, a Meeting AI, and a Coding AI that behave like strangers. I want the same underlying identity and continuity wherever the conversation happens.
A day with the system · vision
HomePilot brings the priorities and context. DayPilot presents the workday.
GitPilot helps implement a feature, using a model routed through OllaBridge.
MeetingSense is designed to listen, transcribe, understand shared material, and track actions.
HomePilot could surface three decisions, two actions, and one unresolved question—then ask permission before creating anything.
Future presenter and coach capabilities can prepare context and talking points.
DayPilot goes quiet. Professional tools recede.
The same persona appears through the 3D Avatar for voice, cooking, language practice, exercise, a movie, VR, or conversation.
Long-term direction
The goal is not a model that only waits for prompts. It is an AI that can know what is happening, remember what matters, prepare me, work with me, and follow up—while asking before any consequential action.
“Good morning. You have three meetings today. The pricing proposal from last week is still open. I prepared the previous decisions and latest document. Would you like a five-minute briefing?”
Afterward: “Three decisions were made. You own two actions. Shall I create the tasks and draft the follow-up?”
GitPilot × OllaBridge
I can use my own AI infrastructure to help build my own AI infrastructure. This is not autonomous recursive self-improvement. It is an engineering loop with an explicit human checkpoint.
Local-first, not cloud-absolutist
I decide where models and data run.
Applications depend on open interfaces instead of one vendor.
Commercial providers are used when they add value, not because the system has no alternative.
I do not want zero cloud.
I want zero forced cloud.
Local-first and open-source by default makes paid AI optional rather than mandatory. Hardware, electricity, optional APIs, and cloud compute can still cost money.
What this solves
The projects
These are active repositories at different stages. The cards separate the role each project already plays from the larger integration direction.
HomePilot is who my AI is. The personal AI backend for personas, identity, memory, knowledge, multimodal capabilities, tools, communication, policy, and model access.
DayPilot is how my AI works with me. A professional cockpit where HomePilot personas can operate with context and approval.
The Avatar is how my AI shares space with me. Embodiment, voice, expression, and a future social and leisure surface for the same persona.
OllaBridge is where my AI thinks. One OpenAI-compatible control plane between applications and the place inference actually runs.
GitPilot helps me build the ecosystem itself. Specialized agents explore, plan, generate, test, and review—with approval modes and GitHub integration.
The manifesto
OWN THE AI.OWN THE MEMORY.OWN THE COMPUTE.OWN THE TOOLS.
Where this is going
The projects exist independently and continue to evolve.
Personas, model routing, meeting intelligence, and tools converge.
DayPilot and HomePilot form a continuous work system.
The Avatar gives the same intelligence an embodied surface.
The AI becomes reachable across devices while respecting boundaries.
Build in public
This is a personal engineering project and a long-term vision—not a pitch deck. The repositories are public so people can learn, fork, improve, or use only the pieces they need.
The reason
One that knows my work. Remembers what matters. Runs on infrastructure I can control. Helps build the software around it. And eventually shares both productive and ordinary moments with me.
— Ruslan Magana Vsevolodovna