# Apache Reqsign™: Build. Sign. Send. > Reqsign signs HTTP requests and loads cloud credentials for AWS, Azure, Cloudflare, Dropbox, GitHub, Google, Aliyun, Huawei Cloud, Oracle, Tencent, Vercel, Volcengine, and Yandex Disk services without pulling in full vendor SDKs. Reqsign keeps explicit per-provider signing protocols while sharing one composition pattern: build the request, load or grant credentials, sign, then send with your own HTTP client. ## Table of Contents ### Docs - [Build. Sign. Send. | Apache Reqsign™](https://reqsign.apache.org/): Apache Reqsign™ signs HTTP requests, loads cloud credentials, and grants scoped access for AWS, Azure, Cloudflare, Dropbox, GitHub, OneDrive, Google, Aliyun, Huawei Cloud, Oracle, Tencent, Vercel, Volcengine, and Yandex Disk — without pulling in full vendor SDKs. - [Community | Apache Reqsign™](https://reqsign.apache.org/community/): How Apache Reqsign is governed and where to ask questions, report issues, and contribute. - [Download | Apache Reqsign™](https://reqsign.apache.org/download/): Official Apache source releases, signatures, checksums, and crates.io convenience packages for Apache Reqsign. - [Architecture | Apache Reqsign™](https://reqsign.apache.org/docs/architecture/): How Reqsign is put together — Context, ProvideCredential, SignRequest, Signer, and Granter — and the three levels at which you can plug in. - [Reqsign vs vendor SDKs | Apache Reqsign™](https://reqsign.apache.org/docs/comparison/):