Skip to content

Glossary

What is on-premises deployment?

On-premises deployment is software running on infrastructure the customer controls. Where data goes and who can support it still depend on the contract.

Updated 21 Aug 2026

01

Where this one gets misread

On-premises is used loosely for a private tenancy or a dedicated instance in somebody else's data centre. Those differ in who can physically reach the machine and who is responsible when it stops, which is usually the reason the question was asked.

02

Questions to ask

Ask for a worked example on your own material, and the evidence needed to reproduce it.

  • Whose hardware, in whose building?
  • Who holds administrative access?
  • How are updates applied, and by whom?
  • What still calls out to the internet, and for what?
03

How Marella uses the term

We use “On-premises deployment” only where a product mechanism or an evaluation method backs it up, and we say when the behaviour depends on how a deployment is configured.

  • Backed by a product mechanism or an evaluation method
  • Deployment differences flagged

What this page does not prove

  1. B1A definition is not a claim about how the product performs.
  2. B2Vendor implementations vary.
  3. B3Test the term against a representative workflow.

Test the claim on your documents

Pick a real piece of work, agree what a good answer looks like, then go through the results together.