Skip to content

Platform

Vercel Deployment

We deploy Next.js applications to Vercel in accounts you own, with preview environments per change, edge delivery and a one step rollback.

Laptop on a software development workspace

Usage

What we build with Vercel

  1. Production and preview environments with separate data and secrets
  2. Static and edge delivered marketing sites
  3. Server rendered applications and route handlers
  4. Scheduled jobs through platform cron
  5. Custom domain and certificate configuration
  6. Deployment pipelines with gates and rollback

Rationale

Why we choose it

  • Preview per change

    Every pull request gets a real URL with its own environment, which is what makes review possible without touching production.

  • Static content at the edge

    Generated pages are served from locations near the visitor, so most of a marketing site never reaches an application server.

  • Rollback is one action

    Deployments are immutable and previous ones stay available, so recovery from a bad release is seconds rather than a rebuild.

Practice

Architecture patterns we use

  • Environment scoped secrets

    Separate values for development, preview and production, so a preview can never write to production data.

  • Static first, dynamic where needed

    Routes default to static generation. Dynamic rendering is a deliberate choice recorded per route rather than a default.

  • Redirects in configuration

    Permanent redirects for moved URLs live in configuration and are reviewed like code, because a lost redirect is lost ranking.

  • Accounts owned by the client

    The project, the domain and the billing belong to you, so a change of supplier is an access change rather than a migration.

Build with our Vercel engineers

Tell us what you are building and what it has to connect to. We will come back with an approach, a scope and what it would take.

  • A mutual NDA is signed before project details are shared.
  • Scope is fixed in writing before any build starts.
  • You own the source code, the IP and the documentation at delivery.
  • Support plans are available and tailored on a discovery or technical call.