AWS vs Azure infographic | burley bike trailer comparison chart

Side-by-side comparison infographic titled "AWS vs. Azure" (in English). Split the canvas vertically into TWO clearly separated columns with strong balanced symmetry: left column for "AWS" with a generic cloud/server hero icon, right column for "Azure" with a different generic cloud/network hero icon. Create an editorial comparison layout, clean grid, vector-clean lines, balanced symmetry, in a sketch / whiteboard style with sharp readable typography, hand-drawn marker accents, neat icons, and high clarity. Use a two-tone palette with contrasting accents: AWS side in warm red, Azure side in teal, on a clean white background with dark gray text and subtle checklist highlights. Build exactly 8 horizontal attribute rows spanning both columns. Each row must include: a short attribute label on the far left in English, a small matching icon, the AWS value in the left column, the Azure value in the right column, and a subtle winner highlight using a checkmark, slightly bolder text, or a green dot. Keep the comparison honest, balanced, and practical, focused on pros & cons checklist differences. Use these exact row labels and exact on-image text values: Row 1 label "Market adoption" with icon of bar chart; AWS value "Largest global market share"; Azure value "Strong enterprise presence"; winner highlight on AWS. Row 2 label "Enterprise integration" with icon of office building; AWS value "Broad tooling, less tied to Microsoft stack"; Azure value "Excellent with Windows, Active Directory, Microsoft 365"; winner highlight on Azure. Row 3 label "Service breadth" with icon of toolbox; AWS value "Very broad and mature service catalog"; Azure value "Broad portfolio, slightly less depth in some areas"; winner highlight on AWS. Row 4 label "Hybrid cloud" with icon of linked clouds; AWS value "Improving hybrid options"; Azure value "Leader in hybrid and on-prem integration"; winner highlight on Azure. Row 5 label "Ease of use" with icon of checklist; AWS value "Powerful but can feel complex"; Azure value "Familiar for Microsoft-centric teams"; winner highlight on Azure. Row 6 label "Pricing clarity" with icon of price tag; AWS value "Flexible but often complex pricing"; Azure value "Also complex, better for existing Microsoft agreements"; winner highlight on Azure. Row 7 label "Open-source and Linux" with icon of terminal window; AWS value "Strong open-source and Linux ecosystem"; Azure value "Good support, historically more enterprise-focused"; winner highlight on AWS. Row 8 label "Best fit" with icon of target; AWS value "Startups, cloud-native builds, widest service choice"; Azure value "Large enterprises, Microsoft-heavy, hybrid environments"; winner highlight on Azure. Add small pros/cons checklist cues within each value cell where appropriate, such as tiny plus and minus bullets, but keep text concise and readable. At the bottom, add a full-width verdict bar with one clear winner in English: "Verdict: Azure wins overall for enterprise and hybrid use, while AWS remains strongest for service breadth and cloud-native flexibility." Mood: professional, informative, balanced, approachable, whiteboard-strategy-session feel. No real brand logos; use only generic cloud/platform symbols if needed. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real brand logos beyond what is essential for the comparison subject, no watermarks Honest, balanced comparison — no biased framing, no real brand logos unless essential to the comparison subject. Where logos appear (e.g. crypto coin symbols), use commonly understood generic representations rather than copyrighted marks.