vercel/vercel-plugin

create-a-backend

Backend architecture guidance.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/vercel/vercel-plugin --skill create-a-backend

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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

NeedVercel product
HTTP APIs, webhooks, streaming, or framework server code[Vercel Functions](https://vercel.com/docs/functions) with [Fluid compute](https://vercel.com/docs/fluid-compute)
Bidirectional realtime connections (WebSockets)[Vercel Functions with Fluid compute](https://vercel.com/docs/functions/websockets); no separate realtime service required
A frontend and one or more backends (API endpoints) that deploy together[Vercel Services](https://vercel.com/docs/services)
An existing Dockerfile, custom runtime, or system dependencies[Container images](https://vercel.com/docs/functions/runtimes/container) on Vercel Functions, optionally composed with Services
Execute generated or user-submitted code, or give each user an isolated Linux workspace[Vercel Sandbox](https://vercel.com/docs/sandbox); load ⤳ skill:vercel-sandbox
Durable multi-step work with retries, sleeps, or external events[Vercel Workflows](https://vercel.com/docs/workflows)
Background jobs, buffering, fan-out, or direct message routing[Vercel Queues](https://vercel.com/docs/queues)
Always-on workers: queue consumers, Celery/Sidekiq/BullMQ workers, job runners[Vercel Daemons](https://vercel.com/docs/daemons) (beta, production only)
Recurring or one-time scheduled work[Vercel Schedules](https://vercel.com/docs/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](https://vercel.com/marketplace/category/storage)
Files and user uploads[Vercel Blob](https://vercel.com/docs/vercel-blob)
Global, read-heavy configuration[Global Config](https://vercel.com/docs/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.
aus demselben Repository

Weitere Skills

Alle Skills
vercel
Offiziell

access-protected-vercel-deployment

Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection. Use when curl, agent-browser, Playwright, or another automated request reaches a Vercel login or protection page; when a protected preview or production URL returns 401 or 403; when TRUSTEDSOURCESENVIRONMENTMISMATCH appears; or when choosing between vercel curl and the x-vercel-trusted-oidc-idp-token header.

Installationen / 1h
1
GitHub Stars
341
Aktualisiert
20. Nov.
vercel
Offiziell

client-side-security

Protect what runs in your users' browsers on Vercel with a Content-Security-Policy header and Page Integrity script monitoring. Use when adding or debugging a CSP, choosing where to set it (Next.js proxy.ts or next.config.js, vercel.json, Project Routes), allowing Vercel Toolbar under CSP, monitoring third-party scripts or tag managers, or meeting PCI DSS script requirements. For WAF rules and rate limits use vercel-firewall; for bots use botid.

Installationen / 1h
1
GitHub Stars
341
Aktualisiert
20. Nov.
vercel
Offiziell

domains

Search, register, connect, transfer, and renew domain names on Vercel using the CLI or Domains Registrar API. Use for domain availability and pricing, custom domains, DNS records, nameservers, ownership verification, and domain orders.

Installationen / 1h
1
GitHub Stars
341
Aktualisiert
20. Nov.
vercel
Offiziell

vercel-schedules

Vercel Schedules guidance — run a private function, route, or Vercel Queues topic on a cron cadence or once at a set time. Covers static schedules in vercel.json, dynamic per-user schedules with @vercel/schedules, handleSchedule, the vercel schedules CLI, environments, jitter, and migrating from Cron Jobs. Use when adding scheduled or recurring work, one-time reminders, or replacing crons.

Installationen / 1h
1
GitHub Stars
341
Aktualisiert
20. Nov.