HybridCloudWorks¶
HybridCloudWorks is a website for cloud architects, engineers and learners, live at hybridcloudworks.com. It brings architecture guidance, certification study material, planning tools, assessments and hands-on labs for Azure, AWS, Google Cloud, VMware, GitHub, FinOps, Terraform, Docker and Ansible together in one place.
This repository is the source for all of it, and it is public so that anyone can see how the site works, report a problem or suggest an improvement.
What you can do on the site¶
- Learn a platform. Each platform has its own hub with news, articles and learning paths, and the certification index lays out every certification track the site follows, level by level.
- Plan. Compare list prices for the same service on AWS, Azure and Google Cloud, refreshed daily; weigh options with the decision matrix; and assemble an Azure landing zone in the Landing Zone Builder, which explains each part, redraws the diagram as you go, and lets you download the Terraform it becomes.
- Assess. Upload an export of your Azure estate and get an assessment back: a staged plan with example automation and runbooks from the migration assessment, the topology, segmentation and exposure of your network from the network assessment, or a scored review against reliability, security, cost and operations criteria from the cloud assessment. Nothing you upload is kept beyond two hours. The drift check compares an export of what is built with your architecture decisions.
- Practise. Run hands-on labs
in your browser, or on your own machine with one
docker runline.
Start here¶
| If you want to | Go to |
|---|---|
| Look around the site | hybridcloudworks.com |
| Prepare for a certification | Certification index |
| Try a lab | Labs |
| Plan an Azure landing zone | Landing Zone Builder |
| Assess an Azure estate for migration | Migration assessment |
| Assess your Azure network or your whole estate | Network assessment, Cloud assessment |
| Check what is built against your architecture decisions | Cloud Crawler drift check |
| Report a problem or suggest something | Open an issue |
| See what is being worked on | HCW Work Board |
| Ask a question or get help | SUPPORT |
| Read how the site is built and run | docs.hybridcloudworks.com |
How it is built, briefly¶
The pages are served by Azure Static Web Apps, and one Azure Functions app serves the site's data and runs its background jobs. The labs and the assessment tools run on a separate lab host. Everything is defined as code in this repository, every change is reviewed and tested before it merges, and nothing reaches the live site without a person approving it.
The full picture is on the documentation site, which is built from the
docs/ folder:
- How HybridCloudWorks is built: the architecture diagram, every component, a map of this repository, how to run each part locally, and how changes are tested and delivered.
- Architecture decisions: why each choice was made.
- Runbooks: how the platform is operated.
Contributing¶
Contributions and suggestions are welcome. To try the website locally you need Git and Node.js 26:
git clone https://github.com/saulpatinojr/HCW-HybridCloudWorks.git
cd HCW-HybridCloudWorks/frontend
npm ci
npm test
npm run dev
Vite prints the local address to open. The other parts of the repository, and what each needs, are in Run it locally.
Before your first pull request, read CONTRIBUTING. In short:
- Work is tracked as GitHub issues and on the HCW Work Board.
- Every change arrives as a pull request that follows the template, with its checks green.
- Narrative documentation goes under
docs/, not beside the code. CHANGELOG.md records completed work and TODO.md the accepted risks.
Everyone taking part follows the code of conduct.
Security¶
Report a vulnerability privately, as SECURITY describes, never in a public issue.
Licence¶
The code is licensed under the Apache License, Version 2.0; the text is in
LICENSE. NOTICE carries the copyright line and explains
that third-party names, logos and marks, such as the vendor logos under
frontend/public/icons/providers/ and frontend/src/assets/brands/, belong
to their owners and are not licensed under Apache-2.0. Other third-party
material, such as the fonts under frontend/public/fonts/, keeps its own
licence terms.