Your API with NestJSReady for web and apps

Build your API’s features yourself or with your AI agent. MainPath adds project structure, tests and a route to your server, so your local NestJS backend becomes a project your team can work with.

A project can connect a backend, app and website. The illustration shows example components.

Your next featureOn your machine first

Open your local project folder and start with the MainPath CLI. Develop and check your NestJS modules there before committing changes to the repository.

  • Business logic and API behaviour stay in your NestJS code.
  • Put your environment values in the documented custom files and confidential values in managed secrets.
mp run-local
The CLI starts the appropriate local development environment for your project.

Your backend onlineOn the server you choose

The pipeline builds a Docker image for your backend. MainPath configures connected servers with deployment access and HTTPS. Your API domain takes clients to the backend.

  • Connect an existing Linux server over SSH.
  • Configure the database and other services to suit your backend.
  • Web and mobile clients can use the same backend.
Backend publishing in detail

What your API needsDecisions to make in the project

The platform prepares the workflow. You decide how your application behaves.

  • Values for each environment

    Dev and production have separate configurations. Add your values to the custom files; MainPath maintains generated files.

  • Data and uploads

    Choose the services you need and use the documented storage paths. Enable Easy Backup when needed for supported MySQL backends.

  • Access and permissions

    Manage project access and secrets deliberately. Implement login, authorization and API rules in your application code.

  • Contracts for your clients

    Define endpoints and data formats in NestJS. Your frontend and app consume them; develop and test their features against the API.

From commit to a reachable APIWith a version you can check first

  1. Save the change

    Merge your change into main. The prepared pipeline starts its checks there.

  2. Build the backend

    Tests check the code and the build creates the Docker image for your application.

  3. Try it on Dev

    After a successful build, the version is published to Dev. Check the API with its clients too.

  4. Approve production

    When the version is ready, start the production step deliberately. A push alone does not approve it for production.

See what happens after releaseApplication errors and server health

Understand your API’s errors

Connect your Sentry account and enable it for the backend. Errors then appear with stack traces and release versions in your Sentry project.

Watch the server

Enable optional server monitoring to see resource use and network traffic. Your team decides what response a problem needs.

Your next API endpointWith a path to release

Start a NestJS project or talk to us about bringing your existing backend and its clients to MainPath.

Questions about NestJS on MainPath

Can web, app and NestJS live in the same project?

Yes. A MainPath project can contain several components, such as a NestJS backend, a web frontend and a mobile app. They share a project foundation and have appropriate separate build and deployment steps.

Can I import an existing NestJS backend?

NestJS is one of the supported backend stacks. Your agent checks the existing project and its component mapping before importing it.

Import an existing project

Which database and backup options are available?

The backend templates use MySQL in a separate container. Easy Backup is an optional setting for supported MySQL backends in production; enable it in the project configuration. It is not a blanket backup of all applications and services.

Configure backups

Are error tracking and server monitoring enabled automatically?

No. Connect your Sentry account under Connections and enable Sentry for the backend. Enable server monitoring separately on the server. Monitoring does not replace an agreed support service or incident response.

Servers and monitoring

Can I change the pipeline and environments?

MainPath maintains generated files such as .gitlab-ci.yml and generated.yaml; do not edit them directly. Put your environment values in the documented custom files and confidential values in managed secrets. Talk to us about additional automation.

Work with environment variables

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