Talorys puts a single-user AI assistant in your Cloudflare account, with chat, memories, tasks, notes and scheduled reminders. If you are comfortable deploying Cloudflare services, this guide takes you from the maintainer's install command to checks you can perform yourself: login, a reminder and a backup. It follows the maintainer's deployment instructions and README; BIG CHANGE has not installed or tested Talorys.
Your browser opens a Cloudflare Pages site, and its /api/* requests pass through a Pages Function to a Worker over a service binding. The maintainer configures that Worker without a public Worker URL. Talorys stores its data in a SQLite-backed Durable Object and uses Cloudflare Workers AI for chat. The documented model is @cf/zai-org/glm-4.7-flash. The Pages address remains reachable on the internet; the owner password protects the data behind it. Architecture and security documentation describe this design.
Before you deploy
You need Node.js 20.18 or newer, a Cloudflare account in which you can deploy Workers and Pages, and a password you will use to sign in. The installer includes Wrangler and uses its browser OAuth flow for Cloudflare access. If you use an API token instead, the maintainer lists Workers Scripts:Edit, Cloudflare Pages:Edit, Workers AI:Read and Account Settings:Read permissions. Choose an account you control and review the Cloudflare authorization screen before granting access. The interactive route below keeps the owner password out of a shell command and its history.
This is a deployment into your Cloudflare account, so check its current plan and usage limits before running the installer. The maintainer says the installer does not enable paid features on its own. Existing account settings and other usage still matter.
Install and check the result
- In a terminal, move to a directory where you want to keep the generated
talorys/folder. Run the maintainer's one-command installer:
npx create-talorys@latest- Follow its prompts. Sign in to Cloudflare through the browser OAuth page if asked, select the intended account, choose an agent name, and enter an owner password at the hidden prompt. The installer checks the Node version, deploys the private Worker and Pages project, and stores a password hash and session secret as Cloudflare secrets. Keep the generated
talorys/directory; itstalorys.jsonrecords the installation and resource names without secrets and is used for later updates. - Wait for the installer to finish its deployment checks and print the actual HTTPS
pages.devURL returned by Cloudflare. According to the maintainer, these checks cover the frontend, authentication endpoint, rejection of an unauthenticated request and storage health. They do not run an AI inference. An installer success therefore shows the deployment passed those checks; it does not show that chat or a scheduled reminder has succeeded. - Open the printed URL and sign in with your owner password. Confirm that the app loads and you can open its tasks and automations areas. Create a one-time reminder with a harmless message and a time you can check soon, using your intended timezone. Confirm that it appears in Automations, then check the in-app notification center after the scheduled time. This is your own functional check of scheduling and delivery, separate from the installer's health checks. The maintainer says reminders use Durable Object alarms and do not require an AI request.
- In Settings → Privacy, use Download backup and keep the resulting
talorys-backup.jsonsomewhere you control. The maintainer says it includes conversations, memories, tasks, notes, projects, settings and automations, while excluding sessions and credentials. The documented import validates the file and merges it in one transaction; it is the recovery path for the exported app data. Protect the backup as personal data. Exporting it does not test an import, so consider the backup unproven until you have checked a restore in an installation you control.
Your deployment check is complete when the Pages URL loads, your owner login works, the reminder appears in the notification center at the chosen time, and you can locate the exported backup. BIG CHANGE has not observed those results.
If setup or access fails
Keep the original talorys/ directory. If installation stops midway, run the same installer command again from its parent directory. The maintainer says the manifest lets it resume using the existing resource names, without deleting data. A new pages.dev address can take a few minutes to pass health checks; a later rerun may finish verification. For permission errors, check that you selected the intended Cloudflare account and have the listed access. From the generated directory, the documented maintenance command is:
npx create-talorys@latest doctorThe README also documents status and update. If you forget the owner password, run npx create-talorys@latest reset-password from talorys/; the maintainer says that replaces its secret and signs out every device. A login lockout after failed attempts may clear after 15 minutes, according to the maintainer's troubleshooting table. Read its troubleshooting guidance before changing Cloudflare resources manually.
Privacy, authority and cost
The maintainer describes Talorys as single-user, with server-side authorization, HMAC-protected session records, no public Worker URL and no telemetry to the developer. Those are documented design claims, not an independent security audit. The Pages login remains publicly reachable. Cloudflare processes chat prompts and relevant memories when its Workers AI model runs; keeping storage in your account does not keep inference on your own device. The maintainer says scheduled AI routines receive read-only tools, while ordinary reminders and task digests are deterministic. Avoid putting information into chat that you would not send to Cloudflare for inference, and review a suggested task or memory change before relying on it.
Talorys has no separate service fee stated in the maintainer's README, but Cloudflare has account-level limits. As of Cloudflare's October 9 Workers AI pricing page, Workers Free includes 10,000 Neurons per day for AI use, resetting at 00:00 UTC; more usage requires Workers Paid and is charged at $0.011 per 1,000 Neurons above that daily allocation. Cloudflare lists glm-4.7-flash at unit prices of $0.0605 per million input tokens and $0.40 per million output tokens, while its billing and free allocation use Neurons. Those unit figures alone do not establish how many conversations fit in a free day. Workers and Durable Objects have their own request, compute and storage limits; Pages Functions are billed as Workers. Check the Cloudflare dashboard for actual usage. The maintainer says tasks, notes and reminders continue when the AI allocation is exhausted, while chat waits for the quota reset.
The big change
- Talorys packages a personal assistant into an install that places the web app, private Worker, SQLite-backed storage and scheduling in the user's Cloudflare account. The maintainer's installer verifies access, authentication rejection and storage health before returning a URL.
- A technically capable solo user can check the remaining gap directly: sign in, save a one-time reminder, observe its notification and export the app data. That check matters because the installer's health probe does not run chat inference or prove reminder delivery.
- Account ownership gives the user control over deployment and stored data, while Cloudflare still runs the infrastructure and processes prompts sent to Workers AI. The free allocation has daily limits, and paid-account overage can be billed.
Sources & further reading
The Talorys README describes the product, one-command install, backup and maintenance commands. Its deployment guide specifies installer steps, permission needs and recovery behavior. The maintainer's architecture and security documents explain the request path and stated protections; neither is an independent audit. Cloudflare's Workers AI pricing, model listing and Workers pricing establish the quoted limits and rates. The maintainer's main repository revision identified for this assignment is 4aa1db8f997ff034a84b1ff9256b67abfa4f4b2b (October 10, 2026). The @latest installer and platform pricing can change after publication.
