Servers & infrastructure
Servers and infrastructure, architected and built.
Enterprise servers and infrastructure — architected, set up, deployed, configured and made resilient. From the target design and the decision records to the build itself and the HA/DR that keeps it standing, engineered by a senior engineer and handed over as systems and documents you own.
Engineering with a defined end — delivered and handed over, not run as a helpdesk. Independent of any vendor, with nothing to resell you.
How the work runs
Design, build, prove, hand over.
Whether the entry point is a review or a full server build, the work follows the same arc.
- 01
Map the estate
A current-state baseline of what actually runs today: systems, dependencies, single points of failure and the gap between documented and real.
- 02
Design the target
Reference and target-state architecture, resilience and HA/DR design, and a capacity plan sized to where the business is going — with Architecture Decision Records capturing what was chosen and why.
- 03
Build & deploy
Servers and environments set up, deployed, configured and hardened against the design — the actual build, not just a diagram of it.
- 04
Prove & hand over
HA/DR tested against RTO/RPO, runbooks written, and a documented handover with training so your team runs it — not us.
What you get
Systems and documents you own.
Every engagement ships working infrastructure and named artefacts, not advice alone.
- Current-state baseline — systems, dependencies and single points of failure, documented
- Target-state architecture & ADRs — the design, and the reasoning behind every choice
- Set-up & deployed infrastructure — servers and environments built, configured and hardened to the design
- HA/DR design & runbooks — RTO/RPO targets, standby pattern, and tested recovery procedures
- Capacity & migration plan — sized against forecast growth; sequenced migration with rollback where relevant
- Handover pack — documentation and training so your team, or your MSP, runs it independently
Scope
Engineered and handed over — not an IT-support desk.
We design, set up, deploy and harden the infrastructure, then hand it over documented for your team or MSP to run.
Out of scope — day-to-day operations: desktop support, a helpdesk, ticket queues, and open-ended managed-operations retainers. The work is engineering with a defined end — a review, a build, a migration — not an ongoing support contract. Follow-on support is available if you want it, but it is optional and never a lock-in.
From the design to the build, engineered.
Start with a review or take on a server build or migration. A short discovery call, then a scoped plan.
FAQ
Servers & infrastructure, answered.
Do you set up and deploy servers, or only design the architecture?
Both. 1722 designs the target architecture and builds it — server and environment setup, deployment, configuration and hardening — then proves the resilience and hands it over documented. You can take the design to your own team, or have 1722 do the build; it is scoped either way.
What do I actually get at the end of an engagement?
Working systems and named artefacts, not a slide deck: a current-state baseline, a target-state architecture with Architecture Decision Records, the servers and environments set up, deployed and configured, an HA/DR design with RTO/RPO targets, standby pattern and tested runbooks, a capacity plan, a migration plan where relevant, and a handover pack with documentation and training. All of it is yours to run with any team.
Is this an ongoing managed-services or IT-support contract?
No. This is engineering work with a defined start and end — design, build, deploy, prove, hand over. It does not include day-to-day desktop support, a helpdesk, ticket queues, or an open-ended managed-operations retainer. Your team or an MSP runs the estate day to day; 1722 engineers and hardens it.
Are you neutral on vendors and systems integrators?
Yes. 1722 sells no infrastructure product, hardware, licence or cloud-reseller margin, and takes no vendor or SI commission. Technology selections are scored against your requirements and total cost of ownership, not a partner relationship — so the build follows the problem.
How is an engagement scoped?
Often a fixed-scope entry piece first — an Infrastructure Review or a Resilience & DR Assessment — priced and timeboxed from a written statement of work. A build, deployment or migration is then scoped from that, on a day-rate or fixed-scope basis. You are never committed to the build to get the design.
What is the difference between HA and DR here?
High availability (HA) keeps a system running through a component failure inside a site — redundancy, failover, no single point of failure. Disaster recovery (DR) is the plan and standby capacity for recovering after the loss of a site or a major failure, defined by RTO and RPO targets, a standby pattern (pilot-light, warm or hot) and a tested runbook. Most estates need both, designed and built together.
Who typically commissions this work?
IT Directors, Heads of Infrastructure, CTOs and enterprise or solution architects — ahead of a funding decision, a server build or migration, or a resilience gap flagged internally or by audit.