Skip to main content
Talk to SalesGet Started
Talk to Sales
Get Started

[AKSELA · DYNAMIC & API ACCELERATION]

Dynamic content,at edge speed.

Aksela caches personalized pages, API responses and live data safely at Medianova’s edge - so your origin works less and your users wait less.

Talk to an engineerExplore the docs
Animation: a campaign starts and requests to /api/prices climb. With Aksela on, the Medianova edge keeps the response for a few seconds; until the time runs out every request is answered from the edge, then a single request fetches the fresh response from the origin. The origin’s load stays low even at the peak. With Aksela off every request goes to the origin, its load climbs and users wait.

THE PROBLEM

Dynamic traffic usually goes straight to your origin.

Static files are easy to cache. Pages and APIs that change are where users actually wait.

  • Peaks land on your servers

    Campaigns, launches and busy hours hit the origin, not the edge.

  • Every request waits

    Time to first byte grows with distance from the origin and with its load.

  • Scaling gets expensive

    Adding servers - vertically or horizontally - becomes the only answer, and it costs more each time.

HOW IT WORKS

Cache for seconds. Stay fresh.

Microcaching keeps a response at the edge for a few seconds - enough to absorb a spike, short enough that users always see current data.

  • No cache

    Requests go straight to the origin for the paths that must always be live.

  • Custom cache

    Cache responses for seconds or minutes, with your own TTL for each path.

  • Full cache

    Serve complete pages from the edge when the content is the same for every visitor.

PAGES AND APIS

One engine for pages and APIs.

Aksela accelerates dynamic HTML and API responses with the same rules - and leaves alone what must never be cached.

  • Dynamic pages

    HTML that changes often but not on every request.

    • Product catalogs
    • Search results
    • CMS and news pages
    • Customer dashboards

  • API responses

    Read-heavy endpoints that many clients ask for at once.

    • REST and GraphQL APIs
    • Pricing and exchange rates
    • Search suggestions
    • Configuration endpoints

  • Always passed through

    Personal and transactional traffic goes to your origin, every time.

    • Logins and sessions
    • Checkout and payments
    • User-specific API calls

CUSTOMER STORY

ebebek cut time to first byte by 60%.

Lower time to first byte
60%
Less origin CPU usage
63%
“After switching to Medianova’s CDN technologies, including Aksela, our TTFB and CPU usage drastically decreased, affirming a much-improved user experience for our shoppers.”
Alper Tekin · IT Director, ebebek

CONTROL

You decide what’s cached.

Every rule is set per path, from the Medianova Control Panel.

  • Page Rules

    Give each path of your application its own caching behavior.

  • Query string caching

    Choose which parameters create a separate cache entry.

  • Browser cache rules

    Control how long browsers keep dynamic responses.

  • Edge cache expiration

    Set how long each response stays at the edge.

  • Instant purge

    Invalidate cached content across the network the moment it changes.

  • Compression

    Brotli and HTTP/2 keep responses small on the way to the user.

VISIBILITY

See your cache hit ratio in real time.

Tune your rules with real data from the edge, powered by Edgesight.

PROTECTION

Fast for users, closed to abuse.

Dynamic sites and APIs are what attackers go after. Aksela runs on the same edge as Medianova’s security layer.

ONE PLATFORM

Works with the rest of the edge.

GET STARTED

Live in four steps.

  1. 01 / 04

    Create a dynamic resource

    Add a Dynamic CDN resource in the Medianova Control Panel.

  2. 02 / 04

    Point your domain

    Point your website’s domain to Medianova with a CNAME record - or ANAME / ALIAS for a root domain.

  3. 03 / 04

    Set your rules

    Choose what to cache, for how long, path by path.

  4. 04 / 04

    Watch it in Edgesight

    Follow cache hit ratio and origin load as you tune.

Dynamic content, at edge speed.

Talk to an engineer about your pages, your APIs and your peak traffic.

Talk to an engineer