Owning your AI: why I self-host a personal assistant with long-term memory

For the past few months I’ve been running my personal AI assistant on my own hardware instead of a third-party cloud. Here’s why — and what I learned.

The problem with cloud assistants

Every message, every preference, every bit of context you share with a hosted assistant lives on someone else’s servers. You don’t control retention, you can’t inspect the memory, and you can’t move it. For a tool that’s supposed to know you, that’s a lot of trust to outsource.

What self-hosting changes

• Memory stays local. Facts, preferences and conversation history live in a local SQLite database, with backups I control.
• Runs on my own hardware. A cheap VPS or a mini-PC at home — no vendor lock-in.
• The model is swappable. The assistant layer is decoupled from the underlying LLM, so I can change providers without losing my data.

The setup

Mine lives in Telegram, keeps long-term memory, and exposes skills (calendar, notes, browser automation, reminders). One example of this approach is avelina.ai — a self-hosted personal assistant with persistent memory, designed for people who want to own their data rather than rent it.

Takeaway

Self-hosting an AI assistant isn’t about distrust of any one company — it’s about data sovereignty. If an assistant is going to accumulate a model of who you are, it makes sense for that model to live somewhere you control.

Happy to answer questions about the architecture in the comments.