Every change has a history
Your code and changes live in the repository. Another person can follow how the tool has developed and continue the work.
A dashboard, an approval flow or a helper for everyday work: build what is missing with AI. MainPath gives your tool a project foundation and supports the steps towards sharing it with your team.
You know the workflow and your AI agent helps with the code. MainPath turns that work into a shared project, where you decide who can see it and keep developing it.
Start with one specific task your team deals with every day.
A purchase approval, a report or a data export? Decide what the tool needs to do and who will use it.
Create a project or have existing code checked for compatibility. A repository, structure and pipeline provide the foundation for your changes.
Connect a suitable server environment and make your web application available at an address. Gather feedback before releasing the next version.
Your code and changes live in the repository. Another person can follow how the tool has developed and continue the work.
Tests and builds run on every push. Spot problems before a new feature becomes part of the team’s daily work.
Project access, sign-in inside the tool and application reachability are separate decisions.
MainPath controls access to the development project. You implement user accounts, roles and sign-in inside your application.
MainPath can reach internal servers for setup and deployment through a network tunnel. Your network and application determine who can open the tool.
An existing GitHub or GitLab project can be the starting point. Your agent first checks whether its stack is supported for import.
Build the helper your daily work is missing. Start a new project or check whether you can keep building on the code you already have.
Yes, when its stack is supported. Your AI agent checks the existing code and guides the import into MainPath. For supported projects, your code remains the foundation.
No. MainPath accounts are for the people developing or managing the project. You implement sign-in and access rights for the actual users inside your application.
No. MainPath can reach servers behind a firewall through an SSH, WireGuard or OpenVPN tunnel. The tunnel enables setup and deployment; it does not replace access rules for your web application.
The tool is a project in your MainPath plan. The people working in MainPath and the resources you choose count towards usage. Hosting and other services depend on your configuration and plan.