
GCore Load Balancer
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
What is GCore Load Balancer
Managed provisioning and operations
Cloud platform integration
API-driven configuration options
Provider lock-in considerations
Less control than self-managed
Feature depth varies by region
Plan & Pricing
Pricing model: Pay-as-you-go (usage-based) Free tier/trial: See notes below How pricing is published: Gcore does not show a public fixed tier table for "Load Balancer" on the public pricing pages. Official pricing for Load Balancers is exposed via the vendor Cloud Pricing API / Cloud calculator and is returned per-region and per-flavor (per-hour and per-month breakdowns). The pricing must be previewed using the API endpoint: POST /cloud/v2/pricing/{project_id}/{region_id}/loadbalancers (or the v1 equivalent) and requires project_id/region_id (and API key) to retrieve actual numeric rates for a given account/region. The API response returns currency_code and per_hour / per_month breakdowns (flavor, external_ip, floating_ip, etc.).
Example / notes (from official API docs; illustrative only): The API response schema includes fields such as currency_code and per_hour (external_ip, flavor, floating_ip) and per_month (external_ip, flavor, floating_ip). The docs show example keys like price_per_hour and price_per_month in example responses, but those are example values in the API documentation and not a public price list.
Summary: No public, static tiered pricing table for Gcore Load Balancer is published on the vendor website; prices are determined per-region/per-flavor and must be retrieved via the official Cloud Pricing API or from the customer Cloud console.