Register with Cloudflare

Saavo runs on Cloudflare Workers. During local development, you can use Wrangler to simulate D1, KV, R2, Queues, and Durable Objects. You will need real Cloudflare resources when you deploy a preview or go live.

Understand users and accounts

Cloudflare distinguishes between a user and an account:

A user can belong to multiple Cloudflare accounts. You must select the same account whenever you create the Worker and its resources later. The Cloudflare documentation explains these concepts in more detail.

Sign up for Cloudflare

Choose an email address before signing up. In addition to signing in, you will use it to receive usage alerts, security notifications, and account recovery emails, so an address you check regularly is best. For a company or team project, use an address the organization can continue to manage. Invite other members after registration instead of sharing a password.

1. Open the Cloudflare sign-up page.
2. Enter your email address and password.
3. Read the terms and notices on the page, then click Create account once you have checked them.
4. After registration, the browser opens the Cloudflare Dashboard.

New accounts have a default name such as <your-email>'s Account. You can keep it for now for a personal project. If you manage multiple projects, we recommend changing it early to a recognizable project or team name to avoid selecting the wrong account during deployment.

Verify your email address

Cloudflare automatically sends a verification email after registration. Open the verification link in the email and sign in to Cloudflare again to complete verification.

If the email does not arrive:

1. Check your spam folder and email filtering rules.
2. Sign in to the Cloudflare Dashboard, click the user icon in the upper-right corner, and open Profile from the user menu.
3. Find Email Address and click Send verification email to resend it.

Once verification is complete, verified appears next to your email address. If you have opened the link but the status has not changed, try another browser or a private window, then resend the verification email.

Confirm which account will own the resources

In the Dashboard, check which Cloudflare account is selected. If you see only one account named after your email address, you can use it for the remaining steps. If you belong to multiple accounts, decide where Saavo should be deployed and note the account name.

To rename an account, open its Configurations page and click Change Name under Account Name. The name is only a label. Changing it does not change the Account ID or affect existing resources.

The free plan is sufficient for local development and a workers.dev preview. You can skip prompts to add a domain, choose other products, or enter billing information for now. When you go live, decide whether to upgrade based on actual usage.

Enable two-factor authentication (recommended, optional)

A compromised Cloudflare user could affect your domains, production data, and deployment permissions. After verifying your email address, we recommend enabling two-factor authentication (2FA) immediately:

1. Open My Profile → Authentication.
2. Add an authenticator app or security key under Two-Factor Authentication.
3. Follow the instructions to save your backup recovery codes in a secure location, such as a password manager.

Recovery codes are only needed when you cannot use your authenticator. Do not store them with your account password in the same unencrypted file. See the Cloudflare two-factor authentication documentation for setup instructions.

Enable R2

Cloudflare R2 is an object storage service. Saavo uses it by default for uploaded files such as avatars, support ticket images, and notification images. Before creating an R2 bucket, you must enable R2 in the Cloudflare account where you plan to deploy Saavo.

Enabling R2 adds an R2 subscription to the current account. It does not create a bucket, API token, or access key. Follow these steps:

1. Open the Cloudflare Dashboard and switch to the account where you plan to deploy Saavo.
2. Open Storage & databases → R2 → Overview in the sidebar.
3. If the page already shows a bucket list or a Create bucket button, R2 is enabled for this account. You can skip to the next section.
4. If the page prompts you to enable R2, click the activation button and follow the checkout instructions. Cloudflare may first ask for billing information and a payment method.
5. Return to the R2 Overview page. If you can see Create bucket, R2 is ready to use.

Enabling R2 requires adding a payment method. If the current account does not have one, Cloudflare will ask you to add it first.

There is an extra page in this flow. This appears to be the default process of adding a payment method before enabling R2. Click Continue to R2.

If there are no issues with your card, activation should succeed. You will then be redirected to the R2 Overview page. The Create bucket button confirms that R2 is ready to use.

R2 charges for storage and operations, with a monthly free allowance. Usage beyond that allowance incurs charges. The free allowance applies only to Standard storage, not Infrequent Access. Allowances and prices may change. See the official R2 pricing for current details.

If a team member cannot see the activation button or complete checkout, their role usually lacks permission to manage both subscriptions and payment methods. Ask the account's Super Administrator to enable R2. Do not switch to another account to continue.

Sign in to Wrangler after installing the project (optional)

Wrangler is installed with Saavo's project dependencies, so you do not need a separate global installation. If you are preparing your environment in documentation order, you can skip this step for now. After downloading the project and running npm install, return to the project root and run:

npx wrangler login

Wrangler opens your browser and requests access to Cloudflare through OAuth. Make sure the browser is signed in as the user you prepared earlier, review the authorization page, and allow access. Once the terminal confirms that sign-in succeeded, run:

npx wrangler whoami

The output should include your sign-in email address and the Cloudflare accounts and Account IDs that this user can access. When configuring resources later, use the Account ID to confirm the target account. Do not rely on the account name alone.

At this point, confirm that your email address is verified, you can access the Cloudflare account where Saavo will be deployed, and R2 is enabled for that account. After installing the project, use Wrangler for a final authorization check.

Next: Install Git.