HAVEN

Communities run on a patchwork of tools. Members struggle with scattered communication, outdated calendars, and a separate login for every community.

Many neighborhoods, clubs and residential communities depend on outdated tools or third parties. Administrators rely on developers or manual processes to set up facility reservations, events and payments. The result is confusion, wasted time, and missed opportunities for connection.

From a user interview

We juggle spreadsheets, calls, and separate apps. It works, but it is far from simple.

Give communities independence and simplicity: create and run a community in minutes, without a developer.

• For administrators

  Households, dues, facilities, events, guests, announcements and documents, all from one dashboard.

• For members

  One account for every community. Switch between them to book facilities, join events, invite guests and stay informed.

Two groups that depend on each other.

• Primary

  Administrators

  Property managers, club administrators and HOA boards who need a professional way to run their community without outside technical help.

• Secondary

  Members

  People who take part in daily community life and want one easy, unified way to interact with every community they belong to.

Early research and interviews, a review of competing platforms, and low fidelity prototypes tested with both user groups surfaced three insights.

1. A

   Admins are frustrated by fragmentation

   Many rely on disconnected platforms or expensive websites built to order.

2. B

   Members want everything in one place

   Bookings, events and announcements, convenient and accessible.

3. C

   Flexibility and control are key

   Admins want to manage everything themselves; members want a modern experience that feels effortless.

Where existing tools stop

None of them let people manage several communities from one account. That gap became the foundation of how HAVEN is structured.

HAVEN is four products that share one TypeScript core: a member app for iOS and Android, an admin dashboard for running the community, a marketing site with public community pages, and secure payment pages.

• Households and dues

  Households are the billing unit. Admins set recurring dues with reminders and grace periods, and members pay by card, bank or offline where the community allows it.

• Facility bookings

  Hours, capacity, prices and booking limits per facility. A slot is held for a few minutes while a member pays, so two people can never book the same time.

• Guest passes

  Members invite guests, who receive a QR pass by email styled in the community's colors.

• Events

  Recurring events with registration, waitlists and tickets.

• Activity

  One calendar showing bookings, events, dues and announcements across every community a member belongs to.

• Announcements and documents

  Scheduled announcements for the whole community or one household, plus bylaws, rules and forms in one place.

Backend

Supabase with PostgreSQL, more than 140 versioned migrations, 27 Edge Functions, role based access and scheduled jobs for dues, notifications and refunds.

Payments

Stripe Connect sends money directly to each community, with itemized fees. If a facility closes or a paid slot is no longer available, the member is refunded in full automatically, with retries and webhook reconciliation behind it.

Quality

Automated tests across the database, server functions, admin dashboard and mobile app.

HAVEN is in active development and preparing to launch with its first communities.

The marketing site is live at havencommunity.app.