Subprocessors
Last updated 28 October 2026
architecture.dev uses the subprocessors below to provide the architecture.dev platform, its hosted environment and support. Each one processes Customer Content only to perform the service listed against it.
| Subprocessor | Service | Customer Content processed | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Cloud hosting: compute, storage, secrets and container images for the hosted environment | All Customer Content in the hosted environment | United States |
| Anthropic, PBC | AI model provider (Claude) for generating specifications, designs and code | Customer Content submitted for generation, and the Output it produces | United States |
| Cloudflare, Inc. | DNS, TLS termination and network edge for architecture.dev addresses | Customer Content in transit to and from the hosted environment | Global edge network |
| GitHub, Inc. | Source repositories that hold generated code and specifications | Output, and the Customer Content it contains | United States |
| Microsoft Corporation | Identity for architecture.dev personnel, and email for support and correspondence | Customer Content included in Tickets and email | United States |
New subprocessors
architecture.dev gives at least 30 days’ notice before a new subprocessor begins processing Customer Content. Notice goes by email to each customer’s Authorized Contacts, and this page is updated at the same time.
A customer may object to a new subprocessor during the notice period by writing to legal@architecture.dev with its reasons. architecture.dev will work with the customer in good faith to resolve the objection. The customer’s further rights are those set out in its agreement and in the Data Processing Addendum.