Getting started
Create your account, activate hosting, and deploy a supported Git repository or one-click application to a live domain.
Before creating a project, follow Prepare your app and the guide for your runtime. Each guide shows the files, lockfile, build rules, and app entry you need.
Prerequisites
- A supported Git repository for PHP 8.4, Node.js 24, Python 3.13, Bun 1.4, or static HTML, or an application available in the one-click catalogue.
- Access to the repository and its DNS zone.
- A payment method for a hosted plan.
Deploy your first app
Create the account
Select Create account. Complete Your name or company, Email, and Password (min 12 chars). The password needs at least 12 characters, an uppercase letter, a lowercase letter, a digit, and a special character.
Activate hosting
Open Billing. Under Plans, choose the hosted plan and select Subscribe. Complete checkout, return to the dashboard, and confirm Subscription status is
activeortrialing.Create the project
Open Projects and select New project. For your code, choose Source repository, enter the project name and Git URL, and leave Managed runtime on Detect from repository when its files clearly identify the stack. Set the branch if it is not
main; use Access token — leave blank for public repos only for a private repository. For a supported packaged app, choose One-click application… instead; its required services are created with the project. See project setup.Review the settings
For source projects, commit the required lockfile or static
index.html, and choose a runtime explicitly when auto-detection would be ambiguous. Add only the environment values your app needs. If your app needs a database or cache, add a service and connect it before deploying. Save any one-time credentials shown during one-click project or service creation. Leave advanced resource limits at their defaults unless your app needs a measured change.Run the release
Create the project, open its details, and select Deploy. Keep the deployment output open until the release is running or a failed phase shows what to fix.
Connect the domain
Point your domain at the hosting target shown by the project. A custom domain also needs a TLS certificate path: the recommended DNS challenge CNAME when offered, a project Cloudflare token, or an uploaded certificate. Select Check domain & TLS to review DNS and certificate readiness, then open the live domain. These checks warn during deployment but do not block a release.
What success looks like
Troubleshooting
Account creation is rejected
Check the email format and every password rule. If new registrations are unavailable, contact DeployGrove support.
Project creation or deployment is blocked
Open Billing. A missing, unpaid, past-due, or canceled subscription can stop project and deployment actions.
The repository cannot be read
Confirm the HTTPS URL, branch, and token access. See private repositories.
The build fails
Copy the failed phase and nearby log lines. Fix the repository or project settings, then select Deploy. Use Rebuild when you specifically need a fresh managed build; it requires privileged confirmation. Do not send repository tokens with a support request.
The domain check fails
Compare the shown DNS target with your DNS record and wait for propagation. Continue with domain troubleshooting.