Release state
The exact code, dependencies, checks, approvals, and changed surface that will actually ship.
Independent engineering assuranceJohannesburg · Worldwide
Know whether it is safe to ship—before your customers find out.
A senior, evidence-led review of the release you are about to make. You get the risks, the missing proof, the fixes that matter, and a decision your team can act on.
Accepting 3 launch audits at R7,500 each
The problem
Green CI is useful. It is not production proof.
Teams ship with passing checks and still miss stale approvals, untested failure paths, unsafe trust boundaries, deployment drift, or a rollback that exists only on paper.
Release Confidence examines the decision as a whole—not one test suite in isolation.
The flagship offer
The 48-hour Release Confidence Audit
One repository. One target release. One clear decision. Scope is confirmed before invoicing.
Architecture & security
Trust boundaries, permissions, secrets, data ownership, failure modes, and unsafe assumptions.
Proof quality
Tests, CI gates, deployment evidence, observability, rollback readiness, and hidden proof gaps.
Decision path
A prioritized fix list with clear owners, urgency, and a defensible ship, hold, or re-scope decision.
Fast engagements
Four ways to reduce technical uncertainty.
Start with the smallest engagement that answers the decision in front of you.
01 / Most direct
Release Confidence Audit
A focused, independent review before a consequential release, migration, or launch.
Request audit02 / Ongoing
Fractional Engineering Advisor
Senior release and architecture judgment for teams that need a regular independent checkpoint without a full-time hire.
Discuss advisory03 / Decision-led
Founder Technical Diligence
A plain-language view of product health, delivery risk, and technical debt before a hire, investment, acquisition, or pivot.
Scope diligence04 / Build & prove
AI Engineering & Delivery Sprint
Move one real workflow from opportunity to a working proof with evaluation criteria, guardrails, failure handling, cost visibility, and a practical rollout decision.
Scope an AI sprintHow it works
Fast enough for the release. Rigorous enough for the decision.
- 01
Brief
Send the release target, deadline, repository shape, and what must be true before you ship.
- 02
Scope
Receive a written boundary, access checklist, start time, and invoice—usually the same business day.
- 03
Audit
The exact release state is inspected and claims are tested against code, checks, and available runtime evidence.
- 04
Decide
Walk away with the decision pack, a findings call, and an ordered route to safer delivery.
Strong fit
You have a real decision and a real deadline.
- Founder-led or product engineering teams
- A consequential release, migration, or integration
- Uncertainty about whether the current proof is enough
- Willingness to expose risks and act on findings
Not the right fit
You only need a rubber stamp.
- A compliance certificate or formal penetration test
- A guaranteed “ship” answer before review begins
- Unlimited implementation inside a fixed audit fee
- Access to systems without an authorized owner
The operator
Independent judgment, close to the code.
I'm Rudi, a Johannesburg-based software engineering operator. My work sits where architecture, delivery, security boundaries, and production evidence meet. I turn ambiguous release risk into concrete findings and an executable next step.
View GitHub profile“Everything is uncertain until the evidence agrees.”
Release Confidence operating principle
Questions
Before you request a scope.
Is this a penetration test?
No. The audit reviews engineering and delivery risk, including security boundaries visible in the release. Formal penetration testing and compliance certification require a separate specialist scope.
Do you need production access?
Usually not. Read-only repository and CI access is enough to begin. Runtime evidence can be shared through redacted logs, screenshots, or a guided session.
Will you fix the findings?
The audit is independent and fixed-scope. A remediation sprint or fractional advisory engagement can be scoped after the findings, without locking you into ongoing work.
Can you help us deliver with AI?
Yes. The AI Engineering & Delivery Sprint takes one bounded workflow from opportunity to a working proof, with evaluations, guardrails, cost and failure analysis, and a rollout recommendation. It is engineering delivery—not a generic AI strategy deck.
What happens before I pay?
You send a short release brief. You receive a written scope, access checklist, start date, and invoice. Work begins only once scope and access are confirmed.
The next release is already moving
Get an independent answer before the decision gets expensive.
Request the auditWritten scope and invoice sent before work begins.