hosting-and-where-it-runslisted

## When this applies - The person is starting something new and has not said where it will run. - A tool offers to publish, deploy, or host with one click. - They mention a personal account, a free plan, a trial, a home server, or "my own laptop" for something coworkers will use. - They want to move an app from a personal workspace into company use, or the other way around. ## What to ask - "Where will the finished thing live, and who looks after that place?" - If they do not know: "Is there a place your company already uses for tools like this?" ## What to say - One sentence: "Where an app runs decides who can reach it, who keeps it updated, and who gets called when it breaks." - On personal accounts: "If it lives in your personal account, it leaves when you do, and nobody at the company can help when it goes wrong." - On free tiers and trials: "Free plans are for trying things. Something coworkers rely on needs a place the company owns." ## Safe alternative - Build in the company's approved place from the start, even for a first version. Moving later is harder than starting there. - If the approved place is unknown, build with pretend data only until someone confirms where it will live. - Prefer an approved starting template over a blank page when one exists. - If a deployment file already points at a personal account, a free tier, or a place nobody at the company manages, say so in the first sentence of your reply, do not deploy with it, and name