From local dev to production in moments: using Upsun CLI and API for fast delivery loops

For most developers, the terminal is where real work happens. While web UIs look polished, most developers prefer the command line for speed and control. However, the path from a local change to a real, production-like environment is full of friction.

Tickets, YAML edits, console clicks, waiting for pipelines, re-running jobs.
All before you even know if the change works.

Upsun CLI and API to shorten this loop. Push from your terminal, trigger deployments, manage environments, and integrate with any CI/CD pipeline, all without context switching or learning proprietary tools.

Deployment workflow problems developers face

Many platforms promise developer-friendly experiences but deliver the opposite:

• Context switching kills momentum. You're writing code in your editor, checking status in the browser console, reading documentation in another tab, and troubleshooting in yet another tool. Each switch costs time and mental energy.
• Custom workflows create vendor lock-in. Proprietary CLIs, specialized deployment tools, and platform-specific integrations mean your team learns systems that don't transfer to other projects. Change platforms? Start from scratch.
• Manual steps introduce errors. Click through the console to deploy. SSH into servers to run migrations. Check logs in separate dashboards. Miss one step and deployments fail at 3am.
• Environments drift by default. Local development uses Docker. Staging runs on a different infrastructure than production. Each environment has slightly different configurations. Bugs appear in production that never surfaced in testing.

The result? Developers spend more time managing infrastructure than building features. Stack Overflow survey found that developers spend over 30 minutes daily just searching for solutions to deployment and infrastructure issues.

Upsun's approach: extend your workflow, don't replace it

Upsun treats your terminal and existing CI/CD pipelines as the primary interface. Everything available in the web console is accessible via CLI or API.

Terminal-first deployment

The Upsun CLI wraps Git commands you already use. Pushing code automatically triggers builds, activates environments, and syncs data. One command replaces multiple manual steps.

Push a new feature branch, and Upsun instantly creates a live environment with a clone of production data. Share the URL with stakeholders for review. Merge when ready. The environment auto-deletes on merge. No tickets, no waiting, no manual cleanup.

The CLI auto-detects which project and environment you're working in based on Git context. No configuration files to maintain or project IDs to memorize.

API access for any integration

Behind every CLI command is a REST API endpoint. Authenticate once with an API token, and you can:

• Automate deployments from any CI system
• Build custom tooling for your team
• Integrate with internal monitoring systems
• Script complex workflows across multiple projects
• Trigger operations from webhooks or scheduled jobs

The API uses standard OAuth2 authentication and returns HAL-formatted JSON. Any HTTP client works, no proprietary SDKs required.

Infrastructure as code that actually works

Configuration lives in your Git repository as YAML files. Define applications, databases, caches, routes, and deployment hooks in one place. Branch your code and the infrastructure branches with it.

This isn't theoretical infrastructure-as-code. It's practical: branch a feature and get a complete clone of the production application, PostgreSQL database, Redis cache, and environment variables. Test against the real stack, not mocked services.

When you merge the branch, the infrastructure is automatically removed. No orphaned resources, no surprise cloud bills.

How teams actually use this

Fast feedback loops without CI complexity

Traditional approach: push code, wait for CI to build, manually deploy to staging, test, repeat. Each cycle takes 10-15 minutes minimum.

With Upsun, push creates a live environment immediately. Run tests against the actual deployed application and services. See failures in context, fix them, push again. Cycle time drops to seconds instead fo minutes.

The CLI can return environment URLs instantly. Share them in pull requests. Designers review actual UI. Product managers test features. Stakeholders approve before merge. Feedback happens on real deployments, not screenshots.

CI/CD that works with any platform

Most platforms lock you into their CI system or require complex integrations. Upsun works with GitHub Actions, GitLab CI, Bitbucket, or any CI/CD system that can run bash commands and install the Upsun CLI.

Install the CLI in your pipeline, authenticate with a token, and run deployment commands. The same script works across platforms. Switch from GitHub to GitLab? Update the token; everything else remains the same.

Testing against production-like data safely

Development environments need realistic data to catch bugs. But production databases contain sensitive customer data that you can't expose across multiple environments and access points.

Upsun clones production data to preview environments automatically, then runs sanitization scripts during deployment. Developers get realistic test data without accessing sensitive information. Environment variables control when sanitization runs, so production stays untouched.

Observability without additional tools

The CLI exposes logs, metrics, and performance data directly in your terminal. Stream application logs while developing. Check CPU and memory usage before scaling decisions. Profile critical endpoints to find bottlenecks.

For PHP and Python applications, Blackfire APM integration is included. Profile any endpoint from the command line, compare performance between branches, and fail CI builds when performance degrades. No additional instrumentation or third-party services required.

Getting started takes minutes

1. Install the CLI: Use the Bash installation script. You can also install using Homebrew (macOS/Linux) or Scoop (Windows). One command gets you running.
2. Authenticate: Run the authentication command. It opens your browser to log in and automatically configures SSH access for your deployments.
3. Initialize your project: Run upsun init from your existing code repository. Choose between an AI-assisted setup or a guided configuration. The CLI detects your language, framework, and dependencies, then generates a starter configuration file.
4. Deploy: Commit the configuration, push your code, and watch your application go live. The entire onboarding takes less time than most cloud provider sign-up forms.

For teams with existing infrastructure, migrate incrementally. Run Upsun alongside current systems, move projects one at a time, and validate that workflows improve before committing fully.

The core difference

Most platforms add layers: custom interfaces, proprietary tools, platform-specific workflows. Each layer promises to simplify but actually introduces complexity and vendor lock-in.

Upsun removes layers. It extends Git and your terminal with deployment automation. The CLI speaks the same language as your existing tools. The API integrates with any system that makes HTTP requests.

Your workflow stays familiar. Git commits trigger deployments. Environment variables configure applications. SSH provides direct access when needed. The difference is speed and automation, not wholesale replacement.

What this means for your team

Faster deployment cycles mean faster feedback. Faster feedback means fewer bugs reach production. Fewer production bugs mean fewer emergency fixes and late nights.

Terminal-based workflows keep developers in their tools. Less context switching preserves flow state. Better focus leads to higher-quality code.

Automated environment management reduces DevOps burden. Platform engineers can focus on architecture instead of provisioning infrastructure. Developers can experiment without creating technical debt.

The compounding effect of small efficiency gains—60 seconds instead of 15 minutes, one command instead of six clicks, automatic cleanup instead of manual tickets adds up to significantly more time building features customers care about.

Try it yourself

The fastest way to understand is to experience it. Create an Upsun account, point the CLI at any Git repository, and push. Watch a production-grade environment appear in moments.

Explore further

• See the Upsun CLI in action
  Complete command reference, installation guides, and authentication setup for terminal-based deployments.
• Read the API documentation
  REST API endpoints, authentication methods, and integration patterns for automating deployments with any CI/CD tool.
• Explore CI/CD integration examples
  See how Upsun works with GitHub Actions, GitLab CI, and other pipeline tools to automate your delivery workflow.