Functions

​

Overview

​

Technology Stack

​

Core Components

• Deno Runtime — Secure, isolated JavaScript/TypeScript execution
• HTTP Router — Each function is an HTTP endpoint
• Secret Manager — Inject environment variables securely
• JWT Middleware — Optional authentication for functions

​

How It Works

1. Write a function handler in JavaScript/TypeScript
2. Deploy via the dashboard or MCP
3. Function is available at /api/functions/{function-name}
4. Supports all HTTP methods (GET, POST, PUT, PATCH, DELETE)

​

Function Example

export default async function handler(req: Request) {
  const { method } = req;

  if (method === "POST") {
    const body = await req.json();
    // Your custom logic here
    return new Response(JSON.stringify({ success: true }), {
      headers: { "Content-Type": "application/json" },
    });
  }

  return new Response("Method not allowed", { status: 405 });
}

​

Authentication Flow

1. Client sends request with Authorization: Bearer <token>
2. Yboard validates the JWT
3. User context is injected into the request
4. Function can access user ID and claims

​

Performance Characteristics

​

Execution Limits

​

Optimization Strategies

• Keep functions focused on a single task
• Use streaming responses for large outputs
• Cache expensive computations
• Minimize cold starts by keeping functions small

​

Best Practices

1. Keep functions small — One function per task
2. Use secrets for API keys — never hardcode credentials
3. Handle errors gracefully — Return appropriate HTTP status codes
4. Use TypeScript for type safety
5. Test locally before deploying