A deployment stamp is a complete, repeatable copy of an application's infrastructure, deployed for one tenant or a group of tenants. Instead of one large shared system, a provider builds the same self-contained unit several times and assigns customers to units. It is sometimes called a cell.

It matters because it offers a middle path between shared and fully separate deployments. A problem in one stamp affects only the customers in it, capacity can be added by creating another, and a customer with special requirements can have its own, such as one in a specific region.

It adds operational work. Many stamps have to be deployed, updated and monitored, which needs strong automation, and moving a customer between them can be complex. The approach does not remove the need for isolation within each stamp if it hosts several tenants.

When considering it, automate the deployment of a stamp end to end, decide how customers are assigned and moved, and monitor each stamp separately so that a problem can be found and contained quickly.