Kairos
Kairos Beta
Kairos is in open beta: usable for real research work, still changing. This page is the contract — what Beta means, what is in scope, how accounts and data work, and what has to be true before we drop the label.
The contract
What Beta means here
Usable now
The workbench, accounts, projects, cited evidence, ranked design panels, and audit trail are in production. Real questions are welcome; this is not a demo.
Still changing
Hosts, scoring functions, and process objects are still being extended. Breaking changes to outputs or access are dated in the changelog below.
No SLA
Availability and support are best-effort during Beta. Material incidents are posted on this page and communicated to affected accounts.
Scope
Pichia, dry-lab, and nothing more
Kairos ranks dry-lab design quality in Komagataella phaffii (Pichia): synthesis safety, host resemblance, 5′ translation initiation, and protein developability. It is a research input for qualified professionals, not a validated manufacturing instruction.
It does not predict expression or titer. Those are wet-lab questions, answered by wet-lab data. Every output carries its own scope line, and every claim carries a citation you can open.
Access
An account, not an anonymous session
Kairos requires an account. Sign in with a one-time code sent to your email — no password. Creating an account is free during Beta; the account is what ties a project, its history, and its reports to you.
- No anonymous trial sessions. Every session belongs to the account that started it.
- Rate limits and per-question length limits apply; they are visible in the workbench.
- Invited evaluation partners may receive extended access at our discretion.
Data
What we keep, and for how long
Research sessions and delivery reports are stored in your own project so you can re-open them, compare versions, and trace lineage. Default retention: research records 7 days; shared report copies at most 30 days; account email while the account is active. You can request deletion at lei@bluex.net.cn.
Sequences are not used to train models. The full data map — including the DeepSeek processing boundary and the egress gate — is in the Privacy Policy.
Feedback
What breaks is the point
Beta exists to find the failures before your production work does. Send a wrong citation, a failed run, an unexpected score, or a confusing screen to lei@bluex.net.cn. Include the project or session link if you can; we will confirm receipt and tell you what we can reproduce.
Changelog
Dated changes
- 2026-10-23 — Public Beta. Account-based access, this page, and a single public status label: Beta.
- 2026-10-21 — Anonymous trial closed. Email account required; the one-time sign-in code creates the account.
- 2026-10-20 — Workbench upgrade: projects, cited evidence, audit trail, and light-theme parity.
Exit criteria
When Beta ends
We leave Beta when four things are true:
- A second host is in production, not a demo.
- Design ranking has prospective wet-lab validation with partners.
- The workbench and API have been stable for four consecutive weeks.
- Support, incident communication, and a public status page have named owners.
Until then, the label stays Beta.
Bring a real question
Create an account with a one-time email code; the workbench opens with the Pichia scope.