Company snapshot
| Category | EdgeMesh | G-Core |
|---|---|---|
| Status | defunct | active |
| Founded | — | — |
| Headquarters | — | — |
| Website | — | — |
| Docs | — | — |
Overview
EdgeMesh was a CDN provider focused on e-commerce, offering real-user metrics (RUM) and in-browser caching to optimize website performance. It provided tools for performance telemetry and smart routing, primarily serving businesses needing fast content delivery. The service is now defunct, with no active operations or official website available as of August 2025.
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.
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.
Feature comparison
| Feature | EdgeMesh | G-Core |
|---|---|---|
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.
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.
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.
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.
History & Notes
EdgeMesh offered a developer-centric CDN with a focus on real-user metrics and API-driven configuration. Its GitHub repositories for client and server components remain accessible, but no recent activity suggests ongoing development. The lack of an official EOL announcement creates uncertainty, but the absence of an active website or support channels indicates the service is no longer operational. For historical reference, see https://docs.edgemesh.com for archived documentation.
—