Talorys – A self-hosted personal AI agent on Cloudflare's free tier
An open-source project called Talorys offers a personal AI assistant that runs entirely in a user’s own Cloudflare account, using Workers, Workers AI, Durable Objects, and Pages to provide chat, task management, and reminders on Cloudflare’s free tier. Commenters are intrigued by the architecture and ease of deployment but strongly debate whether something so tightly tied to Cloudflare’s platform can truly be called “self-hosted,” raising concerns about vendor lock-in, changing “free” limits, and billing transparency. Several also note performance and feature gaps (like semantic recall and web access) while suggesting that similar agent setups could be adapted to run on local or alternative infrastructure.
Project overview and initial reactions
- Talorys is an open-source personal AI agent deployed entirely in the user’s own Cloudflare account, using Workers, Workers AI, Durable Objects, and Pages.
- Features include chat with persistent memory, task/note/project management, reminders/automations, password protection, and one-command deployment.
- Several commenters found it “neat” and “very easy to set up,” praising the architecture and responsiveness.
- Others are unsure of the use case beyond existing chatbots, or would prefer more task-centric UX instead of a chat interface.
“Self-hosted” terminology debate
- A major thread disputes calling this “self-hosted” when it depends completely on Cloudflare’s platform and free tier.
- One camp: self-hosted must mean running on hardware physically owned/controlled at home; if a third party can pull the plug, it’s not self-hosted.
- Another camp: running software yourself on a VPS or cloud provider still counts, as long as you manage the software and have control over the instance.
- Many propose alternative labels: “self-managed,” “self-configured,” “cloud-hosted,” or “hosted on Cloudflare’s free tier” as more accurate.
- There is concern about “watering down” established terms and about marketing-driven redefinitions.
Cloudflare dependence, pricing, and performance
- Commenters note the contradiction between “no reliance on hosted services” and full dependence on multiple Cloudflare products.
- Concerns raised: free tiers can change, neuron-based AI billing is confusing, and some report unexpected or large bills (Workers, Durable Objects) with poor support.
- Cloudflare’s “neurons” are described as a confusing virtual currency; some share rough token and cost equivalents, others liken it to mobile-game style obfuscation.
- Workers AI is reported as slow for interactive use but acceptable for background jobs.
Extensibility and portability
- Because it’s open source, several argue it’s straightforward to swap Workers AI for a local model server or other backends (e.g., celld), though not out-of-the-box.
- Others counter that requiring Cloudflare-specific primitives (Workers, Durable Objects, KV) makes it more “deploy-it-yourself on Cloudflare” than truly provider-agnostic.
Feature ideas and limitations
- Desired additions include web search/webpage access, semantic memory/recall (e.g., respecting “I am vegetarian” in later suggestions), and a robust speech interface similar to smart speakers.
- One commenter notes that without good semantic recall, “memory” feels limited in practice.