Dev Resources
Gcore Function as a service favicon

Gcore Function as a service

Serverless

Run code as a function without creating and maintaining virtual machines.

Gcore Function as a service's website screenshot

About Gcore Function as a service

Gcore Function as a Service lets developers run code as functions without provisioning or maintaining virtual machines. It is a serverless compute offering within Gcore's broader cloud platform, which also includes CDN, DNS, streaming, AI inference, GPU cloud, compute, storage, containers, databases, and security products such as WAF and DDoS protection.

The service is billed based on the duration pods are allocated to run submitted code; when there are no requests and a configured pod timeout passes, the pod shuts down, with the shutdown process taking up to one minute. Cost efficiency is achieved when requests are frequent or pods remain active longer to serve them.

Gcore advertises a 99.9% production-level SLA for this service and provides a pricing comparison against Azure Functions, AWS Lambda, GCP Cloud Functions, and Scaleway based on a workload of 4,000,000 invocations, GB-per-second execution, and egress for 400GB, using the Frankfurt region as the basis for comparison.

Key features

  • Run code as functions without provisioning or maintaining virtual machines
  • 99.9% production-level SLA
  • Automatic pod scale-down when idle to reduce cost
  • Competitive per-invocation and GB-second pricing versus AWS Lambda, Azure Functions, and GCP Cloud Functions

Frequently asked questions

What is Gcore Functions?

It is a function-as-a-service offering that runs code without requiring you to create or maintain virtual machines.

What SLA does Gcore Functions offer?

Gcore guarantees a 99.9% production-level SLA at no additional cost.

How is Gcore Functions priced compared to competitors?

Gcore lists a total cost of $15.32 for a sample workload versus $84.10 for Azure Functions, $87.60 for AWS Lambda, and $111.20 for GCP Cloud Functions in the Frankfurt region comparison.

How does billing work when there is no traffic?

Functions are charged based on pod duration, and pods shut down after an idle timeout, with the shutdown process taking up to 1 minute.

Advertise here

Featured products

  • SerpApi - Search API favicon
  • CoreClaw favicon

Show your product to thousands of developers

· 100k monthly pageviews
· 7k newsletter subscribers

Advertise your product

You might also like