Skip to main content
Seyn is an alpha product. Everything documented in these guides is live unless a page flags it otherwise; this page is the single source of truth for anything that carries a flag.

How to read the labels

LabelWhat it means
In testingImplemented and being validated with design-partner data before we call it stable.
PlannedSpecified and sequenced, not yet started or not yet open.

In testing

CapabilityWhy it isn’t stable yet
Teams meeting transcriptsBeing validated against real meeting volumes and the Microsoft Protected API approval process.
Outcome trackingRules are matched against live events to measure whether they actually hold; we’re validating the signal quality before badges appear everywhere.
Catalog connectors enabled per engagementHubSpot, Salesforce, Jira, Linear, GitHub, Asana, and Zendesk are in the catalog but switched on per engagement rather than self-serve.
Python SDKEarly alpha. The method surface mirrors the TypeScript reference one-to-one; Python-side ergonomics (async client, retries, pagination helpers) are still moving.

Planned

CapabilityWhat it will do
Self-serve custom connectorsThe connector contract is stable and is what our own connectors use; the self-serve build surface is opened per request today.
Connector auto-syncPer-connector schedules, post-sync rebuild triggers, staleness indicators.
Public benchmarksRetrieval quality, extraction accuracy, and latency, published openly.
Multilingual outputPer-org output language for extraction and narratives, with full diacritic preservation.
What we deliberately don’t do: Seyn never writes back to your source systems. Every connector is read-only by design, and that will not change.

Versioning

The /v1 API is the stable contract. Additive changes ship within /v1 (write integrations to ignore unknown fields); breaking changes ship as /v2 with both versions kept live. Flagged features carry no compatibility promise; if you build against one, talk to us first. Questions about any line on this page: support@seynlabs.com.