Approach
How we work, and what we will not do
Handing a firm access to your production infrastructure is a real decision. These are the commitments we make so that decision is defensible.
Engagement sequence
Four stages with explicit gates
Small enough to understand, rigorous enough to operate. Scope, approval, and acceptance are visible before access is removed.
Four commitments
Nothing moves without a rollback position
Every change we make to a running system has a defined way back. Before a migration step, a DNS cutover, or a pipeline change, we know exactly how to reverse it and we have verified that path. Reliability comes before elegance.
Your team owns the result
We do not build systems that only we can operate. Engagements end with documentation, runbooks, and infrastructure defined as code in your repositories under your accounts. If we walk away, nothing stops working.
You keep the keys
Cloud accounts, domains, repositories, and billing stay in your name. We work inside access scoped to the engagement, with least privilege, and that access is revoked at handoff. You should never need our permission to run your own platform.
Bounded scope, written down
Engagements have a defined scope, defined deliverables, and stated exclusions before work starts. We would rather turn down work that does not fit than sell an open ended retainer nobody can measure.
Operating practices
The specifics a technical buyer will ask about on the first call.
Access and credentials
We work inside access scoped to the engagement, under your identity provider, with multi factor authentication required. Credentials are never shared over email or chat. Access is enumerated at the start of an engagement and revoked at handoff.
Account and code ownership
Cloud accounts, domain registrations, container registries, and repositories are created in your name and stay in your name. We do not hold your production infrastructure inside a Redmanh account, because that turns a vendor into a hostage situation.
Change management
Infrastructure changes go through pull requests with a plan output attached, so a reviewer sees what will change before it changes. In environments with their own change control process, we work inside that process rather than around it.
Backup and restore
We verify restores rather than trusting that backups exist. An untested backup is a belief, not a control. Where we find no tested restore path, that is written into the assessment as a finding.
Documentation and handoff
Every engagement produces architecture documentation and runbooks written for your engineers. The measure of a finished engagement is that your team can operate the system without calling us.
Subcontractors and coverage
If an engagement requires capacity beyond our own, we say so before signing rather than quietly subcontracting. You will always know who is touching your systems.
How an engagement starts
- 1
You describe the problem
Send the shape of what is breaking or what you are about to build. No form filling marathon.
- 2
A scoping conversation
Thirty to sixty minutes on your current setup, constraints, and what a good outcome looks like. If we are not the right firm, we say so here.
- 3
A written scope
Deliverables, exclusions, timeline, and price in writing before anyone touches a system.
- 4
Delivery and handoff
Work delivered against that scope, ending with documentation and revoked access.
About Redmanh LLC
Redmanh LLC is a Maryland limited liability company. We are a deliberately small platform engineering practice. That is the model, not a stage we are trying to grow out of, because it keeps the people who scope the work as the people who deliver it.
We build and operate our own software products, which is where our infrastructure practices get tested first.
- Entity
- Redmanh LLC, Maryland
- Office
- 801 Caslon Way #205
Landover, MD 20785 - Engagement model
- Project based, assessments, and defined support windows