Choose one workload
Name the application or workload and its technical owner. We confirm fit and the review boundary, including what falls outside the free engagement.

Free · AWS Well-Architected Review
One AWS workload, reviewed against the six Well-Architected pillars. A ranked fix list and an engineer walkthrough. tMinus1 pays for the review; you keep the findings.
An engineering review, not an accredited assessment or certification. No AWS funding: tMinus1 pays for it.
A review against the six pillars.
Recommendations ordered by consequence.
Discuss the findings with an engineer.
An engineering review of one AWS workload against the six Well-Architected pillars. We connect the configuration to the way your team runs the system and give you written findings, priorities and a walkthrough.
Name the application or workload and its technical owner. We confirm fit and the review boundary, including what falls outside the free engagement.
Create scoped read-only access or arrange a screen-share alternative. Share architecture information and the concerns you want the review to address.
Review configuration and meet with the technical owner to understand decisions, dependencies and operating practices. Note any evidence gaps that limit a conclusion.
Receive the document and an engineering walkthrough. Discuss priorities and ownership. Timing depends on access and availability; a typical review is planned over approximately two weeks.
The framework provides the structure. Your workload provides the context: what it needs to do, what happens when it fails and which trade-offs your team has made. We use the discussion to investigate risks and improvement opportunities.
Review deployment practices, useful telemetry, response procedures and ownership. Discuss who finds out when the workload fails, what information they receive and how they restore service. Identify the gaps between documented process and day-to-day operation.
Work through identity, permissions, trust relationships and the handling of sensitive information. Discuss how access is granted and removed, which records are available and where a compromised identity could affect the workload.
Discuss dependencies, failure points, backups and recovery expectations. Review what has been tested and what remains an assumption. Connect recommendations to the business purpose of the workload and the recovery decisions its owners need to make.
Review the resource choices and demand patterns your team can explain. Discuss bottlenecks, measurement and the conditions under which the architecture needs to change. Recommendations consider service expectations and implementation effort.
Look at resource use, ownership and the relationship between spend and demand. Discuss idle capacity, sizing and scheduling opportunities where evidence is available. A deeper financial analysis can be scoped separately if the workload needs it.
Discuss utilisation, data lifecycle and opportunities to avoid unnecessary work. Consider efficiency alongside performance, reliability and operational constraints, rather than treating resource reduction as a decision in isolation.
Each item follows the same four steps, from evidence to a decision. This is an illustrative structure; real findings depend on the agreed scope.
Record the configuration or operating practice and the evidence available.
Explain how the issue could affect this workload, including assumptions or missing context.
Describe a practical next step and the dependencies or questions to resolve.
Discuss consequence, effort and ownership with your team so the findings become an actionable plan.
Illustrative structure, not customer findings or a completed engagement.
Your team keeps the written findings, the priorities and the context to decide what happens next.
Keep the findings against the six pillars, with context on the evidence and limitations of the review. The document belongs to your team and can support internal planning conversations.
Understand which issues deserve attention first and why. The recommendations separate the observed concern from the proposed engineering response, making it easier to discuss scope and assign ownership.
Discuss the findings with the people responsible for architecture and operation. Ask questions, challenge assumptions and work through the first actions rather than receiving a document without explanation.
Your team can implement the recommendations internally or ask us to scope engineering work. The free review does not require you to purchase implementation or commit to continuing support.
The review gives you an informed engineering view of one workload. Defining its boundary keeps the findings useful and makes the access requirements easier to control.
Choose the workload that matters most: a service approaching launch, an existing application with reliability concerns or a system your team wants to understand better. A whole-estate programme is a separate scope.
We agree the configuration and findings information needed before starting. You create and revoke the role. The review does not install agents or make infrastructure changes; a screen-share approach can be discussed if direct access is unsuitable.
This is our engineering review using the AWS Well-Architected Framework. It is not an accredited assessment, certification or audit. It carries no AWS funding or credits. tMinus1 pays for the review.
Configuration explains only part of an architecture. The technical owner helps connect the workload to its purpose, constraints and the way it behaves in practice.
Describe who uses the service, which systems it depends on and what matters when it is unavailable. Existing diagrams are useful; missing documentation should be flagged rather than invented.
Share known incidents, recovery expectations, deployment practices and current concerns. Distinguish what has been tested from what the team expects to happen.
Allow time for the technical discussion and findings walkthrough. We agree confidentiality and can sign an NDA before starting. Review availability is limited by engineering capacity and confirmed when you enquire.
An AI feature inherits the workload under it: who can reach the data, what fails under load and what it costs to run. If you plan to put AI on an AWS workload, the free review is a practical place to start. It covers one workload, AI or not.
See AI deliverytMinus1 built Automatum, a multi-tenant platform with marketplace integrations and metered billing. That platform work informs how we approach identity, integration, deployment and operational ownership.
Platform engineering experience. The case study is not a claimed result from this service.
PLATFORM CASE STUDYAutomatumExplore the engineering and operations ↗Discuss anything specific to your team or environment.
You spend about three hours with us and we learn whether we would be useful to each other. If the review turns up work you want done, we will quote it. If it does not, you keep the document and we part on good terms. There is no fee and no follow-up sequence.
It uses the AWS Well-Architected Framework and its six pillars, and we are an AWS Advanced Tier Services Partner. It is our own engineering review against that framework. It is not an accredited assessment and it carries no AWS funding, credits or certification. If you need the funded program, say so and we will tell you honestly where we can and cannot help.
A read-only role scoped to the workload, which you create and revoke. We install nothing, we write nothing, and we agree what configuration and findings information is needed before starting. If read-only access is impossible, a screen-share session works, and the review takes a little longer.
You and us. We do not publish it, we do not use your name in marketing without written permission, and we will sign your NDA before we start if you want one.
The free review covers one. Pick the one that worries you most. A whole-estate review is real work and we quote it as such.

We’ll confirm fit and arrange the review. Implementation is separate and optional.
Request your free review