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.
PUBLIC STANDARDCore deployment
AWS Lightsail hosts the application deployment and MongoDB Atlas provides the production data store in the documented architecture.
Dated Reviewable Limits shown
DIRECT ANSWER
The current Indoo architecture can use AWS Lightsail for application hosting, MongoDB Atlas for tenant data, OpenRouter for language-model routing, Apify for website import, Google for optional sign-in, Resend for transactional email, Zernio for social operations, and optional fal.ai or Kie.ai providers for configured media generation.
Verified against the current Indoo product · 2026-08-17PUBLIC RECORD
Claims should be specific enough to verify.
For subprocessors, the current public standard is shown below.
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 WE APPLY IT
Move from a stated standard to an accountable action.
For subprocessors, the sequence keeps context, ownership, and the next decision visible.
- 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.
TRANSPARENCY NOTE
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.
DECISION QUESTIONS
What people ask before choosing this path.
Answers stay specific to subprocessors and the current product boundary.
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.
PUT SUBPROCESSORS TO WORK
Apply this page to your real brand and next marketing goal.
- No payment card in signup
- Website-first brand setup
- Human approval available