Credentials
OAuth scopes are minimal and read-only. No connector requests write access, and the platform has no code path that writes to a client system.
Where your data goes during analysis
- LLM analysis uses the Anthropic API. Per Anthropic’s API terms, API data is not used for model training.
- Reranking sends candidate text snippets to a reranking provider. If no reranker is configured, querying falls back to a passthrough: the feature degrades rather than the data being required to flow.
- LLM tracing (prompts, responses, token counts) goes to a self-hosted tracing instance on Seyn infrastructure. Observability data never leaves the platform for a third-party SaaS.
- Documents and uploads live in S3-compatible object storage, accessed through short-lived presigned URLs.
The ingestion attack surface
Self-serve upload means hostile files are a design assumption, not an edge case. The ZIP unpacker streams archives with layered defenses:Rate limits
All limits return
429 with a Retry-After header. Higher limits for legitimate workloads (backfills, BI) are granted per key: email support@seynlabs.com.
Auth, isolation, and audit
- Every request is authenticated and organisation-scoped; see Multi-tenancy for the isolation model and the superadmin invariant.
- Every LLM call is logged with model, prompt version, and inputs. The audit trail is the same mechanism as the provenance chain.
- Every MCP tool invocation is audit-logged with operation, latency, and outcome.
- Inbound webhooks are signature-verified before any processing.
Alpha honesty: Seyn does not yet hold formal certifications (SOC 2, ISO 27001). The architecture above (provenance by construction, application-level encryption, read-only connectors, self-hosted tracing) is designed to make that path short. If certification status is a blocker for your evaluation, talk to us about timelines.
Related
Multi-tenancy & Roles
The isolation model underneath everything on this page.
Observability
The audit trail on every LLM call.