Skip to main content
Deploy code to your pod by connecting a GitHub repository or any Git URL. Push to a branch and your code deploys automatically — with dependency installation, build commands, and deployment history.
Starting fresh? You don’t need to create the pod first. instapods deploy --repo <url> detects the stack, creates the pod, connects the repo, and runs the first build in one step — the same flow as the From GitHub option in the create-pod wizard and the “Deploy to InstaPods” button.

Quick Start

Connecting a Repository

GitHub Repository

Any Git URL

You can connect any publicly accessible Git repository:
For private repositories, provide an auth token:

Auto-Deploy on Push

When a repository is connected with auto-deploy enabled (the default), pushing to the configured branch triggers a deployment automatically. For GitHub repositories, InstaPods sets up a webhook that fires on every push. For other Git providers, you can configure a webhook manually using the URL shown in the dashboard.

How a Deploy Works

  1. Pull — The latest code is pulled from the configured branch
  2. Install — Dependencies are installed based on the preset (see below)
  3. Build — Build commands run if configured
  4. Restart — The application service restarts with the new code
The entire process typically takes 5-30 seconds depending on the size of your dependencies.

Skip a Deploy

Add [skip deploy] to your commit message to push without triggering a deployment:

Build Auto-Detection

InstaPods uses AI to analyze your project files and automatically determine the right install, build, and start commands for each deploy. This works for all presets and handles frameworks like Next.js, Vite, Django, Laravel, and more — without any configuration. The AI inspects files like package.json, requirements.txt, composer.json, framework configs, and your directory structure. It detects:
  • Install commandsnpm install, pip install -r requirements.txt, composer install, etc.
  • Build commandsnpm run build, framework-specific builds
  • Start commandsnode server.js, serve -s build, gunicorn app:app, etc.
  • App port — The port your app listens on
If AI detection is unavailable, InstaPods falls back to these defaults:
The AI auto-detection handles SPAs and frameworks that need a custom start command (e.g., serve -s build for Vite, node server.js for Next.js standalone). You don’t need to configure these manually.

Custom Commands

Override the defaults with a custom build command:

Check Git Status

See the current git configuration and last deployment status:
Output shows the connected repo, branch, auto-deploy setting, and latest deployment info.

Manual Deploy

Trigger a deployment manually, even if auto-deploy is off:

Deployment History and Logs

Every deployment is recorded with its status, commit, and build output.

View Deployments

View Build Logs

Rollback

Revert to a previous deployment:

GitHub Commit Status Checks

When deploying from a GitHub repository, InstaPods reports deployment status back to GitHub as commit status checks. You’ll see a green checkmark (or red X) on your commits and pull requests. This works automatically for public repositories. For private repositories, make sure the auth token you provided has repo:status scope.

Disconnect

Remove the git connection from a pod:
Disconnecting removes the webhook and git configuration. Your deployed code stays in the pod — nothing is deleted.

Full Example

Deploy a Node.js API from GitHub with auto-deploy: