Source and environments
Versioned source, development and staging that match production closely enough to be useful, and a release path written down.
Company
Working infrastructure
Source control, environments, cloud hosting, security, backups and the access controls used on the job.
How we run the work
The system behind the product
Working infrastructure is not a photograph of desks. It is how we build, host and support your software: source, environments, cloud, backups, and who can touch what.
Repeatable development and staging sit beside the production environment agreed in the scope. Hosting is usually the client’s cloud or a named account we run for you. Architecture notes for your system are available.
Access is recorded. When someone leaves the job, their access is removed. You can have that list.
What this covers
Hosting and recovery
Cloud hosting, backups, and a restore path. We use the client’s cloud when that is already the right place.
Access and security
Named people, recorded access, and removal when the job ends. Firewalls and gateway controls on the systems we run.
Run after launch
Application maintenance, monitoring of what we agreed to watch, and a named path when something fails.
Highlights we will put in a scope
Licensed tools and current runtimes for the stack in the brief, not a pirated workstation image. Backups and a recovery path for the environments we operate. Client servers configured and maintained when that work is in the contract. Multiple environments rather than editing live as a habit. Virus protection and regular backup of project assets we hold. You can have the architecture notes for your system.
Layers we work with
The exact servers, networks, operating systems and databases follow the product. These are the layers we expect to name in a technical scope.
Application hosting
Web and API hosts, often on Azure or the client’s existing cloud, with a staging twin.
Network and access
Named accounts, VPN or IP controls where the brief needs them, and an audit of who can reach production.
Runtime
.NET, Node and the mobile runtimes the product actually ships on, kept current enough to patch.
Databases
SQL Server and other stores chosen from the data, with backups that have been restored at least once.
Continue
Also in company
Next step
Talk to the agency
Use the contact form for web, mobile or software enquiries. We reply within two working days.