Practice
Client-owned infrastructure
Most products run on third-party hosting. When a project of stature needs machines in the client's office, I design and build that internal stack. The client pays the compute cost. The client owns the machines. I do not host client work on servers of my own.
Inside an engagement
- An internal stack only when the written scope calls for it
- Machines and hosting the client pays for and owns
- Software on that stack, built for that one client
- Third-party tools where a private machine is not required
This is not the default, and it is not a server I rent out.