Start from a prepared foundation
The appropriate template creates a repository, project structure and pipeline. Your AI agents get shared guidelines for working on the code.
Build with AI, review progress with your client and deliver the next version. MainPath keeps code, checks and releases together in the project – so the handover includes more than a working link.
From the first draft to the latest update, your code stays versioned. The team can see what changed and keep working from the shared project state.
Three building blocks for work your team can develop together and hand over with a clear history.
The appropriate template creates a repository, project structure and pipeline. Your AI agents get shared guidelines for working on the code.
Tests and builds accompany your changes. Try the result on Dev and review it with the client before releasing to production.
When several brands use the same product, manage branding and store listings as variants. Independent client products stay in separate projects.
Agree on what you are building, who will work on it and where the application will run. Start with a new project or supported existing code.
Work in the shared repository. Your agent helps with implementation; changes, tests and build results stay associated with the project.
Show the version in the development environment. Check the agreed features with the client, then decide whether to release to production.
Hand over code and configuration with the appropriate access. Agree who will own the accounts, credentials, future releases and ongoing operation.
Reuse does not mean sharing credentials or client data. Decide which parts can stay shared for each product.
Start with a manageable client project. Develop, check and deliver together – and agree on ongoing operation before the handover.
Yes, if the stack is supported. Your AI agent checks the existing code first and then guides the import. This does not automatically migrate arbitrary CMS or plugin setups.
The technical handover includes code, relevant configuration, required access and a clear release and operating process. Agree the rights to the application code in your client contract. MainPath does not replace that agreement.
No. Assign a suitable server to the project. Projects can deliberately share a machine or run on separate servers. Plan the separation of data and operations to fit the brief.
When several brands use the same product and shared logic. Branding, domains and store listings can then be managed as variants. Separate projects are often a better foundation for different requirements and independent development.
Trying a deployed web application does not require a MainPath account. Working on or managing the platform project requires an account with appropriate access. You implement sign-in for the application’s own users in the application code.