Stinger functions

Serverless. For real.

Write a handler. Deploy. Done. Sub-millisecond cold starts. True scale-to-zero. No containers hiding underneath.

Stinger functions

A handler, a request, a response.

An HTTP input reaches a tiny handler and returns structured JSON. Follow both sides of the request.

Local function example

GET/hello?name=

Request

GET /hello?name=Ada
Accept: application/json

Response

Run the example to inspect its response.

Ready to run locally

The handler

export function handle(request) {
  const name = request.query.name;
  return Response.json({
    message: `Hello, ${name}`,
  });
}

An ordinary HTTP contract

MethodGET

Path/hello

Responseapplication/json

This interaction runs locally in your browser. It makes no network request.

How it works

Three steps. Zero YAML.

{ }

Write

HTTP handlers, event triggers, or scheduled invocations. Any language that compiles to WASM. No SDK required -- just export a handler function.

→

Deploy

One command. The CLI compiles, uploads to Comb, and Queen places your function across the nearest regions. Live in seconds.

●

Serve

Requests route to the nearest instance. Snapshot restore means no cold start penalty. Scale to zero when idle. Pay per invocation.

Vs. AWS lambda

Not even close.

WASM-native serverless versus container-wrapped serverless. The numbers speak for themselves.

Cold start

Lambda300ms

Stingers<1ms

Min memory

Lambda128MB

Stingers2MB

Idle cost

Lambda$0.20/hr

Stingers$0

Deploy size

Lambda50MB zip

Stingers342KB

Deploy a function.

One command. Sub-millisecond cold starts. True scale to zero.

Start free →Quickstart guide

Stinger functions

Serverless. For real.

Write a handler. Deploy. Done. Sub-millisecond cold starts. True scale-to-zero. No containers hiding underneath.

Stinger functions

A handler, a request, a response.

An HTTP input reaches a tiny handler and returns structured JSON. Follow both sides of the request.

Local function example

GET/hello?name=

Request

GET /hello?name=Ada
Accept: application/json

Response

Run the example to inspect its response.

Ready to run locally

The handler

export function handle(request) {
  const name = request.query.name;
  return Response.json({
    message: `Hello, ${name}`,
  });
}

An ordinary HTTP contract

MethodGET

Path/hello

Responseapplication/json

This interaction runs locally in your browser. It makes no network request.

How it works

Three steps. Zero YAML.

{ }

Write

HTTP handlers, event triggers, or scheduled invocations. Any language that compiles to WASM. No SDK required -- just export a handler function.

→

Deploy

One command. The CLI compiles, uploads to Comb, and Queen places your function across the nearest regions. Live in seconds.

●

Serve

Requests route to the nearest instance. Snapshot restore means no cold start penalty. Scale to zero when idle. Pay per invocation.

Vs. AWS lambda

Not even close.

WASM-native serverless versus container-wrapped serverless. The numbers speak for themselves.

Cold start

Lambda300ms

Stingers<1ms

Min memory

Lambda128MB

Stingers2MB

Idle cost

Lambda$0.20/hr

Stingers$0

Deploy size

Lambda50MB zip

Stingers342KB

Deploy a function.

One command. Sub-millisecond cold starts. True scale to zero.

Start free →Quickstart guide