One site, many handlers

A domain on CloudForge is served by an ordered set of rules: this path from the page builder, that one from your files, another from your own application. Access is enforced on the server, never in a script.

What you manage

Decide where each path goes

A default handler - builder, static files or forward - and rules by path prefix. Each rule says who may see it: everyone, signed-in users, members of your site, or a group.

  • Redirects (301 / 302) and proxies
  • Members-only paths without code
  • Proxy targets reviewed before they serve
  • Reserved paths always stay the platform's

Website traffic, measured properly

Captured from the edge for every site - static, builder or your own app - and enriched by an optional first-party beacon. No cookies by default.

Sessions, pages, sources

Visitors, pageviews, landing and exit pages, channels (search, social, referral, direct), campaigns.

People, not bots

Verified crawlers, fake crawlers, data-centre traffic and probes are classified and kept out of your figures.

Where and on what

Country and city, device, browser, operating system, screen size, language.

Live view

Who is on the site right now, which pages, from where.

Addresses, your way

IP addresses stored, masked or hashed - your choice - with a retention period you set. POPIA in mind.

Events and vitals

Scroll depth, outbound clicks, downloads, form submissions, Web Vitals, and your own events.

Questions people ask

See it with your own site

Tell us what you have. Most sites are live on CloudForge within a day.