A personal AI assistant that you own, with no monthly subscription and no vendor-hosted backend, is the pitch of Talorys, a Show HN project that reached 58 points on Hacker News. It deploys with one command, npx create-talorys@latest, into your own Cloudflare account and is designed to run on the free plan. It is small (about a dozen commits, MIT license, 58 stars at the time of writing), but it is a clean reference for a pattern many builders want: a private, single-user agent with memory and schedules, running on serverless infrastructure.
This post explains what Talorys does, how it is built, what the "free" claim really means, and what Hacker News readers pushed back on.
Quick answers
| Question | Answer |
|---|---|
| What is it? | Single-user personal AI agent on your Cloudflare account |
| How do I install? | npx create-talorys@latest (Node.js 20.18+) |
| Which model? | Workers AI, @cf/zai-org/glm-4.7-flash |
| Cost? | Designed for Cloudflare's free plan; quotas apply |
| License? | MIT |
| Telemetry? | None, per the README |
| Main catch? | Depends on Cloudflare; the free AI allocation is limited |
What Talorys does
According to the README, Talorys gives you:
- Chat with streaming responses, Markdown and tool-activity indicators.
- Memory: durable personal facts and preferences you can view, edit and delete. Only the most relevant memories are sent to the model each turn.
- Tasks, notes and projects with full create, read, update and delete in the UI and from chat ("Add a task to review my project tomorrow").
- Automations: one-time and recurring reminders, daily task digests and optional AI routines, delivered to an in-app notification center. They run on Durable Object alarms, so nothing has to stay online.
- Single-user by design: no signup, no teams. The installer sets an owner password.
- Graceful degradation: tasks, notes, memories and reminders keep working if Workers AI is unavailable or your free quota is used up.
If you have followed the personal-assistant wave, this is a much smaller cousin of OpenClaw, the personal AI assistant or the Odysseus self-hosted workspace. Where those aim for broad integrations, Talorys deliberately stays narrow and cheap.
How it works under the hood
Durable Object SQLite storage holding the Talorys personal AI agent conversations, memories and tasks
The architecture section of the README describes a browser talking over HTTPS to a Cloudflare Pages site (a React app plus an API Pages Function). The function forwards requests over a service binding to a private Worker built with the Hono router. That Worker is deployed with workers_dev: false and preview_urls: false, so it has no public URL at all. Authentication and authorization happen in the Worker, not in the frontend.
The agent itself, TalorysAgent, is a Durable Object built on the Cloudflare Agents SDK. It holds a SQLite database with conversations, memories, tasks, notes, projects, automations, sessions, settings and usage. Chat uses Workers AI with streaming and tool calling, and alarms drive reminders. Responses stream as Server-Sent Events end to end.
Services used: Pages, Workers, Durable Objects (SQLite) and Workers AI. The README states it does not provision R2, D1, KV, Vectorize, AI Search, Workflows or any paid service.
This design echoes what Cloudflare itself has been shipping for agents, including Cloudflare OS for open-source agent platforms and the Sandbox SDK 1.0 for agents. For an agent that needs to hand off files and code safely, see also Cloudflare Artifacts, Git for agents.
Deploy it
The installer, per the README, checks Node.js, verifies your Cloudflare login (or opens the authorization page), lets you choose an account and agent name, asks for an owner password (hashed locally with PBKDF2-SHA256 and stored as a Cloudflare secret), generates a 256-bit session secret, deploys the Worker and the Pages project, and verifies the live deployment without running AI inference. It then prints your pages.dev URL and writes a talorys/ directory with a config file that contains no secrets.
Useful details:
- Interrupted installs resume if you rerun the command in the same place, with no duplicate resources.
- Non-interactive mode uses
TALORYS_OWNER_PASSWORD,--yesand--account-id. - If you use an API token instead of browser login, it needs Workers Scripts Edit, Cloudflare Pages Edit, Workers AI Read and Account Settings Read.
- Updates: run
npx create-talorys@latest updatefrom the talorys directory; the Durable Object namespace is never recreated and migrations are append-only.statusanddoctorcommands help with troubleshooting. - Forgot the password?
reset-passwordreplaces the secret and signs out every device.
For local development, npm run dev starts the Worker, Pages Function proxy and Vite UI, with a deterministic mock AI provider so no Cloudflare login is needed.
What "free" really means
A free-tier gift box beside a usage meter, showing how Cloudflare Workers AI quotas limit a free personal AI agent
The README is candid: Talorys fits the Workers Free plan but is "not unlimited free". Quotas for requests, Durable Object usage and the daily Workers AI allocation are set by Cloudflare and can change. When the AI allocation runs out, chat shows a clear message and resumes after the daily reset. On a paid plan, usage beyond included amounts is billed by Cloudflare.
Built-in guardrails (adjustable in Settings, AI) cap output tokens, context tokens (older history is summarized), tool calls and reasoning steps per request, AI requests per day, and scheduled AI runs per day. Simple reminders and task digests never use AI. A usage panel shows local estimates and links to the Cloudflare dashboard for exact numbers.
That last point matters, because on Hacker News one commenter asked what a "neuron" is. Cloudflare meters Workers AI in neurons, and a user mentioned seeing a 10,000-neurons-a-day free allocation. If you want a primer on how token and usage limits shape agent design, see our explainer on Gemini Notebook's flexible usage limits, and keep Cloudflare's billing docs open when testing.
What developers are saying
The discussion was mixed. These are commenters' reports, not verified facts.
- The author, rociiu, introduced it as a way to own and control a personal assistant without a subscription.
- One commenter, deanc, said this was their first time hearing about Workers AI and asked what a neuron is.
- Several readers disputed the "self-hosted" label. flufluflufluffy defined self-hosted as hosting it yourself, StrLght argued that relying on Cloudflare for everything isn't self-hosting, and quietFalcon said Durable Objects and KV bindings made it impossible to run off Cloudflare, so it is really "deploy it yourself."
- hung warned that they had been billed for confusing neuron usage when mixing the free AI tier with paid Workers and could not get support to explain it.
The fair reading: Talorys is self-owned, not portable. If lock-in is your concern, the same ideas can be rebuilt on a home server, as in our Odysseus guide.
Talorys versus the alternatives
The honest comparison is against three choices a builder has today. A hosted assistant such as a chatbot app is the easiest, but your memory lives in someone else's account and you pay monthly. A fully self-hosted stack on a home server gives you portability and any model you like, but you maintain the box, networking and backups. Talorys sits in the middle: no server to patch and no monthly bill on the free plan, at the price of tying your data to Cloudflare and one hosted model.
| Choice | Control | Upkeep | Typical cost |
|---|---|---|---|
| Hosted chat app | Low | None | Subscription |
| Home server stack | High | You | Hardware and power |
| Talorys on Cloudflare | Medium | Low (one update command) | Free plan within quotas |
Another difference is scope. Talorys ships a narrow feature set (chat, memory, tasks, notes, projects, reminders) and does not try to connect to your email, calendar or messaging apps. That limits convenience, but it also limits the blast radius if something goes wrong, which suits a first personal agent.
Ideas for extending it
Because the repo is a plain TypeScript monorepo with separate agent, web and shared packages, it is easy to fork. Natural experiments include swapping the Workers AI model for another provider behind the same tool-calling interface, adding a new tool such as a read-only calendar lookup, or changing the daily digest into a weekly review. Each of these touches the agent package and its tests, and the project ships unit, end-to-end and packaging test scripts you can run before redeploying. If you do extend it, keep the single-user assumption in mind: the authentication model is a shared owner password with managed sessions, not a multi-tenant design.
Privacy and security notes
The README says there is no telemetry, analytics or advertising code and that nothing is sent to the developers. It also points out that Cloudflare still processes your chat messages and relevant memories for inference, so review Cloudflare's privacy policy and Workers AI terms. There are published docs on the security model in the repo. As with any agent holding personal notes, treat the owner password seriously and use the session management under Settings, Security.
If you later give any personal agent tool access to other systems, put guardrails in front of risky actions; the explainx.ai team builds AgentBeam, an agent security platform designed to stop AI agents before they take dangerous actions.
Who should try it
Talorys suits developers who want a private to-do and notes assistant with scheduled nudges and don't mind Cloudflare as the substrate. It is a good template if you are learning Durable Objects, Agents SDK alarms or tool calling in a production-shaped project. It is not for you if you need multi-user teams, deep integrations, or a model other than the one configured, since the README names a single Workers AI model. Because the project is young, expect rough edges and check the issue tracker before trusting it with data you cannot back up. Do use the backup feature regularly.
Details reflect the repository README as of October 10, 2026.