Software deployment and infrastructure
“It works on my laptop. Now what?”
From local build to live software
Your software needs to run somewhere your users can reach it. I help choose suitable hosting, configure the application and connect the domain, with a release process you can understand and use again.
Your laptop deserves to stop being the production server.
Tell me the problem. I'll explain the possible approach and the next step, before any work is agreed.
What you get
- Hosting and runtime configuration for the application
- Domain, DNS and HTTPS setup
- Environment configuration and deployment workflow
- Release verification and operational handover
My stack
Jack of all trades. Master of none.
Still shipping the whole fucking thing
Before you hire me
The practical details, before a project becomes a project.
Do I need all the content ready?
Bring what you have: the problem, any existing site or tool, and the content you already use. Before work starts, I identify what is missing and agree who supplies copy, images and other assets. Copywriting and custom illustration need their own agreed scope.
Do I get the source code?
Source handover is part of the service. Before starting, I agree the deliverables and ownership terms, including any third-party software or assets with their own licences.
What costs continue after launch?
Depending on the project, domains, hosting, business email, paid services and AI usage may have recurring costs. I identify the services the project needs and discuss those costs separately from the build before agreeing the scope.
What about maintenance and later changes?
I discuss maintenance and handover before launch. Support, new features and changes beyond the agreed scope are quoted separately; ongoing support is something to agree, rather than assume.