Env & config

Secrets and environment variables for serverless functions

Per-function environment variables from the test panel (Config → Environment) or the API—runtime injection into the container, plus log and trace redaction for common secret-shaped strings. Built for function configuration, not as a standalone enterprise secrets manager.

How it works

Configure, invoke, read from env

Add environment variables

In the editor test panel, open Config and expand Environment — or call updateFunction with an envVars map. Values are stored on the function record in the app database.

Invoke the function

The platform merges layer and function variables and passes them into the runtime environment for that invocation.

Read in your handler

Use process.env, os.environ, or os.Getenv like any other deployment. Avoid logging raw credentials; redaction helps but is not a full secrets manager.

Features

Sensitive values without hardcoding in source

Per-function env vars

Configure keys and values per function without editing code. Password inputs in the UI reduce shoulder-surfing while you type.

Runtime injection

The same path used for gateway, jobs, and manual runs supplies environment variables to the container.

Log and trace redaction

Common patterns (tokens, passwords, API keys) are masked in persisted logs and traces where redaction runs.

Pair with your deployment pipeline

For long-lived production credentials, inject values from CI/CD or the host environment and keep the database surface area small — function env vars suit values you accept storing with the function record.

Example

Set environment variables, use them in your function

set-env.js

// Per-function env vars (Config → Environment in the editor, or API):
await api.updateFunction("function-id", {
  envVars: {
    OPENAI_API_KEY: "sk-...",
  },
});

// Values are stored on the function and injected into the container at invoke time

ai-summarizer/index.js

export async function handler(event, context) {
  // OPENAI_API_KEY comes from function env — avoid logging it
  const payload = typeof event.body === 'string' ? JSON.parse(event.body || '{}') : (event || {});
  const { prompt } = payload;
  const openai = new OpenAI({
    apiKey: process.env.OPENAI_API_KEY,
  });

  const completion = await openai.chat.completions.create({
    model: "gpt-4o-mini",
    messages: [{ role: "user", content: prompt }],
  });

  return {
    statusCode: 200,
    body: JSON.stringify({ result: completion.choices[0].message.content }),
  };
}

Get started free

Deploy your first function in minutes. No credit card required.