Give your app an address
Connect your domain to the project. The right DNS records point to the target server, with HTTPS as part of the prepared environment.
Building your app with AI and want to run it on Hetzner? MainPath connects your cloud account or existing server to a prepared project foundation, tests and a clear release workflow.
Hetzner provides the infrastructure. MainPath connects it to your project workflow.
Have MainPath create a server in your Hetzner account, or connect an existing suitable Linux server over SSH.
For a new cloud server, store the Hetzner API token in MainPath. For an existing server, use its SSH credentials.
Assign the configured server to your project. MainPath prepares the server environment and deployment access for the pipeline.
On main, the pipeline checks and builds your code and updates the Dev environment. Try the change there before releasing it.
Release the tested version through the manual release step. The target server stays in your Hetzner account.
MainPath sets up Docker, the reverse proxy and HTTPS, then connects the server to your project’s deployments. Your Hetzner access stays with you; project configuration and application code remain part of your workflow.
Hetzner operates the cloud infrastructure. MainPath provides the project and deployment workflow. Agree who looks after the application, server maintenance and incidents in your setup.
Hetzner offers several cloud locations. Check the location actually used and your application’s data flows; the provider’s name alone does not determine them.
Decide which data and files need backups and how to test recovery. A server backup and an application backup are different parts of that plan.
API tokens and SSH credentials are needed for setup. In MainPath, roles and project membership determine who manages projects and servers.
Connect your domain to the project. The right DNS records point to the target server, with HTTPS as part of the prepared environment.
Tests and builds accompany your code. Dev shows the new version before you approve production.
Invite your team and assign appropriate access. Server assignment and project permissions stay part of your shared organization.
Start with a supported project and connect the right server. Give your AI-built prototype a traceable path through to release.
No. Hetzner provides the cloud resources in your account and bills you for them. MainPath is the project and deployment platform you connect to it. The two services can work together.
Not necessarily. You can store a Hetzner Cloud API token in MainPath and have it create a new server in your account. If you already have a suitable Linux server, there is a separate connection over SSH.
Yes. Your own access remains available. For an SSH connection, MainPath uses the supplied credentials for setup and creates its own deployment key. Before connecting an existing server, check that its current services fit the intended setup.
No. Hetzner’s server backups and MainPath’s optional Easy Backup feature serve different purposes. Easy Backup applies to supported MySQL backends in production and backs up their database and uploads. Check which backups are enabled for your project and how to restore the data.
That depends on the actual server and your other services. Hetzner offers cloud locations in several countries. Check the location used, your integrations and application data flows for your project.