DeployGrove

Managed hosting for GitHub, GitLab and Bitbucket apps

Your server doesn't
deserve your weekend. Ship the app. Leave runtime and routing to us.

Connect a repository, choose a managed runtime and deploy from the dashboard. DeployGrove handles builds and routing, with private services, domain checks and supported recovery options.

Compare against a VPS
The DeployGrove deployment route A route connects a Git repository to a managed build, then to the DeployGrove runtime and a live app. Domain routing and TLS setup are available from the project. TLS + routing SOURCE Git repository BUILD Managed build RUN DeployGrove runtime LIVE Your application

The server was never the interesting part.

You build the app and choose its settings. DeployGrove maintains the supported build recipes, hosted runtime and routing. You still control repository access, environment values and DNS.

Three steps to your first deploy

Create a project, deploy it, then connect your domain. DeployGrove handles the supported build and routing; you provide the code, environment values and DNS records.

  1. Create your account

    Pick a hosted plan and create a project. Choose a source repository or a one-click application from the catalogue.

  2. Connect your repository

    For source projects, enter the HTTPS Git URL and let DeployGrove detect the runtime. Commit the required lockfile, or an index.html for a static site. Private repositories need a read-only access token.

  3. Deploy and connect your domain

    Select Deploy and watch the release in the dashboard. Point your domain at the server and choose an SSL certificate path. To deploy on later pushes, configure a signed Git webhook.

The platform work behind each deploy

DeployGrove maintains the supported build path, runtime and routing. You still choose your app settings, domain and data services.

Maintained build recipes

DeployGrove builds supported stacks with maintained recipes. You commit the required source files and lockfile instead of supplying a Dockerfile or custom image.

Repository → running app

A clear path to HTTPS

Point your hostname to the server and choose SSL validation. The domain check shows whether DNS resolves and a certificate path is available before you send visitors there.

Domain → HTTPS

Release history for recovery

Every release is tracked. Rollback is available for Node.js, Python, Bun and static sites; PHP apps need a new revision.

Failed deploy → release history

Private services for your project

Create a supported database, cache, search or messaging service in the project. Save its credentials and choose whether to inject the connection string or add it to the app environment yourself.

Service → app connection
Deploy from GitHub, GitLab or Bitbucket PHP 8.4Node.js 24Python 3.13Bun 1.4Static HTML

Prepare your app for its first deploy: check folder layouts, lockfiles, entry files, and health checks. Keep local app data with Persistent SQLite for PHP, Node.js, Python, and Bun, or connect a private database service.

The same app, with and without a server to look after

Compare the setup and ongoing work for one production app. Your code and data decisions stay yours in either case.

On your own VPSOn DeployGrove
Write and patch deploy scriptsDeploy from the dashboard
Hand-configure nginx and reverse proxyingRouting handled on deploy
Renew certificates and hope the cron firedDNS and TLS paths shown in dashboard
Track OS and runtime security updatesRuntime kept patched underneath you
Configure and test your own backupsConfigurable backups; restore on request
SSH in and reconstruct a broken deployRelease history and supported rollback
Infrastructure upkeepBuild, run and inspect in one place

Managed hosting with the work included.

Builds, runtime, routing and release history come with each plan. Choose the capacity your projects need, with extra resources priced before you add them.

Sapling

For the projects you want to ship and keep running without maintaining the server underneath.

$20per month

  • Run in productionUp to 3 apps
  • Each app gets2 vCPU · 2 GB RAM
  • Room per app20 GB storage · 1 TB transfer
  • When a deploy breaksRelease history; rollback where supported
  • If data goes wrongConfigurable service backups
  • Managed by DeployGroveManaged runtime and routing

Orchard

The same platform with room for a client roster, or a staging copy beside every project.

$40per month

  • Run in productionUp to 9 apps
  • Each app gets4 vCPU · 4 GB RAM
  • Room per app40 GB storage · 1 TB transfer
  • When a deploy breaksRelease history; rollback where supported
  • If data goes wrongConfigurable service backups
  • Managed by DeployGroveManaged runtime and routing

Both plans have a hard cap: at three apps you move from Sapling to Orchard, which supports up to nine. Extra databases, storage, bandwidth, CPU, and memory are priced before you add them.

Before you deploy

What do I need before my first deploy?

For source projects, have an HTTPS Git URL, a supported runtime and the required lockfile, or an index.html for a static site. Choose a one-click application if the app is in the catalogue. Add any needed service and environment values before deploying.

How do I set up SSL for my own domain?

Point the hostname to the server IP shown in the project. The preferred SSL setup is the _acme-challenge CNAME shown by Check domain & TLS, set to DNS only at Cloudflare. You can also use a project Cloudflare DNS token or upload a matching certificate. Deploy after the certificate path is ready.

What does DeployGrove manage, and what do I still configure?

DeployGrove is managed application hosting for supported Git repositories and selected one-click applications. It maintains supported build recipes, the hosted runtime and routing, and shows release output in the dashboard. You provide the code, repository access, environment values and DNS, and choose a supported TLS path for a custom domain.

Which Git providers can I deploy from?

GitHub, GitLab and Bitbucket. Public repositories need no access token; private repositories need a read-only token. Push-to-deploy requires a signed inbound webhook.

What does DeployGrove cost?

Sapling costs twenty US dollars a month for up to three apps. Each app gets 2 vCPU, 2 GB RAM, 20 GB storage and 1 TB monthly transfer. Orchard costs forty US dollars a month for up to nine apps. Each app gets 4 vCPU, 4 GB RAM, 40 GB storage and 1 TB monthly transfer.

Is 2 GB of RAM enough for my app?

Check the resource limits of the plan shown at checkout against your app and its build. Resource needs vary by stack and workload; do not assume a single memory size fits every app.

What happens when I reach the app limit?

Sapling supports up to three apps and Orchard supports up to nine. If you reach your plan limit, upgrade before creating another app.

Do the apps have to be related?

No. Projects can use different repositories, domains and environments. A one-click application can also create its required services with the project.

Can I use my own Dockerfile?

No. Source projects use supported managed runtimes and fixed build recipes. Repository Dockerfiles, custom images and custom start commands are not accepted.

Which languages and frameworks are supported?

Managed source supports PHP 8.4, Node.js 24, Python 3.13, Bun 1.4 and static HTML. Choose a supported Git repository or a trusted one-click application.

What happens if a deploy breaks the app?

Deployment history and logs show what failed. Node.js, Python, Bun and static projects can roll back to an earlier image. PHP projects must deploy a new revision.

Can I add a database?

Yes. Add a private service to a project, save the credentials shown at creation, and optionally inject its connection string as a secret environment variable. Deploy again after changing the app environment.

Your next deploy starts with a project.

Connect a supported repository, deploy from the dashboard and check your domain before launch. Managed builds and routing leave less infrastructure for you to maintain.