Before you begin
Create the board in the conversation that should receive it. A useful board name makes it easier to distinguish a workshop sketch from a private review. Participants can sketch, add text or images and select objects to move; edits travel directly between connected devices. Confirm that both devices see a simple mark before relying on the board in a meeting.
A practical workflow
Treat a board as shared work, not a permission-controlled document repository. An image inserted into it can be seen by its recipients, and those recipients may retain a copy. Keep a separate durable record of important decisions. Reconnecting peers can synchronise available board history, but closing every browser is not the same as storing a cloud document for tomorrow.
Shared whiteboard
Name a whiteboard, sketch together, insert images and select objects to move. Use it in public or private conversations, with edits synced directly.
Questions that matter
What is the difference between public and private sharing?
Public sharing reaches connected devices on the current network. Click a device avatar, then choose private sharing to send only to that device. Each conversation has its own messages and file list. Private messages and files are not included in public history or file catalogs.
Can a newly joined device see earlier messages?
When a direct connection is established, peers share up to 100 recent public records. A device that posted locally while alone can share those records when another device connects. A peer holding the history must still be available; this is not cloud backup. File and voice contents are fetched separately when available, and private conversations are excluded.
Where is my chat history stored?
Only in the local IndexedDB database of each browser, separated by network. Nothing is uploaded. You can clear the history at any time, and clearing site data in the browser removes it completely.
Open the page. That is the whole setup.
OKYA Share uses only standard browser technology, so there is nothing to install or configure.
- Join the same network: Connect your devices to the same Wi-Fi or wired LAN, then open share.okya.app in a modern browser.
- Devices verify each other: A lightweight signaling service introduces candidates. Automatic mode verifies a local host-candidate path; devices attested by a configured LAN node use a separate verification path.
- Share freely: Once verified, files, messages and screens flow directly between devices. Close the tab to stop sharing.
Connection and privacy
Messages and files are sent over WebRTC DataChannels, which are always encrypted (DTLS). TURN relays are disabled by design, so content can never be forwarded through a server.
If automatic local-path verification fails, Share shows a clear message instead of guessing. An optional administrator-run LAN node can attest devices separately; those attested connections may use configured STUN, but never a TURN relay. Network restrictions can still prevent a connection.