Skip to main content
Mobius
Intermediate

What is deployment

Also known as: deploy, deploying, shipping code, going live

Definition

Deployment, or a deploy, is the step where a new version of a site or app goes live: the code is built, tested and moved to a server, with a quick way back.

Why it matters

Deployment is how every fix and feature reaches your customers, so a safe, routine process protects revenue and lets the team improve the product often.

Common mistakes

Deploying untested code straight to production, which can break the site for every visitor.

Related terms

Worked exampleIllustration

Changing the text on a checkout button

An online flower shop changes the text on its checkout button.

  1. Save

    The developer saves the change in Git, on a separate branch.

  2. Build and test

    The pipeline builds the site and runs the automatic tests.

  3. Preview

    A preview link, the staging copy, goes to the owner, who checks the button on a phone.

  4. Deploy

    The owner approves, and the change is deployed to production.

  5. Watch

    The team watches orders for the next hour.

  6. Roll back if needed

    If orders stop, one click restores the previous version while the developer finds the bug.

The deploy took minutes, and the safety came from the tests, the preview and the rollback.

Illustration

The road a change takes to customers

  1. Development

    Who sees it
    The developer
    Data
    Made up
    Payments and email
    Off
  2. Automatic testsStopped here: a test failed

  3. Staging

    Who sees it
    The team and the owner
    Data
    Test copies
    Payments and email
    Test mode
  4. Owner's check

  5. Production

    Who sees it
    Customers
    Data
    Real
    Payments and email
    Live

An automatic test failed, so the change stopped before anyone saw it. Nothing reached the private copy or the customers.

Deployment moves a change along this road. Each gate can stop it before customers see it.

The rollback lever

  1. Yesterday's version, orders coming in
  2. New button text deployed, orders stophas the bug
  3. Rolled back to yesterday's version
  4. The fixed version deployed

Live site works. One click restored yesterday's version. Orders flow again while the developer finds the bug in peace.

The checkout button change from the example. One click moves production back to the version that worked.

Definition

To deploy is to install a built version of the software in an environment, taking the code from the repository to a server, usually through an automated pipeline. The target can be staging, where the team checks the change, or production, where customers use it. Continuous integration builds and tests every change automatically, and continuous delivery keeps each version ready to go out at any time. Deploy is not the same as release: deploy puts the code on the server, release makes the feature available to users, which can happen later, for example when a feature flag is switched on for everyone. Every deployment needs a rollback, a way to restore the previous version within minutes. Teams use a few standard strategies: rolling (servers updated a few at a time), blue-green (a second copy goes live with one switch) and canary (the new version reaches a small share of users first).

Why it matters

DORA's research found that teams that deploy more often also have lower change failure rates, so small, frequent deploys are safer than rare, large ones. On a modern host a deploy is a button or an automatic push, and each change gets a preview link to check before it goes live. You can judge a team without reading code through DORA's five metrics: change lead time, deployment frequency and failed deployment recovery time for throughput, and change failure rate and deployment rework rate for instability.

Directly related: Staging, Production, Git.

Improvement tips

  • Automate deployments with a CI/CD pipeline, which reduces manual mistakes.
  • Put risky changes, such as database migrations, in quiet hours. Routine small deploys do not need to wait.
  • Make sure a rollback takes minutes and has been tried at least once.
  • Ask for a preview link for every change, so you see it before customers do.
  • Ask your developer four questions: how do we deploy, how do we roll back, who approves, and where can I see a change before customers do.

Common mistakes

  • Copying files to the server by hand, which is slow and easy to get wrong.
  • Having no rollback plan, so a bad version stays live while the bug is hunted.
  • Saving up changes for one big, rare deploy, which makes each one riskier.
Staging vs Production

Related terms

TechnologyIntermediate

Staging

Staging is a private copy of a website or app, kept as close to the live one as possible, where a change is checked before it reaches customers.

TechnologyIntermediate

Production

Production is the live version of your website or app, the one real customers use with real data. Any fault there costs sales, so it changes only after testing.

TechnologyIntermediate

Git

Git is free version control software: it saves a version of the code each time a developer commits, so you see who changed what and can go back.

TechnologyBeginner

Server

A server is a computer, or a program on one, that receives requests from other programs, such as a visitor's browser, processes them and sends back an answer.

TechnologyBeginner

Hosting

Hosting is a service that rents you space on a server connected to the internet all the time, so your website is available to every visitor.

Quick check

What is software deployment?

Choose an answer

Frequently asked questions

Do I need to understand deployment before I start my business?
You do not need the technical steps, but you should know that a deploy is how any change reaches your live site. It explains why an update goes through tests and a preview before customers see it, and it tells you what to ask a developer: how do we roll back?
When does deployment first become relevant for a new business?
When the first version of your site or app is ready to go live. A reliable deployment pipeline set up then means every later fix goes out quickly and the same way each time.
How do deployment choices affect my budget?
An automated pipeline takes some developer time to set up, so it adds to the first bill. It pays back in fewer manual errors, shorter outages and less time spent on each release. On many modern hosts much of it comes built in.
Should I use automated deployment or copy files by hand?
Automation is the better default for anything custom, because it builds and tests every change the same way and reduces human errors. A small WordPress or Wix site deploys through the platform's own tool, and that is fine.
Why does deployment matter for a business already running?
A structured process lets fixes and features reach customers without crashes, and lets the team ship small changes often. Teams that deploy often also break less, because each change is small and easy to undo.
What goes wrong when deployment is chaotic?
Outages after releases, missing files, broken links and a support queue full of complaints. Without a clear rollback, a bad version stays live while developers look for the bug.
How do I move to automated deployment without stopping day to day work?
A developer builds the pipeline and tries it on staging first, then connects it to the live site. The site stays up during the switch, and the old manual path remains until the new one has worked a few times.
How do I know if our deployment process is slowing the business down?
Warning signs: the site goes down with every release, fixes wait weeks for a release date, or developers are afraid to deploy on a Thursday afternoon. If they are, the process is the problem. DORA's metrics, such as deployment frequency and change failure rate, give you numbers to track.
What does deployment actually mean in plain words?
It means taking the new version of your site from the developers' code store and putting it on the server where it runs. It is like sending the final file to the printer: after that the new version is out, and a good process keeps the previous one ready in case of a mistake.
Is deploying updates to my website risky?
Every change carries some risk, but a staging check, automatic tests and a rollback that takes minutes keep it small. Frequent small deploys are safer than rare big ones, because each one changes less.
Do I need a developer to deploy simple changes to my site?
Content changes, such as a blog post or a price in your site builder, do not need a deploy at all. Code changes in a custom site go through a developer and the pipeline.
What is a rollback in deployment?
A rollback restores the last working version when a new deploy causes errors. It is the safety net that keeps the site working while the bug is fixed, and it restores code only, since data comes back from a backup.

Sources: DORA, Software delivery performance metrics guide (dora.dev/guides/dora-metrics), updated 5 January 2026, Nicole Forsgren, Jez Humble and Gene Kim, Accelerate, IT Revolution, 2018, CD Foundation, The DORA 4 key metrics become 5, 16 October 2025

Last reviewed: 2026-09-23

I have worked with

What Clients Say

From different fields, at different stages of business

Dan Manto

Eclipse Capital

Real Estate Investment and Finance, USA

Arty McLabin

GameReady

Game Development Education and Outsourcing, International

Anna, Beautician

Anna

Beautician

After I finished a cosmetology course at a leading company, I was confused. I didn't know how to open a business, what to sell from home, or how to bring in clients. Since I reached out to Mobius, everything has changed. We built an organized plan with clear steps and no unnecessary risks. Today I see results, and I'm growing and developing every month.

Mark, Massage therapist, Gan Yavne

Mark

Massage therapist, Gan Yavne

When I finished a massage course, I imagined a different world. I found out it's a hard field, and financial stability isn't easy to find. When I came to Mobius, something changed. We started an organized process and built a business plan. Without Mobius? I probably would have given up. Today I believe in myself and in my own path.

Tech decisions bigger than your team?

Alex helps Israeli businesses choose technology that fits the business, not the hype. The first call is free.

+972 055-248-6151. Better on WhatsApp: I am in meetings most of the day and answer as soon as I am free.