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
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.
Self-hosting your application here means keeping your servers. MainPath provides the platform that works on them.
MainPath is used as a service. It does not install the entire platform on your own hardware.
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.
Add your Linux server with SSH access. For internal servers, you can assign a suitable network tunnel.
Create a supported project or have your agent check whether existing code is supported. Assign your server to the project.
The pipeline checks and builds your changes. A version on main is deployed to the development environment.
Check the running version on development. When it is ready, approve the same build for production.
MainPath needs suitable SSH access. A tunnel can provide the connection when the server is on a private network.
For a public application, DNS records need to point to your server. Choose any additional access rules to suit the project.
Easy Backup is an optional feature for supported MySQL backends. Enable it when needed and review retention and recovery.
You remain responsible for application code and release approvals. Server monitoring and a connected Sentry account can help identify problems.
Try MainPath with a supported project or talk to us about connecting the servers you already have.
No. The MainPath control plane is operated for you. Your application and its configured services can run on your own servers.
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.
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.
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.