Core deployment
AWS Lightsail hosts the application deployment and MongoDB Atlas provides the production data store in the documented architecture.
SUBPROCESSOR TRANSPARENCY
Know which providers may support an Indoo deployment and feature.
Review the infrastructure, data, AI, website import, authentication, email, social, and optional media providers used by the current Indoo architecture.
WHAT MATTERS
The operating details behind the promise.
Configured services
OpenRouter, Apify, Google, Resend, and Zernio support AI, website extraction, identity, email, and social features when enabled.
Optional media
fal.ai and Kie.ai are optional routed media providers and receive content only when that configured workflow is used.
HOW IT WORKS
Move from context to accountable action.
Every stage keeps the brand, goal, evidence, permissions, and work history attached.
- 01
Match the feature
Identify which Indoo capabilities the deployment will enable and therefore which providers may receive data.
- 02
Verify the current list
Request the production configuration, provider terms, locations where applicable, and effective date before contracting.
- 03
Review changes
Use the agreed notice and objection process for material provider changes covered by the contract.
INDOO PRINCIPLE
This is an architecture-level list, not a claim that every provider processes every customer's data. The production deployment and enabled features determine the applicable set.
COMMON QUESTIONS
Direct answers, then the details.
Does every prompt go to every AI provider?
No. The configured routing and selected workflow determine which provider receives a request.
Can the provider list change?
Yes. Confirm the current deployment-specific list and contractual notification terms before relying on this page for procurement.
ONE BRAND BRAIN · ONE LOOP
Put this workflow to work on your real brand.
- No payment card in signup
- Website-first brand setup
- Human approval available