Happy Knowledge ships two ways.
The model you're on decides who operates each boundary. Read the column for your model in the table below.
Happy-hosted
Happy Technologies runs a dedicated instance in its own AWS account (us-east-1). Our infrastructure subprocessors apply.
BYOC (bring-your-own-cloud)
The instance runs in the customer's own cloud account. Providers the customer brings are the customer's, not our subprocessors.
Current subprocessors.
Four parties, each scoped to a specific purpose. Nothing here is speculative; this mirrors the source of truth maintained alongside the codebase.
| Party | Purpose | Happy-hosted | BYOC |
|---|---|---|---|
| Amazon Web Services | Infrastructure: ECS Fargate, EFS (encrypted), Secrets Manager, CloudWatch, ECR, ALB | Our subprocessor | Customer's own account, not our subprocessor |
| LLM + embedding provider (customer-selected; DeepInfra is the default) | Compile/query inference (BYOK) | Customer-contracted (BYOK); embeddings run in-infra by default (no egress) | Same, customer-contracted, in the customer's boundary |
| Stripe | Billing, only when managed billing is enabled | Our subprocessor when managed billing is on | Only if the customer buys through our managed billing |
| Keycloak | Identity/SSO | Runs inside the deployment boundary, not a third party | Same |
Not subprocessors
Connector OAuth providers (GitHub, Google Drive, Dropbox, Zendesk, Salesforce, HubSpot, S3) are customer-initiated data sources the customer connects; they are not Happy Technologies subprocessors.
Data egress
The only customer-content egress at runtime is inference to the customer-selected LLM provider (BYOK). Nothing ships customer artifacts to any third-party model-training sink; the account export is customer-initiated and authenticated. Embeddings run on the in-infra model by default, so text does not leave the boundary for vectorization.
Changes are announced, not silent.
Any change to this list is announced with at least 30 days' notice, per our Data Processing Addendum. To subscribe to subprocessor change notifications, email privacy@happy-tech.biz.
Happy Technologies holds no formal attestations today (see our Trust & security page). This list is disclosed so customers can verify the data path rather than take a badge on faith.
Last updated: 2026-07-09
Questions about a subprocessor?
Talk to us directly, or see how the rest of the platform is built to be verified rather than taken on faith.