Website · Documentation · Pricing

Cost calculator

Your traffic

Choose a workload. We’ll estimate traffic and requests for you.

Estimated monthly costs

USD per month, before tax. Load balancing and unpriced extras are excluded.

What’s included?

Estimates cover cacheable content. Origin and optional services are added only when you enter their rates. Plans differ in features and coverage; check their terms before buying.

Advanced settings
Split traffic between regions

Percentages must total 100%. The same split applies to bytes and requests. CloudFront charges by serving edge location; this is an approximation. Shared free allowances are allocated proportionally.

Origin and optional services

Paid tiers start with this workload; estimates do not include other account traffic. Enter your own effective rates after origin allowances. Reads use request misses; egress uses byte fill. Functions assume one invocation per viewer request. Zero leaves an extra out of the estimate; it does not mean your origin is free.

Compare a quote you received

This is your quote, not a published provider price. Use an effective rate for the selected traffic mix; tiers, included usage and commitments need to be reflected in your inputs. Sharing a scenario includes your quote details.

Presets are starting assumptions, not measured traffic. Video assumes one rendition and segment GETs; playlists, retries and extra audio tracks add requests. Fill is a byte ratio, not a request cache-hit rate. GB = 1 billion bytes; Google bills GiB = 1,073,741,824 bytes; CloudFront estimates use binary GB as a billing assumption.

Overview

Medianova is a CDN and cloud-security provider founded in 2005, with its central office in Istanbul. It emphasizes delivery across Europe, the Middle East and Africa while offering global coverage.

  • Web and APIs: static caching and dynamic-content acceleration.
  • Media: large-file delivery, live streaming and video on demand.
  • Security: application protection and traffic controls at the edge.

Select the resource type around the workload; available settings differ between static, dynamic and streaming resources.

Network

The network page advertises 55 global PoPs and names 33 cities across six geographic groups. The map shows those published city locations where coordinates can be resolved.

Markers are approximate city centers, not facility addresses or a complete inventory of all advertised PoPs. Test latency and throughput for your audience, particularly outside the service’s EMEA focus.

Published CDN cities

Approximate city centers from the published city list; not all 55 advertised PoP facilities.

IstanbulAnkaraMarseilleFrankfurtBucharestRiyadhJeddahDubaiDohaKuwait CityBaghdadBeirutRahim Yar KhanLahoreSingaporeManamaBakuCairoGizaLagosJohannesburgAlgiersDenverLos AngelesSeattleMiamiTorontoSão PauloLimaBogotaSydney
Cities

Istanbul, Ankara, Marseille, Frankfurt, Bucharest, Riyadh, Jeddah, Dubai, Doha, Kuwait City, Baghdad, Beirut, Rahim Yar Khan, Lahore, Singapore, Manama, Baku, Cairo, Giza, Lagos, Johannesburg, Algiers, Denver, Los Angeles, Seattle, Miami, Toronto, São Paulo, Lima, Bogota, Sydney

Listed without a marker: Fujairah, Ashburn.

Features

FeatureSupported
Web application firewall✓ Supported
Bot protection✓ Supported
DDoS protection✓ Supported
Rate limiting◐ Partial
HTTP/3 (QUIC)Not listed
TLS 1.3✓ Supported
Tiered cachingNot listed
Origin shield✓ Supported
Instant cache purge◐ Partial
Serve stale while refreshing✓ Supported
Serve stale on origin errors✓ Supported
Image optimization✓ Supported
On-demand video✓ Supported
Live video✓ Supported
Digital rights managementNot listed
HLS / DASH packaging✓ Supported
WebSocketsNot listed
Signed URLs✓ Supported
Edge computeNot listed
Edge functionsNot listed
Key-value storageNot listed
Configuration API✓ Supported
Real-time logs◐ Partial
Log export✓ Supported
Terraform providerNot listed

✓ Supported · Partial: limited or separate-product support · ✗ Not supported · Not listed: unconfirmed. Some features need a separate product or plan.

Cache and delivery controls

  • Configure cache lifetimes, purge paths and serve existing stale content during selected origin errors or cache updates.
  • Use TLS 1.3 and signed-token URLs to control access.
  • Resize, crop and transform images, with separate cached objects for transformed URLs.

Image transformations have format and size limits. Purge each transformed URL when removing cached variants.

Security and media

Managed WAF rules, DDoS mitigation, bot protection and rate limits are available. Rate-limit controls described here apply to Dynamic CDN resources; confirm the selected product and plan. Keep the origin protected from direct traffic that could bypass the CDN.

Streaming resources accept RTMP input and package streams for HLS and MPEG-DASH. Prepare encoded renditions upstream: the CDN streaming path does not perform video encoding or bitrate transcoding.

Logs and visibility

Edgesight Instant Logs provides searchable request records within seconds, with plan-specific retention and export limits. Logpush sends compressed batches to configured destinations every five minutes or when a size threshold is reached; activation requires sales contact. Batched delivery is different from a continuous request stream.

Pricing

Request a consultation and quote for the CDN services your project needs.

Ask for delivery rates by region, request charges, minimum commitments, and the cost of security, streaming, image processing and log retention.

Use Advanced → Add your quote in the calculator to enter confirmed rates. A quote estimate does not assume optional services are included or free.

Developer tools

  • Manage CDN resources and settings through the Control Panel or REST API. API tokens are renewable and expire after 30 days.
  • Generate signed access tokens in your application or origin.
  • Export Instant Logs as CSV or NDJSON, subject to plan and export limits.
  • Send Logpush batches to Stook, Amazon S3, compatible object storage, HTTP endpoints or Elasticsearch.

CDN Terraform coverage and a general-purpose edge runtime are unconfirmed. Use the CDN API for delivery automation and Stook instructions for the separate storage workflow.

When it fits

  • Web, API and e-commerce delivery focused on EMEA or MENA.
  • Media workloads with an existing encoder and adaptive-bitrate renditions.
  • Teams seeking cache controls, image processing and application security in one provider.
  • Operations teams that need searchable logs and configurable batch exports.

Before you choose

  • Applications that require a confirmed self-service edge runtime or CDN Terraform resources.
  • Buyers who need a public unit tariff without requesting a quote.
  • Streaming pipelines that expect this CDN resource to encode video or generate bitrate renditions.
  • Workflows that require a guaranteed continuous log stream or zero-delay global purge.
Sources