Your appsOn your servers

Building with AI and want to host your own application? MainPath connects your servers with project structure, tests and deployments. We operate the control plane, while you choose the infrastructure.

Setup and deployment for your connected server

A clear divisionFrom project to operation

Self-hosting your application here means keeping your servers. MainPath provides the platform that works on them.

MainPath handles

  • Operating the MainPath control plane
  • Prepared server setup with Docker, a reverse proxy and HTTPS
  • A project foundation with tests, builds and a deployment workflow

You decide

  • Your server provider, location and access
  • Application code, configuration and production approvals
  • Access rules and appropriate backup and recovery procedures

MainPath is used as a service. It does not install the entire platform on your own hardware.

Your serverA project state you can follow

MainPath deploys your application to its assigned server. The version running on development or production stays traceable in the project, rather than only in a local script.

  • The server stays in your account or company
  • Your application and its configured services run there
  • Approving production remains a deliberate decision
Git workflow and deployment

From server to running appOne step at a time

  1. Connect a server

    Add your Linux server with SSH access. For internal servers, you can assign a suitable network tunnel.

  2. Prepare your project

    Create a supported project or have your agent check whether existing code is supported. Assign your server to the project.

  3. Try changes on development

    The pipeline checks and builds your changes. A version on main is deployed to the development environment.

  4. Approve production

    Check the running version on development. When it is ready, approve the same build for production.

Self-host your applicationWith clear prerequisites

  • A reachable Linux server

    MainPath needs suitable SSH access. A tunnel can provide the connection when the server is on a private network.

  • Set up domains and access

    For a public application, DNS records need to point to your server. Choose any additional access rules to suit the project.

  • Enable backups when needed

    Easy Backup is an optional feature for supported MySQL backends. Enable it when needed and review retention and recovery.

  • Keep track of your application

    You remain responsible for application code and release approvals. Server monitoring and a connected Sentry account can help identify problems.

Your infrastructureYour next project

Try MainPath with a supported project or talk to us about connecting the servers you already have.

Questions about self-hosting

Do I install MainPath itself on my server?

No. The MainPath control plane is operated for you. Your application and its configured services can run on your own servers.

Can I keep using an existing server?

Yes, if it is a suitable Linux server with SSH access. MainPath needs to be able to reach it; a network tunnel can provide access to internal servers.

Connect your own server

Does that keep every piece of data exclusively on my server?

Your application and its configured databases and files run on the assigned server. MainPath operates the control plane separately; project management, repositories and automation are part of that platform service. Review where data is processed for your particular project.

Contracts and privacy documents

Can I keep using my code without MainPath later?

Your application code remains yours and lives in the repository. When moving, plan to export the code and required configuration and set up a new build and deployment workflow. A server you own stays in your possession or provider account.

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