Review privacy, memory, billing, and scaling defaults
3
Open Telegram
Your AI starts owner-only and can change by policy
Private by default
Share by policy
Paid access when you choose
Proof of work
Create my private AI for family trip planning.
I will keep your AI owner-only, use private memory, and ask before sharing it.
Make a packing checklist app.
Done. I created file-backed HTML, CSS, and JS so we can iterate on it.
WebApp created by chat
StorageHTML / CSS / JS files
Memoryper-user private
Accessowner-only by default
Next stepask in Telegram
Reference AI
Dodo proves the loop
Dodo is the internal reference personal AI: chat-first creation,
scoped memory, file-backed WebApps, owner policy, and paid-public controls
are tested there before becoming product defaults.
Made today
Family
Packing Checklist
A private trip app with allowlisted tasks and per-person notes.
Learning
Flashcard Coach
A small WebApp built from chat, then refined with follow-up prompts.
Work
Status Board
A file-backed dashboard that can ask the AI for summaries.
What people do with it
🧠
A personal AI that knows you
Pick its personality. It remembers your conversations, preferences, context. Gets better over time.
🎮
Build stuff together
Games to play with friends, project trackers, learning apps, dashboards — just describe it.
👥
Add it to group chats
Allowlist family, friends, or teammates when you want group-scoped context with clear boundaries.
🌍
Share when you choose
Keep your AI non-public with allowlists, or make it public later with clear access, memory, and billing rules.