Billable hours back
Setup, pipeline and server groundwork are done before you start
Setup and operations come with it, so you stay on the work.

How the day-to-day compares.
| Task |
|
Without a platform |
|---|---|---|
| Project setup | Fully covered: Repository, structure, CI/CD pipeline, server connection, domain | Not offered: Unbillable hours at the start of every engagement |
| Several clients in parallel | Fully covered: Projects and organisations separate clients, each with their own roles | Not offered: One machine, many local setups, credentials in several places |
| Servers and operations | Fully covered: Your own server over SSH or a managed one, with Docker, reverse proxy, SSL, firewall | Partly covered: Servers maintained on the side, often only once something breaks |
| Deployment | Fully covered: Every merge runs through the same GitLab CI pipeline for test, build | Partly covered: Manual steps you have to relearn after three months away |
| Switching machines | Fully covered: Ubuntu workspaces with VS Code, JetBrains, RDP or VNC. | Not offered: Everything depends on one laptop, and an outage stops all work |
| Mobile releases | Fully covered: Flutter, Expo and native projects into the App Store, Play Store | Not offered: Signing, certificates and store forms done by hand |
| Using AI coding agents | Fully covered: MCP server, mp CLI and VS Code plugin connect Cursor | Partly covered: Agents work without clear conventions or a pipeline to check them |
| Production errors | Fully covered: Error tracking with Sentry once you connect your account under Connections. | Not offered: The client reports the bug, usually at the weekend |
| Handover at the end | Fully covered: Repository, pipeline configuration | Not offered: Knowledge stays with you, which means questions months later |
| How you come across | Fully covered: Audit log, roles, deployments in Git | Partly covered: Operations and privacy questions get answered from scratch per enquiry |
Green is covered, amber is partial, grey is not included.
Six things that matter when nobody else cleans up behind you.
Setup, pipeline and server groundwork are done before you start
Every project has its own credentials, roles and secrets.
Docker, databases, reverse proxy, SSL, firewall and backups are set up by MainPath, on your server or a managed one.
Through the MCP server, mp CLI and VS Code plugin, Cursor
Ubuntu workspaces start ready to use in the browser or over RDP.
Environments and deployments live in Git history, so you can promise a client a system somebody else can pick up.
Entirely your call. We give you the ideal setup for both paths.
The MainPath Toolbox detects tools and starts everything with one click.
Ready-made dev environment. No local setup required.
Four steps from signing to the first deployment.
Pick stack and platforms in the wizard.
Use a managed server or attach the client’s server over SSH.
Develop locally with the MainPath Toolbox or in a cloud workspace.
At the end the client receives repository, pipeline and server setup.
The comparison is not platform versus team, it is platform versus unpaid hours.
Each project is its own unit with its own repository, environments and credentials.
The code belongs to the client, with full code ownership.
Tools like Cursor
Yes. You attach an existing server over SSH
Tell us what you are building. We reply through the contact form.