A private voice coordination pilot from everwished.

TailTalk An everwished proof of concept

TailTalk

An upcoming proof of concept for private push-to-talk voice coordination, designed for small teams and community operations that need quick spoken updates without public internet exposure or extra application accounts.

Explore the PoC Discuss support

Early-stage work. TailTalk is not currently offered as a public service.

Private tailnet PTT ready

Active channel

Operations

Desktop Tailnet Android browser

The Need

When a call is too much and a message is too slow

Some work needs a voice channel that is immediate, contained and simple. TailTalk is being prepared to test whether a walkie-talkie style browser experience can help teams coordinate without adding a public communications platform.

Small teams in motion

Site leads, volunteers, support workers and technical teams may need fast spoken updates while moving between tasks, rooms or devices.

Lower-friction coordination

A press-and-hold route can be easier than starting a meeting, making a phone call or moving urgent context into long message threads.

Contained infrastructure

The first pass keeps voice traffic inside Tailscale membership and access rules, rather than opening a public listener for the wider internet.

The PoC

A focused walkie-talkie interface for private groups

The proof of concept is intentionally narrow: a local daemon handles private networking and routing, while the browser provides microphone access, speaker playback and a clear push-to-talk control.

Illustrative interface direction for the pilot. Final screens will be shaped by testing and operational feedback.

Local daemon and browser UI

The desktop service owns tailnet membership, routing and control, while the browser remains the user-facing audio surface.

Press-and-hold voice

Keyboard and touch controls keep transmission deliberate, visible and easy to stop.

Channel groups

Named channels and explicit groups allow a pilot to test how teams separate routine coordination from urgent updates.

Android browser route

The mobile path uses the official Tailscale Android app with a browser or PWA experience for the TailTalk surface.

Basic diagnostics

Status checks can make microphone permission, network state and peer availability easier to understand during a pilot.

Clear first-pass limits

Recording, replay, public access and native mobile hardware integration are outside the initial scope.

Private Network

Designed around tailnet membership

TailTalk treats Tailscale membership and access controls as the private network boundary for the first pass. The pilot should test whether that is simple enough for real use while staying honest about what it does and does not provide.

01 / User device

Browser controls audio

The user grants microphone access and holds a key or touch control to transmit.

02 / Local service

Daemon routes packets

The TailTalk service applies the selected channel and group routing before sending audio.

03 / Tailnet peers

Private nodes receive

Other authorised devices on the configured tailnet receive the live voice stream.

Pilot Questions

What the proof of concept needs to learn

The pilot is not only a technical exercise. It should test usefulness, trust, support load and the conditions that would be needed before a wider service could be considered.

  1. 01

    Usability

    Can people join, choose a channel and use push-to-talk without training overhead or confusing setup?

  2. 02

    Reliability

    Does the voice path behave predictably across realistic desktop, Android browser and network conditions?

  3. 03

    Physical controls

    Which buttons, keyboards, headsets or accessibility devices can make the interaction quicker without requiring a native mobile app?

  4. 04

    Operational policy

    What rules should govern channel membership, transmission etiquette, emergency escalation and support responsibilities?

  5. 05

    Responsible next step

    What evidence would justify improving the prototype, and what limitations should remain visible to future users?

Support

Help test private voice coordination responsibly

TailTalk is suited to partners who can help ground the PoC in real operational needs, careful evaluation and a proportionate approach to privacy and support.

Email Everwished

Funders

Resource the learning

Support discovery, delivery, accessibility input and evaluation.

Operational partners

Bring realistic settings

Shape channel models, usage boundaries and practical rollout needs.

Technical partners

Challenge the implementation

Review networking, device behaviour, diagnostics and maintainability.