One page, every feature — how the messaging works, how the mesh keeps your office talking when a PC or the internet goes down, how mobile and identity fit together, and exactly what's protected and how.
Your conversation history is stored on your own network, not a third-party cloud.
No single office PC has to carry the whole conversation on its own.
iPhone and Android access, installed straight from a QR code — no app store.
Stay notified after leaving the chat screen, not just while it's open.
A recommended everyday connection, and a direct-LAN alternative when you need it.
Restore the same identity — and the same private conversations — across Stable and Local.
One shared space for the whole office network.
Dedicated one-to-one conversations, separate from the group.
Reply to a specific message, quoted in context.
Emoji reactions on any message.
Tag a specific person so it's clear who a message is for.
Find previous messages and information quickly.
Record and send voice notes directly in a conversation.
Share images and documents with inline previews.
See who's currently available at a glance.
Unread conversations stand out, organized by day as you scroll back.
See which station or device a message actually came from.
Conversation history stays in sync as stations reconnect.
Authorized Station Chat PCs find each other automatically across your local network and form a mesh — recent group history is replicated between them, so one PC is never a single point of failure, and a station that's been offline catches up automatically when it reconnects.
Stations find one another on the network without manual setup.
On a separated network segment, an administrator connects a station directly by IP address or hostname instead of relying on automatic discovery.
A station that was offline recovers the group messages it missed when it reconnects — merged and deduplicated automatically.
Direct messages wait for the destination station and deliver once it reconnects, while missed group conversation is recovered automatically alongside it.
If one station goes offline, the others keep communicating.
Local messaging continues even when your internet connection is down.
Stations rediscover each other automatically after a network change.
A newly discovered station is flagged for an administrator to review before it's trusted.
A real installable app for iPhone and Android — no App Store submission required. Group chat, private messages, voice, files, replies, reactions and mentions all work exactly like the desktop app.
Stable Mobile is the recommended everyday connection — it can securely relocate your paired station even after its network address changes. Station Chat Local connects directly over the LAN and keeps working without internet, as long as the local network itself is up. Most people never need to think about which one they're using — Stable Mobile just works, and Local is there as a fallback.
Add it to your home screen straight from the browser — no app store deployment.
Scan a code to connect — no accounts to create.
Works from any modern browser, not just phones.
Stable Mobile finds your station's current network address automatically.
The address the relay returns is cryptographically checked, never just assumed correct.
Handles a station's local IP changing without any manual re-pairing.
A saved Station Chat identity can be restored into both Stable Mobile and Station Chat Local — the same name, the same cryptographic credentials, and access to the private-message history tied to that identity. Switching connection methods never turns you into a second, different person in the conversation.
Back up once, restore whenever you need to — a new phone, a reinstalled PWA, or setting up both Stable and Local.
Not tied to a temporary browser session — it's yours to carry forward.
Restoring your identity restores access to the private conversations tied to it.
Cryptographic identity survives normal restarts — no re-verifying every time.
A returning device proves possession of its identity, not just a claimed name.
Detects and recovers cleanly if identity storage is ever damaged.
Station Chat keeps notifying staff after they've left the chat screen — including while the installed app isn't actively open. Ordinary group chat stays quiet by default; a message only reaches everyone's phone when its sender deliberately flags it.
Arrive even when the app is backgrounded or closed.
Notified the moment someone sends you a direct message.
Ordinary group messages don't push a notification to everyone's phone — no alert fatigue from routine conversation.
Routine group conversation doesn't bombard everyone's phone. The original sender can use the one-time Bell to escalate a specific message when it truly needs attention — it stays visibly marked so everyone can see it was flagged.
A message from another station still reaches your phone correctly.
Configure how long an away device keeps receiving push alerts.
For transparency: notification preview text currently passes through our push delivery service on its way to your phone, the same way standard web push works for most apps. Core chat and your stored conversation history are entirely separate from this and are never exposed to it. Recipient-side encryption of push previews specifically is in active development — see what's next.
Group conversations and stored history remain on your office network. External services are used only for specific features that require them: push delivery, locating a station after its network address changes, initial license activation and software updates. Core chat and communication between stations continue locally without internet.
Stored messages and files are encrypted at rest with AES-256-GCM, not just in transit.
Station-to-station sessions are mutually authenticated and use HKDF-SHA-256 to derive per-session AES-256-GCM keys. Plaintext isn't accepted once a connection has authenticated.
Turn on encryption for a private conversation and the content is genuinely unreadable to any intermediary station or server — a separate layer from the encrypted mesh and encrypted storage above.
Protected private conversations can be verified out-of-band, not just trusted by default.
Cryptographically checks the station it connects to, rather than blindly trusting the relay.
Block a device and cut off its access, including notifications, at any time.
A conflicting identity key is rejected rather than silently trusted — a mesh peer can't quietly impersonate another station.
Ban and re-admit devices as needed.
Decide which stations accept new users and which participate in the mesh.
A newly discovered station waits for administrator review before it's trusted.
Authorize a new station from an existing trusted Station Chat PC — no phone, camera or separate browser setup required. Credentials are provisioned only after cryptographic verification and administrator approval.
Configure how long an away device continues receiving push notifications.
Your organization's name and logo, shown across every device.
See connection status across the mesh at a glance.
Real diagnostic information, exportable when you need support — enough separation between LAN, Stable Mobile and push to tell you exactly which layer had a problem.
Having trouble reaching another station? Station Chat can test the connection for you. It checks whether this PC's own mesh service is running, whether the local Windows Firewall rule appears to exist, whether the station's address resolves correctly, whether that address is acceptable, and whether the station is actually reachable — then explains the likely cause in plain language instead of just "connection failed." It tests the Station Chat mesh path on TCP 47892 without changing your network configuration.
Plain-language connection information, not just raw logs.
Export a full diagnostic log for support, filterable by date.
See peer-dialing results between stations directly.
Run the readiness test for any configured station and quickly identify DNS, firewall, routing or reachability problems.
A rejected, conflicting identity key is logged with enough detail to investigate.
See exactly why a notification did or didn't arrive.
Know whether an issue is your LAN, Stable Mobile, or the push service — not just "something's wrong."
Nothing is designed to take the whole system down at once. Here's what actually happens when something goes wrong.
The one remaining gap between "the push service can technically see a notification preview in transit" and true end-to-end privacy for every part of Station Chat. The design is already worked out — recipient-side encryption using a separate encryption identity from your signing identity, so the push service only ever sees ciphertext, never your message. We'll update this page the moment it ships.