Skip to content
rigid.fi
Rigid Lambdas · Edge functions

Your code,
inside the network.

Deploy functions into Rigid's global edge — running beside the auth path, not across the internet from it. Your spend rules, your core-banking lookups, your product logic: executed in the same millisecond budget as the authorization itself.

Book a demoRead the docs
$rigid deploy auth_hook.ts --all-regions
auth_hook.ts · runs on every auth
export default async (auth: AuthEvent) => {
  // your core, reached over the private mesh
  const account = await core.balance(auth.holder); // 3ms

  if (account.available < auth.amount) {
    return decline("insufficient_funds");
  }
  if (auth.mcc === "gambling" && account.limits.block_gambling) {
    return decline("holder_preference");
  }
  return approve({ hold: auth.amount });
};
✓ executed in 4.1ms · inside auth budgetv7 · 100% traffic
WHY IT EXISTS

The round-trip to your stack is the latency you can't buy back.

Most processors call your webhook across the public internet and wait. Rigid runs your logic inside the region that's answering the tap — so "check with our core" stops costing a continent.

Legacy: webhook to your data center & back~240ms
Rigid Lambda at the answering edge~4ms

SAME LOGIC, SAME DECISION — 60× LESS WAITING AT THE TERMINAL

ONE DEPLOY · EVERY REGION

Push once. Live at every edge in seconds.

rigid deploy · v7 → 14 regions ✓

fra1 ✓lhr1 ✓iad1 ✓sfo1 ✓gru1 ✓sin1 ✓nrt1 ✓syd1 ✓bom1 ✓jnb1 ✓dxb1 ✓mex1 ✓waw1 ✓icn1 ✓
WHAT TEAMS RUN ON IT

If it has to happen during the auth, it belongs in a Lambda.

Balance checks against your core

→

Authorize against the balance in your core banking system — over the private mesh, in single-digit milliseconds.

Product spend logic

→

Per-holder limits, category blocks, parental controls, budget envelopes — product rules too specific for static card controls.

Real-time rewards & fees

→

Accrue cashback, apply dynamic FX margins or waive fees at decision time — posted to the ledger in the same transaction.

Instant notifications

→

Push the "you just paid €38.20" notification from the edge that approved it — it beats the receipt printer.

Custom risk signals

→

Feed your own device or session data into the decision alongside Fraud AI's score — your context, our models, one verdict.

Stand-in logic

→

If your core is unreachable, your Lambda defines the fallback policy — degrade on your terms, not the network's.

ISOLATED

V8 isolates per tenant — your code can't see anyone else's, and nobody's can slow yours.

BOUNDED

Hard CPU and time budgets — a slow Lambda falls back to your declared policy, never a hung auth.

VERSIONED

Canary to 1% of traffic, watch the metrics, promote or roll back — like any good deploy pipeline.

OBSERVABLE

Logs, traces and per-region latency for every invocation — in the same dashboard as the auths they shaped.

Ship a Lambda in the demo call.

Bring one auth rule you wish your processor could run — we'll deploy it to 14 regions live.

Book a demo