From template to release
A project begins with structure, conventions
MainPath for startups
Pipeline, servers and stores are ready before the team builds them.
The first months with and without a platform
How the day-to-day compares.
| Task |
With MainPath
|
Without a platform |
|---|---|---|
| Project setup | Fully covered: Repository, project structure, CI/CD pipeline, server connection, domain | Not offered: The first weeks go into fundamentals rather than product |
| Web and mobile at once | Fully covered: One project holds frontend, backend | Partly covered: Separate setups per platform, each with its own pipeline |
| DevOps knowledge on the team | Fully covered: Server baseline, databases, reverse proxy, SSL, firewall | Not offered: One developer becomes the part-time infrastructure owner |
| Deployment | Fully covered: Every merge runs through the same GitLab CI pipeline for test, build | Partly covered: Deployments depend on scripts and on whoever wrote them |
| Store releases | Fully covered: App Store, Play Store and Microsoft Store including metadata, screenshots | Not offered: Signing and store forms cost a day per release |
| Seeing production errors | Fully covered: Error tracking with Sentry once you connect your account under Connections. | Not offered: Users report bugs before the team notices them |
| Onboarding developers | Fully covered: Remote workspaces with VS Code, JetBrains, RDP or VNC start ready to use | Not offered: A day or two of machine setup, usually with loose ends |
| Due diligence | Fully covered: deployment configuration, audit log, roles | Partly covered: Details about operations and access get reconstructed for the data room |
| Growing into it | Fully covered: Extra environments, users, workspaces and CI minutes come as add-ons | Partly covered: A setup built for two people stops working at ten |
| Provider dependency | Fully covered: Repositories, pipeline configuration | Partly covered: Scattered services that each have to be replaced separately |
Green is covered, amber is partial, grey is not included.
What a small team gets
Six things that matter between prototype and Series A.
Web and mobile in one project
Frontend, backend and mobile apps belong to the same project
Infrastructure without a hire
Docker, databases, reverse proxy, SSL, firewall
Errors visible early
Once you connect Sentry under Connections, production errors arrive
Ready for due diligence
Audit log, roles, access rights and deployment configuration answer the questions that come up in a data room.
AI agents that stay useful
The MCP server, the mp CLI and the VS Code plugin connect Cursor
Pipeline for Customer App
test
build
publish
release
Getting to your first release
The path is the same whether you are building a website or a mobile one.
-
Create the project
Pick name, platforms and stack in the wizard.
-
Connect a server
Use a managed server or attach your own over SSH.
-
Build the product
Work locally with the MainPath Toolbox or in a cloud workspace.
-
Ship it
The pipeline handles build, versioning and deployment.
Frequently asked questions
We have nobody doing DevOps. Is that a problem?
No, that is the case MainPath is built for.
Can we build web and mobile out of one project?
Yes. A project can contain frontend, backend
What happens when we grow quickly?
Pricing is a base price plus add-ons for extra users, workspaces and CI minutes, so you scale in small increments.
Does this help during due diligence?
It answers a meaningful slice of the technical questions.
Are we locked in afterwards?
The code is entirely yours. Repositories live in GitLab
Talk to the sales team
Tell us what you are building. We reply through the contact form.