Edge Functions

An Edge Function is a piece of server code that Aurabase stores for your project and runs on demand. You trigger the same function in three ways:

• A call: your app calls aura.functions.invoke('name'), or sends an HTTP request, and gets the answer.
• A job: you enqueue a call to run in the background, with a delay and automatic retries.
• A schedule: a cron entry enqueues a job at the times you choose.

There are two runtimes: Deno (TypeScript or JavaScript, the default) and WASM (a compiled Rust binary). Each call runs in its own isolated worker with a memory limit and a timeout.

A Deno function is one file that calls Deno.serve. It receives the request you described and returns a Response.

Deno.serve(async (req) => {
  const { name = 'world' } = await req.json().catch(() => ({}))
  return Response.json({ greeting: `Hello, ${name}!` })
})

An export default is never called. A function is a single file: relative imports are not shipped, so use npm: or https://esm.sh/ imports.

• Only invoking a function works with the public key. Everything else needs a service_role key and belongs on your server.
• Requests and responses must stay below about 256 KiB. Use Storage for larger data.
• Every call is stateless. Do not keep data in memory between calls.
• Secrets are variables of the function, set with aura secrets set or PUT /env. Encryption at rest applies only on the PUT path and only when the deployment has a key.
• What a function writes with console.log is not available to you yet. See limits for the current gaps.
• There is one region and no version history: keep your functions in Git.