This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine.
What if the most important things we preserve with AI aren't generated images, productivity metrics, or chat histories—but the stories of the people we love?
Family traditions, childhood memories, the sound of a grandparent telling an old story, and the little moments that shaped us can easily disappear with time. Yet sharing these deeply personal memories with cloud-based AI raises an important question: Should preserving our memories require giving up control over them?
That question inspired me to build Echoes — a private digital memory garden powered by open-weight AI.
🌿 What I Built
Echoes is a local-first memory archive designed to help people preserve family stories, oral histories, personal milestones, and meaningful moments.
Users can record memories with dates, people, places, categories, and tags, then explore them through a searchable archive or chronological timeline.
Echoes also uses a locally running open-weight model to help transform saved memories into thoughtful, structured keepsakes.
Key features
- Memory Garden: Preserve and organize personal stories in one place.
- Chronological Timeline: Revisit memories across years without inventing dates for undated recollections.
- AI Reflections: Generate remembrance cards, reflective tributes, grounded summaries, and oral-history narratives.
- People and Places: Keep the context surrounding each memory connected to its story.
- Backup and Restore: Export memories as portable JSON and restore them with duplicate-conflict handling.
- Fictional Demo Archive: Explore the experience using sample stories rather than anyone's personal memories.
The design deliberately avoids pretending to recreate deceased people or simulate their consciousness. Echoes works with the memories people choose to preserve—not fabricated messages from those who are gone.
🚀 Live Demo
Try Echoes: https://echoes-frontend-1mss.onrender.com/
Source code: https://github.com/Tanmay-Dalvi/echoes
For the best first look, explore the fictional demo archive, open the timeline, and visit the AI Reflections and Backup & Data sections.
🛠️ How I Built It
The central design decision was to keep the AI component replaceable and support local inference through Ollama with the open-weight gemma3:1b model.
The application combines a web interface, a backend API, local database storage, and an AI provider layer. The local installation is designed to keep saved memories on the user's machine while using the locally running model for AI-assisted writing.
The major components are:
- Frontend: React, TypeScript, and Vite.
- Backend: Python and FastAPI.
- Data storage: SQLite with full-text search indexing.
-
AI inference: Ollama running
gemma3:1blocally. - AI tasks: Remembrance cards, reflective writing, grounded summarization, and oral-history narratives.
- Data portability: JSON export and validated restore workflows.
- Deployment: Render-hosted web demo, with local inference remaining a separate deployment mode.
The architecture is intentionally modular: the memory archive is useful on its own, while AI adds another way to revisit and reflect on preserved stories.
Architecture
The following diagram describes the intended local installation. The Render demo is a separate deployment mode and must not be assumed to have access to Ollama running on a user's computer.
🔓 Why Open Innovation Matters
For Echoes, open innovation is not just about choosing a different model. It changes the relationship between the user, their memories, and the technology processing them.
1. Personal stories deserve privacy
A family memory can contain names, relationships, locations, grief, and details that were never meant for a third-party service.
With local inference, the model can process memories on the same machine where the application runs. The local architecture avoids sending those memories to a remote AI provider for inference.
2. AI should remain replaceable
Using an open-weight model through Ollama gives developers greater control over their inference environment. Models can be evaluated, replaced, and adapted as requirements evolve, without designing the entire product around one proprietary model API.
3. The experience can work without cloud inference
Once the application and model are installed locally, the core memory archive and supported AI features can work without an internet connection, provided the required dependencies and model are already available.
That makes local-first AI especially meaningful for a tool whose purpose is to preserve personal history rather than depend on a continuously available cloud service.
4. The user should own the archive
Portable JSON export and restore make memories easier to back up and move. The archive should remain useful even when a particular model, hosting provider, or AI service is unavailable.
Open innovation gives Echoes a path toward privacy, portability, and user control that a cloud-only architecture would make harder to achieve.
🕯️ The Spirit of It
The theme Ghost in the Machine naturally brings to mind haunted technology, simulated personalities, and machines that appear to remember.
I wanted to explore a quieter interpretation.
The most meaningful echoes aren't artificial voices claiming to be someone we've lost. They are the real stories that person left behind: a recipe, a family tradition, an unforgettable afternoon, a lesson, or a small detail that would otherwise fade.
AI can help us organize and reflect on those stories, but it should never replace the person behind them.
Echoes is my attempt to build technology that helps memories stay human.
🔮 What's Next
I'd like to keep improving Echoes with stronger local-model support, more robust backup and recovery, accessibility improvements, and additional ways to preserve oral histories while maintaining the project's privacy-first principles.
The long-term goal is simple: make it easier for people to preserve the stories they want future generations to remember.
🏆 Challenge
Built for the Hacktoberfest Open-Source AI Challenge — Week 4: Ghost in the Machine.
- Live demo: https://echoes-frontend-1mss.onrender.com
- GitHub: https://github.com/Tanmay-Dalvi/echoes
I'd love feedback on the local-first architecture, the memory-preservation experience, and how open-weight AI can be used responsibly for deeply personal applications.
Top comments (0)