My blocks.cloud review examines the product, workflow, pricing approach, implementation demands, risks and best-fit buyers.
By Tolu S.5 min readBlocks focuses on AWS cost optimisation and agentic DevOps service.
My short take: The interesting question is whether AWS savings survive the commitment terms and the operational changes needed to obtain them. A discount can be expensive if usage falls, ownership is unclear or an automated change creates an outage.
| Question | Answer |
|---|---|
| What is it? | AWS cost optimisation and agentic DevOps service |
| Best for | growth companies with meaningful AWS spend and willingness to transfer billing |
| Less suitable for | Azure or GCP users and teams unwilling to alter their AWS billing relationship |
| Pricing | Sales-led unless stated otherwise below |
| Review access | Public-evidence first look; no authenticated workspace |
| Main buying test | Prove accurate, governed outcomes on representative work |
The product is designed around five buyer jobs:
The interesting question is whether AWS savings survive the commitment terms and the operational changes needed to obtain them.
The product material in the source record describes the following areas. I would evaluate them as a connected workflow, not assume that a named feature proves an operational result.
The interesting question is whether AWS savings survive the commitment terms and the operational changes needed to obtain them. A discount can be expensive if usage falls, ownership is unclear or an automated change creates an outage.
A discount can be expensive if usage falls, ownership is unclear or an automated change creates an outage.
Pricing evidence was recorded on 20 July 2026. The figures and plan descriptions below are historical research, not a newly verified quote. Confirm current terms with Blocks before budgeting.
Blocks describes success-based fees on realised savings rather than a conventional subscription. Contract terms govern the percentage, commitments and one-off actions.
Blocks is best suited to growth companies with meaningful AWS spend and willingness to transfer billing.
It is less suitable for Azure or GCP users and teams unwilling to alter their AWS billing relationship.
I would use one AWS account with a documented billing baseline and no authority to change resources during the initial review. I would ask for the proposed discount or commitment terms, compare the outcome under falling as well as rising usage, and examine one reversible optimisation through the normal infrastructure review. Savings would count only after the bill, performance and commitment exposure were reconciled.
| Alternative | Consider it when |
|---|---|
| An established category incumbent | Procurement favours maturity and a broader ecosystem |
| A specialist point solution | One narrower capability matters more than platform breadth |
| An internal build | Control and proprietary workflow are strategic |
| A services-led provider | Expert execution matters more than software ownership |
| The current process | Volume and expected benefit do not justify migration |
Before adding Blocks to a shortlist, I would write down the job, the current alternative and the evidence needed to justify a change. Our guide to a requirements-first approach to choosing AI tools.
For Blocks, I would also count the existing tools, review time and operating work that remain after adoption. Our guide to a framework for reviewing overlapping software costs.
I would use the AI Tool Chooser to organise the shortlist around requirements before a vendor discussion. It does not replace the product-specific, technical or professional validation described for Blocks.
For related engineering buying decisions, I would also read our Adapter Labs review and CtrlB review. These are adjacent evaluations, not a claim that every product replaces Blocks.
I would put Blocks on a conditional shortlist for growth companies with meaningful AWS spend and willingness to transfer billing.
A discount can be expensive if usage falls, ownership is unclear or an automated change creates an outage.
Blocks is AWS cost optimisation and agentic DevOps service. This review focuses on practical buyer fit rather than repeating vendor claims.
Blocks describes success-based fees on realised savings rather than a conventional subscription. Contract terms govern the percentage, commitments and one-off actions.
Growth companies with meaningful AWS spend and willingness to transfer billing.
No. It is a research-based first look using official public evidence. No authenticated workspace or production integration was tested.
No commercial relationship was disclosed for this review, and no rating was assigned.
Operations Lead, AI Search & GEO
Leads operations for AI search visibility and generative engine optimization (GEO) campaigns.
