REKKY first. Mission complete.
Platform operations
It's done.
How a change gets to production, which environments no longer match, and which platform chores have no owner. A working path, not a catalog of machines.
The path, not the inventory
Platform operations here means the system that lets a product change reach production and stay understandable. The engagement follows one change. Where it starts, what builds it, where it waits for a person, which environment it lands in, and who can undo it. A list of servers with no path through them is not the deliverable.
Drift is part of the same walk. Staging that is not production, a region that was an experiment and is now load, a configuration file that exists in three forms. The finding is the difference that can change a release, not every difference that exists.
This replaced the older infrastructure-assessment page on this site. The work is narrower on purpose. Security consulting for the company is the parent firm, REKKY Consulting LLC.
What we look at
We look at the tools you already use to build and ship. Source, the pipeline, the artifact if there is one, the place the artifact runs, and the account that can change that place. We look at who has that access today and who still has it from a project that ended.
We look at the platform backlog as the product teams experience it. Tickets, chat threads, and the recurring favor: a database, a queue, a certificate, a new environment. If the favor is how the platform actually runs, the backlog should say so, with an owner.
- One change, from merge to production, with the people who did it.
- The environment you test in, compared with the one you serve.
- Access that can still change production, and access that should not.
- Platform favors that have never been written down as work.
Handoffs inside the path
A path usually breaks at a handoff. Development thinks the pipeline is the platform team's. The platform team thinks the service owner will watch the deploy. Nobody is wrong in the abstract, and the release still waits. The engagement names the handoff and gives it one owner for the steps that stall.
We do not add a meeting to represent the handoff. If a working session is required to see a real deploy, the scope says when, and it sits inside the week you already run. We run the engagement end to end and work around your normal operations, but we'll need access to the right areas and the right people while we do.
What you receive
A written path, the drift that matters, the access that is too wide or too thin, and an ordered backlog. What is already sound is included, so the next quarter does not rebuild a pipeline that works.
You keep the notes. A follow-on fractional DevOps period can execute the backlog, and that period is a separate scope. The Recon Assessment, starting at $15,000 plus expenses, can be the four-day version of this look when the path, the on-call, and the bill need to be in one report.
We will not recommend a new platform because it is newer. A replacement is on the table only when the current path cannot carry the release. The choice to switch stays with you.
Questions on this work
Is platform operations an infrastructure assessment?
It is a look at the path a change takes to production, the environments that have drifted, and the platform backlog product teams are covering by hand. Security consulting for the wider company sits with the parent firm.
What do you need from the team?
Access to the pipeline, the environments, and the people who approve a release. We schedule that around the week you already run. A diagram with no one who can open the pipeline is not enough.
What do we leave with?
A written account of the path, the drift, the owners, and the order in which to close the gaps. The record stays with you.
Contact
Describe the platform you have.
Point us at one change that was hard to ship, and at the person who can open the pipeline. We run the engagement end to end and work around your normal operations, but we'll need access to the right areas and the right people while we do.
Recon Assessment, starting at $15,000 plus expenses. Four days on site with your team, then a written report within about two weeks.