Webhooks and integrations
Payment providers, CRM or shop systems report events via HTTP, and the few calls don't justify a permanently running service. A function receives the webhook, processes it and costs nothing when it isn't called.
Functions that only run when they are needed: invoked via HTTP or triggered by events, isolated in a hardened sandbox and billed by usage.
No invocation, no cost – under load, additional instances start automatically.
You bring a container image: any language, any version.
React to uploads, webhooks or platform events – without a listener of your own.
Payment providers, CRM or shop systems report events via HTTP, and the few calls don't justify a permanently running service. A function receives the webhook, processes it and costs nothing when it isn't called.
Uploaded files should be resized, converted or checked automatically. The upload triggers the function, and the result lands back in storage – without a listener of your own and without a server waiting for work.
Campaigns or month-end closings briefly generate many times the usual load. Functions automatically start additional instances on demand and then scale back to zero, so you pay for usage instead of reserve capacity.
An event in your platform should automatically trigger an action, such as a notification or a sync with a third-party system. The function is triggered by the event and runs isolated in a hardened sandbox, in the language and version of your choice.
One million invocations and 400,000 GB-seconds are free every month.
Serverless Functions comes in three operating models – and you can switch at any time as your team grows or wants to focus on other things.
You get the cluster with full access and orchestrate it yourself.
We operate cluster, ingress and updates – you push images.
We also build pipelines and deployments and take responsibility for operating your application.