Infrastructure assessment
An infrastructure assessment for companies across the U.S.
We write how work moves through the identity, the network, and the platforms you already run, and where a person is covering a gap by hand. Based in Utah. Engagements are remote-first across the U.S., and on-site travel is available. We work around your normal operations, and we'll need access to the right areas and the right people while we do.
When a company asks for one
After a merger, an acquisition, or a platform change. A second site running a second week. Leadership and the floor disagree about the same system. The invoice and the tools have drifted.
Text the stuck path and the system it depends on. After two companies join is the same kind of work when a deal or a cutover is the reason.
Identity, network, and platforms
The assessment looks at identity, the network, and the platforms in use. Tools, access, and records. What the stack costs. One standard at every site, with room for what is truly local.
We work with what you already use. A second platform on the same job is a finding. We replace a system only when the record cannot carry the work.
Capacity, resilience, and a restore
Infrastructure work is also the foundation under ISO 27001 readiness and under a penetration test. Capacity, resilience, backup, and recovery are reviewed because a control that depends on a host, a network path, or a restore point fails when that foundation fails.
We look for defined capacity for the on-premises, hybrid, and cloud systems the facility actually runs, and for a named owner when that capacity is exceeded. Resilience is whether the service holds and who is called when it does not. Backup is not treated as complete until a restoration test has been done and the result is recorded.
Logs, tickets, and the last restoration test are part of that record, with the date and the person who ran the test. A diagram that does not match the cables, accounts, or cloud subscriptions in use is a finding, not documentation. We'll need access to whoever runs the restore and whoever owns the platform.
One job, start to finish
You name one job: an order, a ticket, a hire, a change. We follow it, including the side path the official process omits.
- Where the request starts, and which system records it.
- Who touches it, and who believes they own the outcome.
- Which step is done by hand because two systems disagree.
- What access that step requires, and whether it is shared.
- What would stop if that system were down tomorrow, and who would notice.
- Which other product claims to record the same job.
That path is the infrastructure assessment. A catalog of servers with no path is not. We'll need access to the path and the people who walk it.
The written account
You receive what holds, what disagrees, and the order to close it. We write the scope before the work starts. Once you approve it, we'll need access to the right areas and people. You keep the owners, the reviews, and the record.
The map is the path people use. The name is the owner. An unused diagram is not the deliverable.
The bill on the same account
A platform nobody owns still sends a bill. Seats for people who left, and a second tool on the same job, belong on this account. Cloud cost starts from the invoice. The deeper cloud-cost practice is Coalesce Ops.
Shared admin access with no owner is both an infrastructure fact and an access fact. SOC 2 readiness starts from the control.
Contact
Text the stuck system.
Tell us which path is stuck. Engagements are remote-first across the U.S., and on-site travel is available. We work around your normal operations, and we'll need access to the right areas and the right people while we do. If it is not a fit, we say so.