Infrastructure and connected providers

• Hosting and storage: the operator's selected infrastructure host, database, runtime coordination, and object-storage services.
• AI and retrieval: model, embedding, reranking, and web-search providers configured for the deployment or selected by an authorized user.
• Connected tools: MCP-connected services receive data required for a user-authorized tool call, subject to connection scope and approval settings.
• Optional delivery: SMTP email, push, voice, or other integrations may process the information needed for the enabled feature. The public contact form sends its verification code, message, and reply address through the deployment's configured SMTP provider. Resend may receive direct mail sent to the site contact address and forward it to the operator's private inbox through a signed webhook.

The source defines PostgreSQL, Redis, and MinIO-compatible storage components and supports configurable external providers. It does not identify the live hosting company, data region, enabled supplier names, applicable transfer safeguards, or each provider's current contractual role. Those facts are set outside the source repository and must be confirmed for the specific deployment.

The service operator must publish the legal names, purpose, processing location, and privacy notice for each supplier used by the hosted instance, and update this page when that list changes. The codebase does not contain enough information to present a complete production subprocessor list. Do not treat the categories above as a substitute for that deployment-specific notice.