Your servers stay your servers
Existing machines are attached over SSH and configured with Docker, reverse proxy, SSL, firewall and backups.
A grown setup next to MainPath
How the day-to-day compares.
| Task |
With MainPath
|
Without MainPath |
|---|---|---|
| Project setup | Fully covered: Repository, structure, CI/CD pipeline, server connection, domain | Not offered: Every project carries the handwriting of whoever set it up |
| Operational knowledge | Fully covered: Environments and deployments live as readable configuration in Git history | Not offered: Knowledge sits in scripts, wiki pages of uncertain age |
| Using your own servers | Fully covered: Attach existing servers over SSH or use managed servers | Partly covered: Possible, but every machine is maintained on its own |
| Server baseline | Fully covered: Docker, databases, reverse proxy, SSL, firewall | Partly covered: Manual setup, documented afterwards at best |
| Roles and access rights | Fully covered: Organisations, roles and access rights govern access per project | Partly covered: Permissions grew historically and are rarely cleaned up |
| Evidence for audits | Fully covered: An audit log of relevant changes plus Git history for environments | Not offered: Evidence gets assembled shortly before the audit date |
| Where processing happens | Fully covered: Operated in the EU, GDPR compliant, data processing agreement available | Partly covered: Individual services sit outside the EU and have to be assessed one by one |
| Onboarding and cover | Fully covered: Remote workspaces with VS Code, JetBrains, RDP or VNC start ready to use | Not offered: New colleagues need days before an environment runs |
| Production errors | Fully covered: Error tracking with Sentry, including stack trace, release and context | Partly covered: Errors arrive through support and get classified by hand |
| Provider dependency | Fully covered: Repositories, pipeline configuration | Partly covered: Individual tools and contractors are replaceable only with effort |
Green is covered, amber is partial, grey is not included.
What an SMB with in-house IT gets
Six points about operational safety and being able to prove things.
Operated in the EU
Processing and hosting happen in Europe, GDPR compliant
A history that holds up
The audit log records the relevant changes.
Roles instead of grown access
Organisations, roles and access rights define who may see and change which project and environment.
Knowledge in the repository
Environments and deployments live as configuration in Git history
One way to deliver
Every project uses the same GitLab CI stages for test, build
-
Anna WeberAdministrator
Organization, members & billing
-
Max SchneiderDeveloper
Code, Git & deployments
-
Tom RichterTester
QA on dev & staging
-
Paul KleinCustomer
Customer app & feedback
Replacing a grown setup step by step
One pilot project first, then controlled rollout.
-
Agree the ground rules
Decide which servers may be used, where which data is processed and which roles should exist.
-
Run a pilot
Pick a project with a clear scope, create it in the wizard and attach an existing server over SSH.
-
Write down the standard
Adjust the pipeline configuration in the repository to your internal requirements.
-
Move the estate across
Existing applications follow gradually, sensibly bundled with updates or relaunches that are due anyway.
Frequently asked questions
Do we have to replace our existing infrastructure?
No. You attach existing servers over SSH
How does this help with an audit or certification?
MainPath supplies the technical traceability auditors ask for
What happens when the colleague who knows everything is unavailable?
That is precisely the risk that configuration in Git addresses.
Where is our data processed?
MainPath itself is operated inside the EU, GDPR compliant and with a data processing agreement.
How predictable are the costs?
The model is a MainPath base price plus add-ons for users, workspaces
Talk to the sales team
Tell us what you are building. We reply through the contact form.