Skip to content
Alcarta

Known limitations

Alcarta is in closed beta. The following constraints describe the implemented main branch, not the longer-term product plan.

TOTP is visible but cannot be enrolled

Section titled “TOTP is visible but cannot be enrolled”

The sign-in form contains an optional TOTP code field. There is currently no profile or API route that enrolls a TOTP secret, and the login path does not complete TOTP verification. Treat the field as non-functional. Do not claim TOTP-based MFA in a security policy for this release.

Long-running connections grow memory

Section titled “Long-running connections grow memory”

Sustained monitor_inbox, email_await, and WebSocket workloads have shown approximately 1.4 MiB/minute of resident-memory growth in soak testing without a demonstrated plateau. Until this is resolved, set memory alerts and limits, watch per-instance RSS, and recycle instances gradually before they approach their limit. Keep enough replicas to preserve availability during recycling.

Planned identity and mail features are absent

Section titled “Planned identity and mail features are absent”

Passkeys, enterprise SSO, contacts, conversation/thread APIs, and a cross-mailbox selector are not implemented. They are intentionally omitted from the rest of this documentation.

Billing screens and routes currently use a mock billing implementation. Do not connect production entitlements or financial reporting to their responses.