Subprocessors

This page describes the third-party subprocessors that Stackmint, Inc. ("Stackmint") may engage to support delivery of the Stackmint platform and related services.

Last updated: November 30, 2025. Stackmint may update this list from time to time. Where required by contract or applicable law, customers will be notified of material changes.

1. Core Infrastructure

These subprocessors are used to host and operate the Stackmint platform.

SubprocessorServiceLocation
RenderApplication hosting and runtime infrastructureUnited States / EU
Amazon Web Services, Inc. (AWS)Infrastructure and compute hosting for Bud runtime and execution (Bud code, execution metadata, runtime logs, and related configuration)Primarily EU and US regions (e.g., eu-west-1, us-west-2)
SupabaseManaged PostgreSQL database, authentication, and storageEU or US regions (customer-dependent)

2. Billing and Payments

These subprocessors are used to process subscription fees and marketplace payments.

SubprocessorServiceLocation
StripePayment processing and billingGlobal (primary processing in EU / US)

3. Communications

These subprocessors are used for transactional emails and limited customer communications.

Example placeholder:

SubprocessorServiceLocation
ResendTransactional email deliveryUnited States

4. Optional AI Model and Inference Providers

Stackmint can be configured by customers to route workloads to multiple AI model providers and inference platforms. These providers are only used where explicitly enabled by the customer.

  • OpenAI – hosted large language models
  • Mistral AI – hosted large language models
  • Hugging Face – inference endpoints and model hub
  • Anthropic – hosted large language models
  • Other providers as configured by the customer

5. Optional Customer-Activated Integrations

Customers may connect Stackmint to third-party systems (for example, Salesforce, Slack or Microsoft Teams, Google Workspace, HubSpot, Workday and other tools). In those cases, Stackmint acts as a processor, orchestrating data that already resides in those systems.

These integrations are activated and configured directly by the customer, and the third-party providers remain independent data controllers or processors under their own terms.