Company snapshot
| Category | G-Core | OnApp CDN |
|---|---|---|
| Status | active | active |
| Founded | — | — |
| Headquarters | — | — |
| Website | — | — |
| Docs | — | — |
Overview
G-Core, founded in 2011 and headquartered in Luxembourg, operates a global content delivery network (CDN) with a focus on low-latency delivery for video, gaming, and web content. The company serves a range of customers, including gaming platforms, media providers, and enterprises, leveraging its extensive network to optimize performance. Its CDN is designed to handle dynamic and static content, with additional services like cloud hosting and DDoS protection. G-Core targets businesses needing robust global reach and specialized video/gaming delivery.
OnApp CDN is a federated content delivery network designed for hosting providers, utilizing spare capacity in OnApp Clouds to deliver content globally. It supports HTTP push, pull, and streaming/live streaming, catering to hosting providers and enterprises managing web content delivery. The platform integrates with OnApp Cloud, enabling users to leverage a network of edge servers for improved performance. It is primarily used by service providers and enterprises needing scalable CDN solutions. The service is operational as of August 16, 2025, with recent updates enhancing its reporting capabilities.
Network & Architecture
G-Core operates over 150 points of presence (PoPs) across Tier III/IV data centers globally, with a network capacity exceeding 110 Tbps and over 11,000 peering partners. The network spans regions including North America, EMEA, APAC, LATAM, Africa, India, and the Middle East, with an average latency of 30 ms. It uses intelligent routing and TCP/TLS optimization for performance. The company is particularly strong in gaming and video delivery but may have less coverage in certain emerging markets compared to larger providers like Cloudflare or Akamai.
OnApp CDN operates a global network of Points of Presence (PoPs) by leveraging spare capacity from OnApp Clouds, though specific PoP counts are not publicly detailed. It uses a federated model, combining edge servers from multiple cloud hosts to ensure broad geographic coverage. The platform supports content delivery across regions including North America, EMEA, APAC, and others, with synchronization between CDN and OnApp Cloud occurring every 20 minutes by default. Regional strengths include flexibility for hosting providers, but limitations may arise from reliance on third-party cloud capacity, potentially affecting consistency in less dense regions.
Feature comparison
| Feature | G-Core | OnApp CDN |
|---|---|---|
waf | ✓ | ✗ |
bot_mitigation | ✓ | ✗ |
ddos | ✓ | ✗ |
rate_limit | ✗ | ✗ |
http3_quic | ✓ | ✗ |
tls13 | ✓ | ✗ |
tiered_cache | ✗ | ✗ |
origin_shield | ✓ | ✗ |
instant_purge | ✓ | ✓ |
stale_while_revalidate | ✗ | ✗ |
stale_if_error | ✗ | ✗ |
image_optimization | ✓ | ✗ |
video_vod | ✓ | ✓ |
video_live | ✓ | ✓ |
drm | ✗ | ✗ |
hls_dash_packaging | ✗ | ✗ |
websockets | ✓ | ✗ |
signed_urls | ✓ | ✗ |
edge_compute | ✗ | ✗ |
functions | ✗ | ✗ |
kv_storage | ✗ | ✗ |
api_first | ✓ | ✓ |
realtime_logs | ✓ | ✓ |
log_push | ✓ | ✗ |
terraform | ✓ | ✗ |
Legend: ✓ = Supported, ✗ = Not supported, — = Not listed
Pricing
G-Core uses a pay-as-you-go (PAYG) model with a free tier offering limited usage. Pricing varies by region and traffic volume, with per-GB rates available on their pricing page. Enterprise plans are available for high-volume customers, and premium support is offered for migrations. No public per-GB pricing examples are disclosed without signup. See https://gcore.com/cdn/pricing for details.
OnApp CDN primarily targets enterprise clients, with pricing typically based on committed contracts tailored to hosting providers. No public per-GB pricing is disclosed, and there is no free tier or pay-as-you-go (PAYG) option widely advertised. Pricing details are available through direct inquiry with OnApp sales teams. For more information, visit https://www.virtuozzo.com/onapp-cdn/.[](https://www.virtuozzo.com/onapp-cloud-docs/7.0/release-notes-onapp-6-4/OnApp%2520CDN.pdf)
Integrations & DevEx
G-Core supports Terraform for programmatic CDN management, enabling versioning and replication across environments. Its API-first approach includes comprehensive documentation for resource configuration. Real-time logs and customizable log exports (5–60 minute latency) via Logs Uploader enhance observability. Migration tools and plugins simplify transitions from deprecated CDNs like StackPath or Lumen Technologies. SDKs and CI/CD integrations are not extensively documented.
OnApp CDN offers API-first integration for managing CDN resources, with documentation available at https://docs.onapp.com/cdn/. Real-time logs support monitoring, but there is no public evidence of Terraform support, SDKs, or specific CI/CD integrations. The platform includes tools for managing CDN resources within the OnApp Control Panel, with recent UI updates enhancing usability. Migration tools or import capabilities are not explicitly documented.
When it fits
- Businesses needing low-latency video or gaming content delivery with global reach.
- Enterprises seeking integrated DDoS protection and WAF for secure content delivery.
- Developers using Terraform or APIs for automated CDN management.
- Hosting providers needing a federated CDN integrated with OnApp Cloud for scalable content delivery.
- Enterprises requiring video VOD and live streaming with global reach through a network of edge servers.
- Users prioritizing API-driven management and real-time logging for CDN operations.
When it doesn’t
- Organizations requiring extensive edge compute or serverless functions, which G-Core lacks.
- Small businesses needing highly competitive pricing compared to BunnyCDN or Cloudflare.
- Users in regions with sparse PoP coverage, where latency may not match larger providers.
- Small businesses or startups seeking pay-as-you-go pricing or free tiers, which OnApp CDN does not offer.
- Organizations needing advanced security features like WAF, DDoS protection, or bot mitigation, which are not documented.
- Users requiring edge compute, image optimization, or specific protocol support like HTTP/3, which are unsupported.
History & Notes
—
—