rociiu/talorys

Talorys is a personal assistant for one person: it chats, keeps durable facts about you, holds tasks and notes, and fires scheduled reminders. The interesting part is where it lives — entirely inside your own Cloudflare account, so there is no database or backend for the authors to run. If that hosting model fits you, it is a tidy self-hosted option; if you expected a box on your desk, read the limitations first.

The problem

You want one assistant that remembers your preferences, tracks a few tasks and nudges you at the right time, instead of stitching a chatbot, a notes app and a reminders service together and copying context between them. The friction is usually setup: running a server, a database and an API key, or handing all that data to a hosted product. Talorys replaces that step with a single installer command that provisions Cloudflare Pages, a private Worker and a SQLite-backed Durable Object in your account. The result is a login-protected web app where chat, memory and scheduling all operate on the same stored data.

What's different

The architecture is the pitch. The browser talks only to your Pages site; a service-binding call reaches a Worker that is deployed with no public URL, and that Worker forwards to a TalorysAgent Durable Object. Conversations, memories, tasks, notes, automations and settings sit in that object's SQLite storage, and its alarms drive reminders and recurring routines. Chat runs on Workers AI's glm-4.7-flash with streaming and tool calling, and memories are filtered so only the most relevant ones go into each prompt.

The practical benefit is a small, inspectable footprint: one command installs it, and there is a documented update path that reuses the same resources with append-only migrations. The trade-off is that "self-hosted" here means "hosted in your Cloudflare tenant," not on your hardware — the dependency is Cloudflare's platform and its model. The authors say there is no telemetry, but Cloudflare still processes your messages for Workers AI inference, which the README states plainly. Operating it means keeping a Cloudflare account and using the project's CLI for status, updates and password resets rather than treating it as an appliance you never touch.

Who should try it

Good fit: a single technical user who already has (or is happy to create) a Cloudflare account, wants a private assistant for personal notes, tasks and reminders, and prefers a one-command deploy to maintaining a VPS. The free-tier framing and single-user login match someone who wants low upkeep and does not need multi-user sharing.

Poor fit: anyone whose definition of self-hosting requires their own hardware or a non-Cloudflare host, or who needs to keep prompts away from a third-party inference provider. The README does document a second install route that deploys it as a single Worker without Pages, but it still lands in the same Cloudflare account rather than removing the platform dependency.

Requirements and limitations

You need Node.js 22+ and a Cloudflare account with permission to edit Workers and Pages. The installer uses Wrangler's OAuth login or an API token with the listed scopes; it does not need a Global API Key. Chat depends on Workers AI's free daily allocation — when it runs out, you wait for the reset or switch on Demo mode, and a paid plan changes the billing picture. The semantic recall feature is off by default and must be enabled in settings or at install time, so search-by-meaning is not there out of the box.

The ongoing costs are attention, not money: update by re-running the installer, reset a forgotten password through the same CLI (which signs out every device), and know that a fresh pages.dev site may take a few minutes to pass health checks. Treat the security model as a document to read — the README points to docs/security.md — rather than assume the private Worker removes every concern.

HotRepo's take

HotRepo's only dated signal is a 2026-10-24 observation on the NEW-REPOSITORY board (typescript), where it showed 1,383 total stars at #9; that is a snapshot, not daily growth, and there is insufficient daily-board history to judge whether interest persists. The 2026-10-10 HN thread drew 331 points and 155 comments; much of the visible debate is about whether Cloudflare counts as self-hosting, which tells you the term matters more than the mechanics to some readers. Before deploying, confirm the Workers AI allocation and current platform terms for your account, since that is where the real constraints sit.