Your Next.js appFrom prompt to your domain

Build the frontend with your AI agent. MainPath gives your Next.js app a project foundation and connects tests, builds and deployment to your own connected server.

A browser app with a development environment and your own production domain

The frontend is the startYour backend can belong here too

When your app needs its own API, add NestJS, Laravel or FastAPI to the same MainPath project. Each component has its own repository; its configuration belongs to the shared project.

  • Work on application code with your familiar AI agent
  • Manage the frontend and API in one project
  • Keep separate configuration for local development, Dev and production
A project with several components

First on your computerThen on your server

Open your cloned project and start the Next.js app from the root of its repository. MainPath Toolbox loads the right environment and starts the development server.

  • Your own values belong in the documented custom files
  • Generated environment files and .gitlab-ci.yml stay unchanged
mp run-local
The shared start command for your MainPath applications

From a local changeTo your own domain

You decide when a tested build becomes a published version.

  1. Prepare the project

    Choose Next.js for your app or have your agent check existing code for support before importing it.

  2. Assign a server

    Connect a server and assign it to the project. MainPath prepares delivery with HTTPS.

  3. Check on Dev

    Changes on main go through tests and builds. Use the Dev address to try the resulting version.

  4. Approve production

    Set up your domain and DNS, test the build on Dev and deliberately start the production job.

After the first releaseKeep track of what is running

At your own address

MainPath shows the required DNS records and checks them. With a connected DNS provider, it can set the records for you.

Connect errors to a version

Connect your Sentry account and enable it for the app. Errors appear there with a stack trace and release version.

Your next Next.js versionWith a clear path to publishing

Start a project or talk to us about bringing your existing Next.js app to MainPath.

Questions about Next.js on MainPath

Can I bring my existing Next.js app?

Yes, if the project is supported. Your AI agent checks the existing code first and then guides the import. Next.js is one of the supported app stacks.

Explore project imports

Where does my Next.js app run?

The pipeline builds a Docker image and deploys it to your project’s server. Traefik routes requests to the app using its domain; MainPath sets up HTTPS.

Publish browser apps

Do I have to write my own pipeline?

The project includes a prepared pipeline. Do not edit generated files such as .gitlab-ci.yml. Your own environment values belong in the documented custom files; other changes go through MainPath configuration.

Work with environment variables

Can I keep features tied to a particular hosting runtime?

Check those dependencies when bringing your app over. MainPath deploys the Next.js application as a container on your server. Features that rely on a particular provider’s runtime are not automatically replaced.

Are databases, backups and error tracking always enabled?

No. Choose components and features to fit your project. Add a database and supported backups when needed. For error tracking, connect your Sentry account and enable Sentry for the app.

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab