Talivia Docs
Talivia Docs
HomeDashboard
IntroductionInstallationTeamGetting updates
Self-hostingInstall TaliviaUpdatingCustom domainOwner accountLicense and transfersCloudflare and backupsUninstallTroubleshooting
Integrations
AI agents and MCPllms.txtllms-full.txt
Self-hosting

Cloudflare and backups

Understand hosting, storage and backups for your own installation.

View Markdown

Your Cloudflare account owns the Talivia Worker and D1 database. The default names are talivia and talivia-data. The Worker serves the dashboard, API and tracking script; D1 stores the application data. A separate PostgreSQL or Redis service is not required.

Hosting limits

The Talivia Lifetime payment covers the application license. Cloudflare manages hosting allowances and usage charges separately. The installer does not buy or upgrade a Cloudflare plan.

Review the current Workers limits and D1 limits for your account. Monitor Worker requests, CPU usage and D1 storage in Cloudflare as traffic grows. A free plan has limits; the Lifetime license does not remove them.

Keep a backup

Before deleting an installation or making manual database changes, export its D1 database using Cloudflare's import and export instructions. Select the actual database bound to your Worker, especially if you installed using another name.

Updating Talivia keeps the existing database. A license transfer also leaves it in place. Deleting a Worker alone does not delete its separate D1 database; deleting D1 can remove both analytics data and owner credentials.

A backup is not a second licensed installation. To move an active installation, follow license transfers.

License and transfers

Find your license and manage its one active installation.

Uninstall

Remove your own installation and manage the remaining database and license.