Index of every page on this site: llms.txt
All skills
vercel avatar

/create-a-backend

@250769d official
by vercelvercel/vercel-plugin340 stars
82
Run it yourself

Backend architecture guidance. Use when planning, building, or migrating an API or backend; choosing between Functions, Services, containers, Daemons, Workflow, Queues, and Marketplace databases; or selecting a supported backend framework or runtime.

Use this Skill: https://skilld.dev/gh/vercel/vercel-plugin/create-a-backend

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈67 tokens for metadata: the name and description. ≈1.3k when used: this file. ≈48 more on demand in 1 file.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈269 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Create a Backend

Help the user create a backend by choosing an architecture before reaching for implementation details. Start from the workload, not the programming language. Vercel runs complex backend applications, not just frontends.

Product map

Need Vercel product
HTTP APIs, webhooks, streaming, or framework server code Vercel Functions with Fluid compute
Bidirectional realtime connections (WebSockets) Vercel Functions with Fluid compute; no separate realtime service required
A frontend and one or more backends (API endpoints) that deploy together Vercel Services
An existing Dockerfile, custom runtime, or system dependencies Container images on Vercel Functions, optionally composed with Services
Execute generated or user-submitted code, or give each user an isolated Linux workspace Vercel Sandbox; load ⤳ skill:vercel-sandbox
Durable multi-step work with retries, sleeps, or external events Vercel Workflows
Background jobs, buffering, fan-out, or direct message routing Vercel Queues
Always-on workers: queue consumers, Celery/Sidekiq/BullMQ workers, job runners Vercel Daemons (beta, production only)
Recurring or one-time scheduled work Vercel Schedules (beta; replaces legacy Cron Jobs); load ⤳ skill:vercel-schedules; use Workflow when the job itself must be durable
Postgres, Redis, NoSQL, vector, or other application data Storage integrations from the Vercel Marketplace
Files and user uploads Vercel Blob
Global, read-heavy configuration Global Config

Use Functions for the normal request/response backend. Use Services when independently built components should share one deployment, routing layer, preview URL, and rollback. Use separate Vercel projects when components need independent release cycles.

Prefer a native Functions runtime for supported frameworks. Use container images when the application already has a Dockerfile or requires a custom runtime or system dependencies. They run as autoscaling, stateless Functions rather than always-on container hosts.

Choose Queues for background jobs, buffering, fan-out, and message routing. Choose Workflow for durable multi-step business logic. Choose Daemons only when a process must stay running to pull work, such as a poll-mode queue consumer or an existing Celery, Sidekiq, or BullMQ worker; daemons cannot receive traffic.

Use Sandbox when the backend needs to execute code in an isolated Linux environment or manage a user's workspace. Keep the application's HTTP endpoints in Functions or Services, and load ⤳ skill:vercel-sandbox for authentication, command execution, and workspace lifecycle. For offloading the project's own heavy builds or tests, load ⤳ skill:offload-to-sandbox.

Databases and data stores

Provision data stores through the Marketplace so credentials are injected into the project and environments stay connected. Check the current catalog before choosing a provider.

  • Postgres: Neon, Supabase, AWS/Aurora, Nile, Prisma Postgres
  • MySQL: AWS/Aurora
  • Redis and key-value: Upstash, Redis
  • Document and NoSQL: MongoDB Atlas, AWS
  • SQLite: Turso
  • Realtime application backend: Convex
  • Analytics: MotherDuck

Keep the database close to the Functions region and use a serverless-compatible connection or pool.

Backend frameworks

Vercel provides first-class backend examples and integrations for these frameworks:

  • Node.js and TypeScript: Elysia, Express, Fastify, H3, Hono, Koa, NestJS, Nitro, and xmcp. Next.js Route Handlers are the natural choice when the backend belongs to a Next.js application.
  • Python: FastAPI, Flask, and Django. Other WSGI or ASGI applications can run when they export a compatible app, with additional configuration as needed.
  • Go: supported as a Vercel Functions runtime.

Frontend and backend combinations, for example a Next.js/Vite/SvelteKit frontend with a FastAPI/Flask/Express/Go backend, can be deployed together in one project using Services.

Prefer the user's existing framework. For a new project, choose based on ecosystem and application needs.

Work sequence

  1. Identify synchronous requests, asynchronous work, persistent data, and independently deployed components.
  2. Select the products from the map, then select the framework.
  3. Load the focused skill for implementation: vercel-functions, vercel-services, daemons, queues, workflow, vercel-storage, or marketplace.
  4. Confirm function limits, regions, environment variables, observability, and current product availability in the official docs before deployment.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts10d3 checks · Risk SAFE
  • Gen Agent Trust Hub10d

    This skill provides architectural guidance for building backends on Vercel. It is primarily informational and does not contain executable code or security risks. It correctly identifies security-sensitive patterns like using isolated sandboxes for user-submitted code and managing credentials through official marketplace integrations.

  • Socket10d

    No alerts

  • Snyk10d

    Risk: LOW · No issues

Signed by skilld at 250769d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
summary
Match backend workloads to the right architecture
Other metadata
metadata
{
  "priority": 7,
  "docs": [
    "https://vercel.com/docs/frameworks/backend",
    "https://vercel.com/docs/functions",
    "https://vercel.com/docs/services",
    "https://vercel.com/docs/queues",
    "https://vercel.com/docs/daemons",
    "https://vercel.com/docs/workflows",
    "https://vercel.com/docs/storage"
  ],
  "sitemap": "https://vercel.com/sitemap.xml",
  "pathPatterns": [
    "Dockerfile.vercel",
    "Containerfile.vercel"
  ],
  "promptSignals": {
    "phrases": [
      "backend on vercel",
      "vercel backend",
      "build a backend",
      "create a backend",
      "deploy my backend",
      "backend architecture"
    ],
    "allOf": [
      [
        "backend",
        "vercel"
      ],
      [
        "backend",
        "docker"
      ],
      [
        "backend",
        "node"
      ],
      [
        "backend",
        "python"
      ],
      [
        "backend",
        "queue"
      ]
    ],
    "anyOf": [
      "api",
      "database",
      "service",
      "workflow"
    ],
    "noneOf": [],
    "minScore": 6
  }
}
retrieval
{
  "aliases": [
    "Vercel backend",
    "backend architecture",
    "backend framework"
  ],
  "intents": [
    "build a backend",
    "choose backend products",
    "deploy an existing API or server",
    "select a Node.js or Python backend framework"
  ],
  "entities": [
    "Vercel Functions",
    "Vercel Services",
    "Vercel Queues",
    "Vercel Daemons",
    "Vercel Workflow",
    "Vercel Marketplace",
    "container images"
  ]
}

README badge

README badge for vercel/vercel-plugin/create-a-backend