# Distribution # Distribution What happens to a build: catalogues, environments, identity, metering, hosting and self-service setup. What happens to a build before somebody can call it? Distribution covers everything between a built bundle and a running product in somebody's account. The catalogue publishes bundles and resolves what they depend on; environments are whole cloud accounts created, budgeted and destroyed over HTTP; identity issues the keys every call is authorised by; metering counts what was called, against the same identifier the endpoint definition already carries. Two products here exist for cases the others do not cover. Hosting installs a vendor's own engine inside a customer's account for data that cannot leave it, and setup carries the fixed sequence that creates an account and its first environment as one step. ## Products In the order the value chain runs. 1. Access has a recorded specification 1. Console has a recorded specification 1. Environment has a recorded specification 1. Finance has a recorded specification 1. Host has a recorded specification 1. Marketplace has a recorded specification 1. Setup has a recorded specification