Cloudflare deployment

Deploy Linketry with the right amount of control.

Start in Cloudflare when you want a fast dashboard launch, or use the reviewed repository workflow when you need an auditable resource plan. Both paths keep your account and data in your hands.

Launch on Cloudflare Read self-hosting guide

A · Cloudflare Quick Deploy

Start from the Cloudflare dashboard.

The official launcher opens Cloudflare's authenticated repository-deployment flow. It is the fastest way to begin a new installation from your own account.

1
Sign in to the Cloudflare account that will own the application.
2
Review the repository and choose the deployment target before creating it.
3
Complete the required D1, KV, Pages/Admin and private Admin-token choices in the guided setup.

Open Cloudflare deploy

A secure first install cannot be configuration-free.

A launcher cannot safely choose your account, custom hostname, D1/KV bindings, or private Admin secret. Linketry never invents those values or sends them through a public page.

B · Reviewed repository workflow

Provision exactly what you approve.

Fork the repository and use Linketry's maintained dry runs. The scripts show the D1/KV plan and require an exact confirmation phrase before any Cloudflare or GitHub write.

1
Fork Linketry into the GitHub account that will own future upgrades.
2
Run the bootstrap and repository configuration dry runs.
3
Review the plan, confirm the exact phrase, then start the protected workflow.

Guarded assistant prompt

Help me deploy Linketry from my fork to my own Cloudflare account.

The prompt does not ask you to paste a token into chat, source files, logs, or command arguments.

Open full repository guide ↗

Before any write

Deploy Linketry with the right amount of control.

Start from the Cloudflare dashboard.

Provision exactly what you approve.

Read the contract, then deploy.

Deployment safety model

Fresh self-hosting

Backup and recovery