[ Edge Proxy ]

Fast, protected, edge-distributed apps

Edge Proxy brings your traffic closer to users, cuts latency and operational complexity, and adds security and control directly at the edge — without building parallel stacks.

An edge layer ready for real traffic

Edge Proxy is the layer that puts control, caching and protection between your users and the origin. Instead of serving everything straight from the backend, traffic is distributed across a global network that cuts physical distance, absorbs spikes and simplifies operations.

A global network to serve closer

Traffic is routed to the network point closest to the end user. Less physical distance means faster responses, a more stable experience and less load on your central infrastructure.
  • Global coverage
    The network covers the main markets worldwide, with nodes also in regions usually overlooked by traditional providers.
  • To the fastest node
    Every request is routed to the network point responding fastest at that moment, not the one that's geographically closest on paper.
  • A shared infrastructure
    The edge network is shared across all JAMflow services. Fewer stacks to manage, more consistency across the performance of content, images and APIs.

119+ PoPs across 77 countries.

The network that distributes your traffic covers the main markets in Europe, North America and Asia Pacific, with nodes also in Africa and Latin America — areas often ignored by traditional cloud providers.

It's not just about having more servers: every request is routed to the node that delivers the fastest response at that moment, not the one that's geographically closest on paper.

See the full map of our network

Global Cache to cut origin calls

Distributed caching serves ready-made content from the edge instead of rebuilding it from the origin every time. Less backend load, faster responses, more stable behaviour during spikes.
  • Configurable cache for every route
    Static content, marketing pages and assets are cached and served quickly. Authenticated areas and APIs stay dynamic with no extra configuration.
  • Content shared across the edge network
    Content that can be cached is stored and shared across the edge network. Fewer duplicate requests to the backend, more stable timings for users.
  • Cache refreshed at the right moment
    When content changes, the cache is updated in a controlled way. No global reset, no risk of serving stale data longer than necessary.

Content is built once and served everywhere.

Traditional caching is local to the instance: if the backend scales to multiple replicas, each one starts from scratch. With Global Cache, ready-made content is distributed across the whole edge network and served from the node closest to the user, without going back to the origin.

Combined with JAMlabs, prerendered Nuxt pages are stored directly on the edge at deploy time, so the first user doesn't pay the cost of the first render.

Edge protection against anomalous traffic

Edge Proxy intercepts malicious traffic before it reaches your backend. This reduces operational risk, takes load off origin servers and keeps the service stable even under attack.
  • Protection before the origin
    Malicious traffic is intercepted and blocked on the edge network, before it reaches your backend. Origin servers only receive legitimate requests.
  • Control over anomalous traffic
    Excessive requests from the same user or from automated patterns are blocked before they can degrade the service for everyone else.
  • Stable uptime even under attack
    Distributed protection ensures that an attack concentrated on a single node does not affect the global availability of the service.

Protection happens before the origin, not after.

An attack that hits the backend directly consumes compute just to be analysed. With edge-level protection, filtering happens on the distributed network: only clean traffic reaches your servers.

This applies to the subtler patterns too: slow requests, application-level flooding and endpoint abuse are identified and blocked before they affect service availability.

Native integration with Nuxt and Nitro

Edge Proxy doesn't require configuration separate from your Nuxt project. Through JAMlabs, caching, routing and protection are managed alongside your application code, without adding operational complexity for the team.
  • A single configuration point
    Everything about the edge infrastructure lives in the Nuxt project, not in separate consoles. The team has a single source of truth for how the system behaves.
  • Works with Nuxt without changes
    If your project already uses Nuxt, the edge integration follows the same rules you have already defined. No refactor, no double configuration.
  • Edge updated on every deploy
    When you deploy, the edge configuration is updated automatically along with the application. Nothing to do manually, nothing to forget.

A single configuration point for the entire edge infrastructure.

Instead of managing separate dashboards for cache, CDN, DNS and protection, with JAMlabs all edge configuration lives in the application repository and is versioned like code.

The team works from a single mental model: no external console, no manual syncing between what is configured in the infrastructure and what the code expects.

Intelligent DNS with security and routing

Edge Proxy's DNS doesn't just resolve domain names: it handles security, geographic routing and optimisation toward the fastest destination. More control, less manual configuration.
  • More secure DNS
    DNSSEC adds cryptographic security to DNS records, preventing traffic from being redirected to unauthorised destinations.
  • Geographic routing
    Requests are directed to the geographically closest destination, reducing latency without the user having to do anything.
  • To the fastest server
    Regardless of geographic location, requests are directed to the server responding fastest at that moment.

DNS as part of the infrastructure, not just an address book.

Traditional DNS resolution is static: each name points to a fixed IP. With GeoRouting and Latency Routing, the destination is chosen based on where the user is and which servers are responding fastest at that moment.

DNSSEC adds a layer of cryptographic security to DNS records, preventing spoofing and cache-poisoning attacks that can redirect traffic to unauthorised destinations.

Less complexity, more performance

Edge Proxy makes sense when you want to unite delivery, cache, routing and protection in a single operational layer. Instead of assembling separate pieces, you give the team one clear place to govern traffic.
  • Faster responses
    Traffic travels shorter paths and is served from the closest point. Users get faster responses, wherever they are.
  • Less load on the origin
    The edge network handles most requests without touching your backend. Origin servers work less and stay stable even during traffic spikes.
  • More robust infrastructure
    Protection, caching and routing are already included and active. You don't have to assemble separate solutions to cover the basics of security and distribution.
  • Less operational complexity
    A single layer to configure and maintain instead of several separate tools. The team has a single source of truth for the entire edge infrastructure.

When it really matters

Edge Proxy is built for projects that need global performance, protection from anomalous traffic and intelligent routing, without adding operational complexity for the team.
  • Landing pages and marketing sites
    High-traffic pages served directly from the edge. Fast loading even during spikes, with no overhead on the backend.
  • Nuxt apps with global content
    Nuxt applications distributed at global scale benefit from the edge network with no extra configuration beyond what you already use with JAMlabs.
  • Products with login and mixed content
    Authenticated areas stay dynamic and private. Public areas are served quickly from the cache. The system tells the two apart without manual configuration.
  • Multi-region platforms
    Each region's traffic is directed to the closest infrastructure. If something goes wrong, the system adapts automatically with no manual intervention.
  • Projects with intelligent DNS and failover
    Secure DNS, intelligent routing and automatic failover in a single configuration. Less risk, less latency, fewer manual operations when something goes wrong.
  • Caching and protection without separate stacks
    Instead of wiring up a CDN, DDoS protection and DNS separately, Edge Proxy brings them together into a single service configurable with JAMlabs.

Frequently asked questions

Everything you need to know about Edge Proxy.

Want to bring traffic closer to your users?

We can shape Edge Proxy on your Nuxt/Nitro infrastructure, starting from caching, DNS and protection, and figure out together which parts to use right away and which to keep as a next step.