Platform status
What Lynkoria v1 supports today, what is limited, and what is not available.
Plan your launch against this page. “Supported” means implemented and covered by automated tests against real local infrastructure. It does not mean load-tested in production; see the limits below.
Capabilities
| Capability | Status | Notes |
|---|---|---|
| One-to-one and group video/audio calls (web) | ✅ Supported | Browser media through @lynkoria/client, with typed participants, connection quality and device selection. |
| Screen sharing (desktop web) | ✅ Supported | Mobile browsers generally cannot capture the screen. |
| Livestreaming with host/speaker/viewer roles | ✅ Supported | Viewers are realtime WebRTC participants; no HLS or CDN. |
| Call signaling (invite, ringing, accept, decline, end) | ✅ Supported | Delivered to connected devices only. |
| Messaging: DMs, groups, history, edits, deletes, reactions, threads, receipts, typing | ✅ Supported | Ordered with gap recovery. |
| Attachments | ✅ Supported | Released only after a clean scan when the scanner is configured (required in production). |
Malware scanning service (apps/scanner, ClamAV) | ✅ Supported | Tested with real ClamAV locally; throughput unmeasured. Details |
| Presence across devices, manual status | ✅ Supported | Visible across a tenant; no contact list or block list. |
| Webhooks with signatures and retries | ✅ Supported | At-least-once delivery. |
| Console: projects, environments, keys, roles, calls, webhooks, analytics, audit | ✅ Supported | Hourly (35 days) and daily usage per environment; live call state; no per-key usage, no infrastructure views (console). |
Native Android/iOS messaging (lynkoria-core, LynkoriaCore) | ⚠️ Preview | Tested against the local API; not on devices. |
| Native Android/iOS/React Native calls | 🧪 Experimental | Built on LiveKit native SDKs; Android and macOS builds pass, not device-tested. Details |
| Push notifications, CallKit / Android incoming-call UI | ⚠️ Preview | Backend delivery tested against mock FCM/APNs only; native UI not device-tested. Details |
| Recording and streaming (LiveKit Egress) | ⚠️ Preview | Lifecycle tested with a stub; no real Egress run. Details |
| Ingress | ❌ Not available | |
| End-to-end encryption | ⚠️ Client-side | Clients may use LiveKit E2EE; calls flagged e2ee cannot be recorded. Lynkoria does not manage keys. |
| Console password sign-in, CLI-provisioned accounts | ✅ Supported | No sign-up. Details |
| Offline send queue | ❌ Not available | Failed sends must be retried by your app. |
| Multi-region media, high availability | ❌ Not available | One media node per deployment. The API supports several instances (ADR 021); the template runs one. |
SDK availability
@lynkoria/server, @lynkoria/client, @lynkoria/react, @lynkoria/react-native and @lynkoria/scanner-client are at version 0.1.0; the Android (io.lynkoria:*) and Swift packages are at 0.1.0. None has been published. See install the SDKs, package publishing and the SDK architecture.
Known limits
- Capacity is not yet measured on production infrastructure. A local single-host run reached 300 simulated livestream viewers at medium quality without packet loss, but that is not a deployed result. See load testing.
- Usage figures are operational, not billing-grade: counters are buffered for about 15 seconds and can lose the final interval if a server crashes abruptly.
- Removing a call participant does not revoke join tokens issued in the last 5 minutes; for a hard ban, also stop issuing tokens and end the call.
- Disabling an environment does not disconnect active media; end calls separately.
- Single-device calls can briefly overlap if two devices join at the same moment.
Per-SDK feature coverage: capability matrix. The platform team tracks verification and outstanding launch gates in the implementation tracker and blockers.