Skip to main content
tensel
Sign up

Deploy guides

Deploy Next.js on Tensel

Connect a GitHub repo and push. The rest is handled. No DevOps required.

From commit to production
$ tensel github import acme/nextjs-appDetected Next.js — Node server.→ build  isolated context, Paris→ rollout  1/1 replicas  healthy ✓ https://nextjs-app.tensel.cloud   38 s

How Next.js is detected

Detection
the `next` dependency in package.json
Runs as
a Node server in a serverless container in Paris, or a static site on the edge when next.config declares `output: "export"`

From repo to URL

  1. 1

    Import the repository — “tensel github import” or the dashboard — or drop a folder, no git required.

  2. 2

    Tensel detects Next.js, builds in a disposable virtual machine and publishes an immutable image.

  3. 3

    Your application answers over HTTPS on its tensel.cloud subdomain; every later push redeploys.

Good to know

  • An explicit `output: "export"` routes the build to the static edge instead of a container; anything else runs `next start`, conservatively, so dynamic routes keep working.
  • ISR, Vercel image optimization and edge middleware are platform features of Vercel, not of Next.js; they do not run here. Standard server rendering and API routes do.
  • Your app must listen on the port the platform provides (PORT). Every framework's production server does this by default.
  • Environments scale to zero on the Free plan; always-on keeps an instance resident from the Personal plan up.
Create an accountDeploy guides