Backend code that runs when needed.

Functions runs your backend code on HTTP requests, events and schedules — with secrets, logs and execution history in one place.

Start Building Documentation

Pricing starts at [price] per [usage unit] · See pricing

app.stack53.com / acme / storefront / functions

storefront OverviewFunctionsExecutionsSecretsLogsEnvironments

production New function

FUNCTIONTRIGGERSTATUS

checkout-webhookHTTPActive

send-receiptEventActive

sync-inventoryScheduleActive

resize-imageBackgroundDeploying

RECENT EXECUTIONS checkout-webhook succeeded · HTTPsync-inventory succeeded · Schedule Deploying resize-image to production

HTTP endpoints Call a function over HTTPS

Events and schedules Run without a request

Secrets per environment Kept out of your code

Logs and history Every execution recorded

HTTP FUNCTIONS

Write a function. Get an endpoint.

Deploy a handler and call it over HTTPS. Send a test request from the dashboard and see the response before anything goes to production.

Runtimes: [Supported runtimes]An HTTPS endpoint for each HTTP functionTest requests from the dashboard

HTTP functions in the docs →

checkout-webhook · staging[Runtime]

POSThttps://storefront-staging.[functions-domain]/checkout-webhook

export default async function handler(req) { const order = await req.json() // secrets are read from the environment const key = env.PAYMENTS_KEY await recordOrder(order, key) return { status: 200, body: { received: true } } }

TEST REQUESTSend

{ "orderId": "1042" }

RESPONSE200 OK

{ "received": true }

TRIGGERS

Run on requests, events or a schedule.

Choose what starts each function: an HTTP call, an event in your project or a cron schedule. Background functions take slower work off the request path.

How triggers work →

Triggers · sync-inventoryproduction

ADD TRIGGER

HTTPEventSchedule

Cron expression*/15 * * * *Every 15 minutes

Add trigger

ATTACHED

HTTPPOST /sync-inventoryEnabled

Event[Supported events]Enabled

Schedule0 3 * * *Enabled

EXECUTIONS

See every run, and why it failed.

Execution history records each run with its trigger and status. Open any execution to read its logs — from the app, the API or the CLI.

Logs and execution history →

Executions · checkout-webhookproduction

EXECUTIONTRIGGERSTATUSSTARTED

ex_8d2fHTTPSucceeded[Time]

ex_8d2eHTTPFailed[Time]

ex_8d2dHTTPSucceeded[Time]

LOGS · ex_8d2eDownload

[info] request received POST /checkout-webhook [info] parsing order 1042 [info] calling payments service [error] payments service returned 502 [error] execution failed · response 500

ALSO INCLUDED

Everything a function needs.

Full feature list in the docs →

Secrets API keys and credentials set per environment, not in code.

Background functions Hand off slower work and return to the caller right away.

Event triggers Run when something happens in your project: [Supported events].

Scheduled functions Run on a cron expression, with no server to keep running.

Logs and execution history Every run recorded with its trigger, status and output.

API access Deploy, invoke and inspect functions from the API, SDKs or CLI.

HOW IT WORKS

Running in four steps.

01 Create a function In a project, in the environment you choose.
02 Write your handler In the dashboard editor, or deploy it with the CLI.
03 Add a trigger An HTTP endpoint, an event or a cron schedule.
04 Watch it run Follow every execution in history and logs.

AUTOMATE

Deploy and invoke from anywhere.

Anything you can do in the dashboard — deploy a function, invoke it, read its logs — you can do from the CLI, the SDKs or the REST API.

CLI →SDKs →API reference →

$ stack53 functions deploy send-receipt --env staging
# ✓ send-receipt deployed to staging

$ stack53 functions invoke send-receipt --data '{"orderId":"1042"}'
# ✓ execution ex_9c41 succeeded

$ stack53 functions logs send-receipt --follow

Illustrative — see the API reference for exact commands and fields.

USE CASES

What teams run as functions.

Webhook handlers Receive webhooks and serve small endpoints without running a full service. Webhooks App Platform Environments

Event-driven processing React to events in your project and move slow work into the background. Storage Auth Jobs

Scheduled maintenance Clean up data, sync records and send reports on a cron schedule. Databases Cache Backups

SECURITY Secrets kept out of code Secrets scoped to each environmentHTTP functions served over HTTPSWorkspace roles decide who can deploy Security at Stack53 →

AVAILABILITY Canadian regions

Canada Central[Status]

Canada East[Status]

Operated by [Partner / Stack53] All regions →

PRICING From[price]/ [usage unit] Billed by usage. See pricing for units and any included allowance. See full pricing →

FAQ

Common questions.

An HTTP request, an event in your project, a cron schedule, or a call from your own code for background work. Supported events: [Supported events].

RESOURCES QuickstartDeploy your first function Functions guideTriggers, secrets and logs API referenceFunctions, invocations, logs ExamplesFunctions you can fork and deploy

WORKS WITH

App Platform Jobs Storage Databases

Run your first function.

Write a handler, add a trigger and go live on Stack53 — or talk to us about larger workloads.

Start Building Contact Sales