
Discover what’s happening
See short-lived plans around a fixed map area without broadcasting anyone’s live location.
Closed beta · Melbourne
Flare shows what people nearby are genuinely up for doing now—without broadcasting anyone’s live location.

Inside Flare
Explore the actual closed-beta experience from discovery through accepted access.

See short-lived plans around a fixed map area without broadcasting anyone’s live location.

See the activity, host and intentionally approximate area before deciding whether to join.

Review a public profile and shared-event context before choosing whether the plan feels right.

Accepted participants receive the exact meeting point and arrival guidance—never the public map.

A temporary event chat helps the group coordinate without creating a permanent public thread.

Turn a spontaneous idea into a short-lived invitation for eligible people nearby.
Why Flare
Most plans begin with a small window: an hour free, a place you already are, and the feeling that you would rather do something than scroll past it.
Flare turns that window into a visible invitation—temporary, local and controlled by the person hosting it.
One simple journey
Open the local map and find active plans that match the moment you are in.
View the host, activity and approximate area, then send a request when it feels right.
Once accepted, unlock the exact meeting details and a temporary event chat.
Designed for real life
Every core interaction has an explicit boundary: who can discover a plan, who may join it, when exact details appear and when access ends.
Public map areas are intentionally offset. Exact meeting details stay protected until a host accepts you.
Flares are about what is happening now—not building another endless event directory.
Hosts review profiles before deciding who receives private event access.
People who meet through a shared flare can choose to stay mutually connected.
Leave, remove, block and report are built into the event journey—not hidden in a help centre.
Discovery, private access and chat follow a deliberate post-event lifecycle.
Privacy by design
Flare takes one accurate foreground reading when it is needed. A host’s exact meeting point is stored separately while the public map receives one stable, randomly offset area.



Beyond one event
Connections are private and mutual. They begin in the context of a shared flare, can be removed at any time and never override a block.
Read the community standards →We’re testing deliberately
We are starting small to learn what makes a local network feel useful, trustworthy and alive before opening it more widely.
TestFlight beta · Invite only