Dashboard

Your websites

Loading profile...

Active & in progress

Website status

Each card shows the current step and what to do next. Deleted websites move to History below.

Trial

Free trial usage

Try Flare53 free for up to 3 months or 100GB total data transfer, whichever comes first.

Usage meter will show real transfer after metering is enabled. No automatic paid charge without choosing a paid plan.

Performance proof

Before vs after

Run a website checkup before setup. After Flare53 is active, compare response time, cache hit signal, and delivery usage.

Run checkup
Origin protection

Block bypass traffic

Visitors should use your public website domain through Flare53. Direct access to the origin should be restricted where possible.

Learn the flow
Add another website

Start a new Flare53 setup

Create a setup under your logged-in account. Your email is taken from login automatically.

Important: the public website domain and origin URL must be different. Example: public is www.test.com, origin is https://origin.test.com.
Origin safety: your origin must be public, reachable, and not an internal/private address such as localhost, 127.0.0.1, or 192.168.x.x. Flare53 checks this before creating the setup.
Simple meaning: visitors use the public website domain. Flare53 uses the origin URL behind the scenes to fetch your website.
Setup guide

What you need to prepare

1. Public website domain

This is what visitors type, for example www.customer.com. After SSL is ready, this DNS record points to Flare53.

2. Origin URL

This is where your real website is hosted, for example https://origin.customer.com. It must be different from the public website domain.

3. DNS access

Flare53 will show CNAME records. Most DNS providers need the short host/name. Use the full host/name only if your provider asks for it.

4. Origin protection later

Do not block the origin before setup is active. After testing, protect the origin using your hosting firewall, server rules, AWS security group, or private S3 origin method.

Ask your hosting provider if unsure: “Can I restrict direct origin access and only allow requests that come through Flare53 or contain a trusted HTTP header?”
Account settings

Delete my Flare53 account

You can delete your login account only after all websites under this account are deleted. This prevents orphaned CloudFront distributions and SSL certificates.

Before account deletion: remove all active websites first and wait until their status becomes deleted.