## Reference images

Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language.

- Component: https://kage-design-assets.t3.tigrisfiles.io/components/ledger-com/abaab959-f9d6-43c3-8f0c-09f584ac8799-1789146872-6.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/ledger-com/abaab959-f9d6-43c3-8f0c-09f584ac8799-1789146801441-full.webp
- Component on Kage: https://kage.design/component/ledger-logo-cloud

## Before you start
Ask what the user's product is, who it serves, and what its brand voice and visual identity are. Apply the following principles to that product rather than reproducing the reference.

Create a dark supported-services section with a left-aligned heading, one explanatory line, and a small browse-all action aligned to the heading row. Below it, show a single responsive row of circular asset or integration marks with generous spacing. Use muted introductory text, 30–36px heading type, 56–64px circular mark containers, and a black background. Each mark should have its own accessible label and use brand colors only when the user's product has permission to display them. Fade or wrap overflow rather than clipping meaningful content.

On mobile, use a horizontally scrollable list with a visible affordance and no forced carousel autoplay.

### Never
- Never copy logos, product names, copy, illustrations, or imagery from the reference.
- Never imply unsupported integrations or use third-party marks without an appropriate data source and permission.