Competitors
August 2026 spot-check
Snapshot date: 2026-08-10. A targeted re-check of Sit By Me plus a first look at Metby.ai, not a full sweep. The June assessment below still stands; this only records what moved.
Sit By Me: moved slowly, thesis unchanged
Their own site now claims 3,700+ users and 7,800+ connections, against ~3,200 users in the June reading. Roughly 15% user growth in two months, still Milwaukee plus Wausau, with Chicago, Atlanta, and Denver still waitlists rather than live markets. That is consistent with the June call: closest mechanic, weakest executor, benchmark rather than predator.
One new thing worth noting: they now market "+20% Revenue increase for partner businesses" to venues. No methodology is published, and with a few thousand users across two small markets it is unlikely to survive scrutiny, but it tells us what number a venue-facing pitch is expected to lead with. When our attribution receipts exist, we will be able to make a version of that claim we can actually defend, which is the difference we should sell.
What they actually sell to businesses (correcting a loose earlier reading)
Checked directly, because "they monetize merchants too" is easy to say and wrong in the way that matters. Sit By Me sells venue partnership tiers: visibility, foot traffic, and "community credibility", with some tiers bundling premium memberships for the venue's people. Consumer premium is separate at about $5/mo. Event organizers can buy sponsor advertising, and premium users see deals at Connection Points.
What that is NOT: an advertising product. There is no evidence of self-serve offer creation, targeting, delivery metrics, or attribution reporting. A venue is buying presence on the map and a community perk, priced like a listing subscription (roughly $300/mo per the June founder conversations), not impressions or outcomes.
So the two models differ at the root, not in the details:
| Sit By Me | Lantern | |
|---|---|---|
| Who pays | Venues (tiered partnership) AND users ($5/mo) | Merchants only; users never pay |
| What a business buys | Visibility, foot traffic, community credibility | Offers and contextual ads delivered to people at or near the venue |
| Self-serve | Not evident; sales by mailto | Merchant creates and publishes their own offers |
| Proof of value | A blanket "+20% revenue" claim | Attribution receipts, which is the whole Phase 6 bet |
| Audience framing | Remote workers and co-working, professional connection | Meeting people socially at venues, anonymously |
That last row matters as much as the money: their early Connection Points are cafes and co-working spaces (ExpMKE at Wantable Cafe, Haven Cafe, BizStarts), and the press frames it as breaking the ice between remote workers. We are not fighting over the same table.
Correction to the standing line that "anonymity + venue + merchant-data is unclaimed": venue opt-in is genuinely claimed, but merchant DATA and attribution are not, and neither is anonymity. Two of three remain ours. The earlier August note here overstated the overlap by reading a partnership program as an ad product.
Unverified this pass: release cadence, the June tripwire for "they found funding or a team". Worth checking directly next time.
Metby.ai: adjacent, not competing (and a useful mirror)
Indian interest-based social network (Bengaluru, Delhi, Mumbai; 1 to 10 employees) that bills itself as helping people "find, plan & meet compatible companions". Two mechanics: broadcast a plan for an activity to find companions, and create or join clubs by interest. Categories run from dating and fitness to travel, business, and flat-sharing. ML is used to screen fake profiles.
Threat: low. Different geography, profile-based rather than anonymous, and crucially not venue-anchored: it matches people to activities, where we anchor presence to a specific place in near-real time. It is closer to Meetup plus matchmaking than to Lantern.
Why it is still worth reading: their "plans" mechanic is essentially our scheduled lanterns feature, which is exactly the surface we are repositioning toward "going somewhere with a buddy, closer to a yoga class than an event". Someone else has shipped that mechanic at scale in another market, so their category list, their club framing, and whatever they have learned about no-shows are free design reference. Adjacent products that already solved a sub-problem are cheaper to learn from than competitors we are trying to beat.
Others surfaced in the same pass
Timeleft (dinner with five strangers, 200+ cities across 52 countries) and Meza (solo travellers over meals, Bali) both keep validating the manufactured-density lesson the June assessment already drew: strangers meet more readily inside a scheduled container than on an ambient map.
Current Landscape — June 2026 Assessment
Snapshot date: 2026-06-11. Sourced from a multi-agent research sweep (24 sources, 112 claims extracted, top 25 adversarially verified). Reassess quarterly: September 2026, December 2026, March 2027. The conceptual comparisons further down this doc (Foursquare, Left Field, etc.) remain valid framing but predate this landscape.
The field, ranked by threat
| Rank | Player | Mechanic | Identity model | Live where | Why this rank |
|---|---|---|---|---|---|
| 1 | Tinder / Match Group | Curated, ticketed "Events" (RSVP via ticketing partner) — not presence | Profiles | LA (Mar 2026); more cities planned "in upcoming seasons" | Distribution we can't buy; could define the IRL narrative in CA metros before our launch. Fast-follow risk activates only after someone proves the presence mechanic. |
| 2 | Venue (venue-app.co) | Check-in dating; exposes live AND historical presence ("who's been here before") + in-app messaging | Profiles + mandatory verification | Nowhere — waitlist-only private beta | Same venue-anchored instinct, opposite identity bet. Only competitor whose launch could directly collide with ours. Funding unknown; private betas surface without warning. Watch closely. |
| 3 | Timeleft | Scheduled stranger dinners; new "Last Drinks" sends groups to a surprise bar after | Profiles | San Diego + SF today, many metros | Most underrated threat: already has local density in our launch markets and is drifting toward venue presence. Solved cold start by manufacturing density (scheduled moments). Their "3M+ users" claim failed verification 0-3 — treat self-reported traction skeptically. |
| 4 | Sit By Me (sitbyme.co) | Presence map at partner venues (green "open to chat" / red "quiet") | Profiles | Milwaukee only + 4 venues in Wausau, WI. Denver/Chicago/Atlanta are waitlists, not live | Closest mechanic + same two-sided model, weakest executor. Solo founder, agency-built (Cardiff App Developers), no funding as of mid-2025, $4.99/mo premium gates seeing who's at a venue (paywalls the core loop pre-density). Benchmark, not predator. |
| 5 | Mmotion | Ambient location-sharing (Snap Map rival), interest "Circles" | Profiles, application-gated | NYC, capped 1,000-member beta | Celebrity halo (Knicks' Miles McBride co-founder) but minimal mechanic overlap. Steal their idea: capped, application-gated alpha. |
Honorable mentions: Proxii (SF bar-matching, 2022, never took off — cautionary tale in our own market), Roomvine (anonymous venue chat rooms, small), curated-events wave (222, Pie, Clyx ~$14M raised, Washed Up, Les Amís, Meet5).
Sit By Me detail (most-studied competitor)
- Timeline: App Store v1.0 Dec 2022 was a dormant placeholder; real development started Feb 2025. ~3,200 self-reported users, 27 App Store ratings, ~3 named Milwaukee partners + 4 Wausau venues after ~16 months of real effort.
- Monetization: venues = "Community Connection Point" partnerships, no public pricing (sales via mailto), ~$300/mo per founder conversations; users = $4.99/mo premium gating who's-at-venue visibility, venue discounts, pre-event messaging.
- Stack: outsourced to Cardiff App Developers (Welsh generalist agency); cross-platform single codebase (likely React Native); Next.js admin; WordPress site; Stripe payment links; boilerplate EULA, no privacy policy on site despite live-GPS app.
- Release cadence = paid agency sprints (bursts around milestones, silence between). Tripwire: sustained weekly 1.2.x/2.x releases = they found funding/team.
Venue-side pricing benchmarks
Yelp Guest Manager: $129–159/mo (Basic), $279–349/mo (Plus). Yelp Ads: from ~$5/day (~$150/mo). So ~$300/mo venue SaaS is normal-range pricing — Sit By Me's problem is value delivered (3,200 users, no attribution), not the number. Implication: venue budget lines at $150–300/mo exist; price there after attribution receipts exist, not before.
Lessons from the prior presence wave (2012–2016 graveyard)
Highlight, Sonar, Foursquare check-ins all died of the same pair: density never arrived and always-on background broadcasting (battery drain + creepiness). Lantern's mechanic dodges the second by design (opt-in, momentary, venue-bounded, off by default). The first is still our dragon — mitigations: merchant offers give the empty map a floor; alpha should manufacture density via scheduled lantern evenings (Timeleft's lesson), not wait for ambient adoption.
Where Lantern is weaker (honest section)
- Cold start, amplified by anonymity — a profile app with no density still has people to browse; Lantern with no density is a dark map.
- Anonymity vs safety perception — every competitor chose profiles; Venue made mandatory verification a selling point. Our structural safety case (public venues only, no location persistence, no browsable identity) must be made visibly in-product. Alpha must measure women's comfort explicitly.
- PWA-only distribution — all five competitors are native. No app-store discovery; iOS install friction. Counterweight: QR-at-venue instant install fits our acquisition geometry. App-store wrapper decision needed before public launch.
- Solo capacity — we outrun Sit By Me's rented velocity; we would not outrun a funded team. Alpha evidence (retention, approach rate, merchant receipts) is the uncopyable asset.
- Name collision — lanterndating.com (2021 dating app, same trademark class), lanterns.app, withlantern.com, golantern.com. Resolve trademark before public marketing exists.
Quarterly tripwires
- Venue surfacing anywhere (especially funded, especially CA)
- Tinder Events announcing San Diego / SF
- Timeleft extending "Last Drinks" toward open venue presence
- Sit By Me cadence shift to sustained weekly releases
- Any new funded presence-mechanic entrant
Foursquare
Key Differences
| Aspect | Lantern | Foursquare |
|---|---|---|
| Core Purpose | Anonymous real-time social connection at venues | Venue discovery, ratings, and check-in gamification |
| Identity | Anonymous by default - no photos, no names, no profiles | Public profiles with photos, friends lists, badges |
| Goal | Facilitate meeting people in person at venues | Track visits, earn points/badges, find places to go |
| Visibility | Only your interests & mood visible (not identity) | Full profile, check-in history visible to friends |
| Interaction Model | "Wave" to signal interest → meet offline | Comments, likes, tips, digital social engagement |
| Privacy | Zero-knowledge encryption, presence-based signals | Data collection for recommendations & ads |
| Philosophy | "Presence over profiles" - moment-based | Gamified location tracking, mayorships |
Lantern's Unique Approach
- No profile optimization - No photos, bios, or swiping
- Real places as safety boundaries - Must physically be at a venue (verified within 100m)
- Temporary signals - Lanterns auto-extinguish after 2 hours
- Consent-first - The "lit lantern" is a clear signal saying "I'm open to meeting"
- Interest-based matching - Share what you're interested in (conversation, activity, quiet company), not who you are
Essentially, Foursquare is about tracking where you go and building a digital history, while Lantern is about meeting someone right now at a venue without exposing your identity until you choose to connect in person.
Left Field
Key Differences
| Aspect | Lantern | Left Field |
|---|---|---|
| Core Purpose | Anonymous real-time presence-based connection at venues | AI-curated compatibility matching based on social overlaps |
| Discovery Model | See who's available right now at a specific venue | Receive limited "drops" (2/week) with curated matches |
| Identity | Anonymous by default - no photos, names, or profiles | Profile-based with mutual connections highlighted |
| Matching Logic | Interests & mood shared at a venue; no algorithmic matching | AI analyzes shared contexts (mutual friends, locations, hometowns, colleges) |
| Volume | Unlimited - see all lit lanterns at nearby venues | Limited drops to avoid swipe fatigue |
| Real-Time Element | Live presence - only see people currently at a venue | Asynchronous - matches delivered periodically |
| Location Role | Must be physically at the venue (verified within 100m) | Location used for background compatibility scoring |
| Interaction Model | "Wave" to signal interest → meet immediately in person | Receive personalized notes → chat first, then meet |
| Privacy Philosophy | Zero-knowledge encryption; anonymous until you choose to engage | Profile visible; trust built through mutual social graph |
| Connection Trigger | Being at the same place right now | Shared history (friends, places, schools) |
| Anti-Swipe Approach | No swiping - show up and signal availability | No swiping - AI selects for you |
| Philosophy | "Presence over profiles" - moment-based | "Feels like a setup from friends" - context-based |
Lantern's Unique Approach
Lantern is about spontaneous, anonymous, in-the-moment connections — you're at a bar, you light your lantern, someone waves, you meet right there.
Left Field is about curated, trust-based introductions — AI finds people with shared social contexts and delivers limited, high-quality matches with explanations of why you might connect.
Both apps reject traditional swiping, but:
- Lantern = "I'm here now, open to meeting"
- Left Field = "We have things in common, you should meet"
Other Competitors
Direct Competitors (Location + Real-Time + Meeting)
| App | Overlap with Lantern | Key Difference |
|---|---|---|
| Happn | Shows people you've crossed paths with | Profile-based, not anonymous; retrospective not real-time |
| NeverMissed | Venue-based connections | Event/concert focused; profile-based |
| Blendr | Proximity-based meetups | More traditional profile/chat approach |
Privacy-Focused Dating
| App | Overlap with Lantern | Key Difference |
|---|---|---|
| PURE | Anonymous, no profile optimization | Hookup-focused; time-limited requests; not venue-anchored |
| Feeld | Privacy-conscious, interest-based | Profile-based; focused on alternative lifestyles |
| Blindmate | Friends set you up anonymously | Requires friend involvement; not real-time |
Anti-Swipe / Curated Matching
| App | Overlap with Lantern | Key Difference |
|---|---|---|
| Left Field | Limited matches, anti-swipe fatigue | AI-curated based on social graph; not real-time |
| Hinge | "Designed to be deleted" | Still profile/photo-based; swipe mechanics |
| Thursday | Time-limited to encourage action | Only works one day/week; still profile-based |
| Coffee Meets Bagel | Limited daily matches | Curated but still traditional profiles |
Interest/Activity-Based
| App | Overlap with Lantern | Key Difference |
|---|---|---|
| Meetup | Real places, shared interests | Group-focused, not 1:1; not anonymous |
| Bumble BFF | Interest-based connections | Friendship-focused; profile-based |
| Friender | Activity-based matching | Platonic; profile-based |
Real-Time Social
| App | Overlap with Lantern | Key Difference |
|---|---|---|
| Zenly (discontinued) | Real-time location sharing | Friend groups only; full identity visible |
| BeReal | Authenticity, anti-optimization | Photo-based; friend network; not for meeting strangers |
Venue/Nightlife Specific
| App | Overlap with Lantern | Key Difference |
|---|---|---|
| Spot | Bar/venue connections | More traditional matching at venues |
| Wingman | Friends help you match at bars | Requires friend involvement |
Lantern's Unique Differentiators
What sets Lantern apart from all competitors:
- Anonymous by default — No photos, no profiles to optimize
- Presence = the signal — Being somewhere IS the introduction
- Venue-verified — Must physically be there (100m verification)
- Zero-knowledge encryption — Privacy at the technical level
- Temporary signals — Lanterns expire (2 hours), not persistent
- No algorithmic matching — You choose where to show up, not who to swipe on
- Immediate offline interaction — Wave → meet in person (no chat-first)
Closest Conceptual Competitors
| App | What They Share | What Lantern Does Differently |
|---|---|---|
| Happn | Location awareness | Real-time presence (not retrospective); anonymous; venue-anchored |
| PURE | Anonymity, anti-profile | Venue-verified; not hookup-focused; in-person-first |
| Left Field | Anti-swipe philosophy | Real-time presence; no AI curation; anonymous |
| Thursday | Time-limited urgency | Always available; venue-based not day-based |