Ki-Ki

What Cloudflare Workers actually are

A Worker is essentially a small script that runs on Cloudflare whenever a matching request comes in. It can read headers, cookies and request bodies, look at the route, make decisions and optionally send data to other services. All of this happens before your origin sees anything.

• Runs at the edge logic happens on Cloudflare infrastructure, not your shared hosting account.
• Fast to respond decisions are made close to the visitor, which keeps latency low.
• Targeted Workers can be attached to specific routes, not the entire site.
• Flexible they can talk to APIs, write logs or alter requests in flight.

Used carefully, Workers give you the benefits of a custom back end without dragging a full framework around.

How Workers power fingerprinting and Edge Tracker

The clearest example of Workers in use on Ki-Ki projects is the fingerprinting and Edge Tracker system. That page walks through the detail. Here is how Workers sit underneath it.

Collecting traits at the edge

A Worker receives the request and pairs browser traits, headers and timing information with a stable identifier. The fingerprint is assembled before the request reaches your origin, which keeps the heavy lifting away from your server.

Turning visits into evidence grade records

Workers attach fingerprints to requests and send structured payloads into logging channels, often via webhooks. That is how Edge Tracker can tell when the same device keeps returning under different IPs or user agents, and how it builds a clean audit trail.

Profiling patterns rather than single hits

The same Worker logic can group fingerprints by network, organisation or behaviour, so repeated probes from the same source stand out. This gives you a higher level view of who is watching your site and how persistent they are.

Other ways Ki-Ki uses Workers

Fingerprinting is one example. Workers can also support quieter jobs that still make a real difference.

• Custom routing send certain paths to different back ends or static assets without rewriting everything on the host.
• Header and cookie handling add or strip headers, normalise cookies or tag requests for later analysis.
• Bot and scraper handling add extra checks for suspicious behaviour that sit alongside normal firewall rules.
• Lightweight APIs serve small pieces of dynamic content from Workers without needing a full application server.

The aim is always the same. Keep your main site simple and static where possible, and push any required logic into Cloudflare where it is easier to control and observe.

Why small organisations should care about Workers

Most small organisations are told they need a full application framework when in reality a static site with a handful of Workers is enough. This keeps costs down and avoids the maintenance overhead of a complex stack.

• Less to patch fewer moving parts on your origin mean fewer places for exploits to land.
• More visibility edge logs and Worker outputs give you better insight into who is doing what.
• Controlled complexity you add logic only where it helps, instead of by default.
• Scales cleanly Cloudflare handles the load so you are less exposed to traffic spikes.

Ki-Ki designs Worker use around your actual risk and goals, not around a checklist of features.

Want to put Workers to use without breaking your stack?

If you like the idea of the fingerprinting and Edge Tracker approach on the fingerprinting page, or you have specific logic you want to run at the edge, Ki-Ki can design and deploy the Workers for you and walk you through what they are doing in plain English.

Short, focused pieces of work that add real capability without turning your infrastructure into a science project.