100% Cloudflare. Always has been.

One network.
Everywhere on earth.

Pagayo runs entirely on Cloudflare. Every page, every API call, every database query, every payment webhook — handled in the data centre closest to your customer, in milliseconds, with no servers to manage and no maintenance windows to plan around.

Visit cloudflare.com ↗

300+

Cities running Pagayo

<50ms

From any major city

Origin servers to manage

100%

Cloudflare, end to end

The stack

Twelve Cloudflare services. One platform.

Pagayo uses Cloudflare top to bottom — compute, storage, security, routing, the lot. Here is the full set, and what each one does for you.

Workers Compute

Every API route, every page render, every webhook handler.
D1 Database

SQLite at the edge. One database per tenant, fully isolated.
KV Key-value

Hot reads of settings, navigation and cached lookups.
R2 Object

Product images, invoices, exports — no egress fees.
Queues Async

Background jobs: emails, webhooks, exports, retries.
Workflows Durable

Multi-step processes like tenant provisioning.
Pages Static

The marketing site you are reading right now.
DNS Routing

Tenant subdomains, custom hostnames, instant cutover.
Access Zero-trust

Platform admin protected without VPN or passwords.
WAF Security

Bot mitigation, rate limiting, managed rules.
Cache API Edge cache

GET responses served from the closest city.
SSL TLS

Automatic certificates for every tenant domain.

How it fits together

Six layers, one platform.

Compute, data, cache, async work, security, routing — every layer of Pagayo runs on a Cloudflare primitive. Here is what each one does.

01 Workers

Compute on the edge

Every request runs in the city it came from.

Pagayo runs as a fleet of Workers — small, focused, V8-isolated services that wake up in the data centre closest to your customer, handle the request in milliseconds, and go back to sleep. No virtual machines. No Kubernetes. No "scale-out" event to plan for. There are 300+ cities running Pagayo right now, and we never had to provision a single one.

Cold start in ~5ms, warm requests in under 1ms
Same Worker handles webshop, API, admin, POS
Service bindings connect Workers without leaving the edge

02 D1 · KV · R2

Data, close to the customer

Three storage layers, each for the job it is best at.

D1 holds the transactional truth — orders, products, customers — as SQLite databases with one per tenant for hard isolation. KV serves the things that change rarely and read often: settings, navigation, public lookups. R2 stores the heavy stuff — product images, invoices, exports — without ever charging egress fees. Together they replace the entire "database + cache + bucket + CDN" stack most platforms juggle.

D1: per-tenant SQLite, automatic global replication
KV: sub-10ms reads of hot configuration
R2: S3-compatible objects, zero egress cost

03 Cache API

Edge-first, always

Cache API → KV → D1. Never the other way around.

Every public GET in Pagayo follows the same order: try the Cache API first, then KV, then D1. The fast path serves a fully rendered response in single-digit milliseconds, anywhere on earth. The slow path still finishes inside the same data centre. The database is the last thing we touch — never the first.

Catalogue, product, brand and content pages pre-cached
Per-tenant cache keys for safe multi-tenant isolation
Surrogate keys for surgical, instant invalidation

04 Queues · Workflows

Async work, done right

For everything that should not block the customer.

Order confirmation emails, webhook deliveries, exports, retries, scheduled reports — none of it happens inside the request that triggered it. Queues take messages off the hot path; Workflows run the durable, multi-step processes (like provisioning a brand-new tenant with its own D1 database, KV namespaces, DNS records and SSL certificates) that need to survive a deploy.

Queues: at-least-once delivery, retries, dead-letter queues
Workflows: durable execution across hours or days
Cron triggers for scheduled jobs across all tenants

05 Access · WAF · SSL

Security by default

The hardest network on the internet, free of charge.

The platform admin sits behind Cloudflare Access — no VPN, no shared passwords, no panic when someone leaves. The WAF mitigates bots, brute-force, and the OWASP top ten before traffic ever reaches a Worker. Every tenant — every custom domain — gets an SSL certificate, automatically, the moment they're provisioned. Pagayo never sees a plaintext request.

Access for zero-trust admin authentication
WAF + rate limiting on every public endpoint
Automatic SSL for every custom hostname

06 DNS · Pages · Custom Hostnames

Routing & domains

A new shop, on a new domain, in seconds.

Every tenant lives on its own subdomain ({slug}.pagayo.app) the moment they sign up — DNS, SSL, routing, everything. When they're ready, they bring their own domain and Cloudflare Custom Hostnames handles the cutover without downtime. The marketing site you're reading right now is served by Cloudflare Pages from the same network.

{slug}.pagayo.app live in under a minute
Custom hostnames with zero-downtime cutover
Pages for static marketing, Workers for everything else

Why this matters for you

It's not about the infrastructure.

You will never need to touch any of this. You will never read a status page, file a support ticket about a region outage, or plan a migration. That is the whole point of standing on Cloudflare: the boring parts of running a platform on the internet are taken care of, by the people who do it best.

What you get instead is a shop that loads instantly anywhere on earth, a checkout that doesn't go down on Black Friday, an admin that's protected without you thinking about it, and a platform that gets faster every week without you doing anything.

That's what "100% Cloudflare" really buys.

Start selling today.
Grow with the platform.

Free to start. All features included. Yours to leave whenever you want — most never do.

Start Free → Compare Plans

Have an idea, a question, or a feature you wish existed? Get in touch — we listen.

One network. Everywhere on earth.