# What is an operating partner, and how is it different from a vendor that delivers and leaves?

An operating partner keeps running a system after it ships: watching it, changing it as the company changes, and re-setting it when a part underneath moves. A vendor that only delivers hands over the code and leaves, which means the company owns every future break alone. The difference shows up the day something needs to change.

Checked: 2026-09-27

In one line

Runs the system after it ships, instead of handing it over.

## Why it matters to you

The test is what happens on day one after launch. A vendor's contract ends at delivery, so any change becomes a new negotiation. An operating partner's does not: the same people who built the system are the ones who watch it, and a change is routed through the relationship that already exists.

This is also why rollback and monitoring are answered before launch, not discovered after: a partner that is still there when a build breaks has already worked out how it finds out and how it reverts.

## What it is not

An operating partner is not a retainer for occasional support calls. It runs the system day to day, the same way it was built, and re-sets it as the company or the models underneath it change.

## Next to this

- [Rollback](https://octyn.co/glossary/rollback)
- [Observability](https://octyn.co/glossary/observability)
- [Total cost of ownership](https://octyn.co/glossary/total-cost-of-ownership)

## Argued out at length

- [Alternatives to hiring for operations](https://octyn.co/compare/alternatives-to-hiring-for-operations)

## Related

- [Alternatives to hiring for operations](https://octyn.co/compare/alternatives-to-hiring-for-operations)
- [Rollback](https://octyn.co/glossary/rollback)
- [The Consult](https://octyn.co/consult)

Canonical: https://octyn.co/glossary/operating-partner