NeighborHub
Your community, connected.
NeighborHub is a multi-tenant SaaS platform for HOA community management. It helps management companies and self-managed associations run board operations, communicate with residents, handle private requests, and accept assessment payments while preserving each community's data ownership, authorization boundaries, and immutable audit history. The current build is focused on the back-end services, workers, models, and functions that make the platform trustworthy before the public UI is wired.
Screenshots are coming
The NeighborHub team is currently perfecting the back-end services, workers, models, and functions. UI integration happens once the foundation is sound.
What NeighborHub does
A multi-tenant SaaS platform for HOA community management.
Community-owned tenants
Every community is an independent tenant that owns its data. Management companies and self-managed associations each get a clear, isolated boundary.
Tenant isolation by design
Master and child associations are isolated. Shared managers, payers, or addresses never imply cross-tenant access. Scope is derived from persisted records, not route values.
Board operations
Versioned board meetings, agendas, motions with attributable roll-call votes, minutes, review, approval, lock, and linked amendments.
Resident communications
Non-official announcements, advisory owner polls, and resident document libraries — each with a narrow, explicit audience and immutable evidence.
Assessment payments
Imported balance snapshots, processor-managed payee accounts, resident checkout, reconciliation support, and dual-control refunds.
Identity and access
People, accounts, ownership, occupancy, board offices, and role assignments are modeled separately. Access requires a verified property relationship and a constrained role.
Safe onboarding and imports
Community, roster, property, unit, and balance CSV imports with validation, preview, error reporting, and safe retries. Evidence-assisted property claims with human review.
Dual control and audit
Sensitive financial actions require a different initiator and approver. Every official, financial, and support action leaves append-only, immutable evidence.
Capabilities
Built for the real operational, legal, and security context of community management.
Community and portfolio administration
Management companies can operate explicitly delegated communities without taking ownership. A community can replace its management company, change its payer, and export its data without interruption. Portfolio administration, staff assignments, and billing umbrellas stay separate from community data.
Official records that behave like records
Meetings, agendas, motions, votes, and minutes move through draft, review, approval, and lock states. Locked records cannot be silently edited. Corrections flow through linked, attributable amendments. The system records the evidence; it does not certify legal sufficiency.
Resident operations with real boundaries
Announcements, advisory polls, documents, and private requests are each governed by their own restrictive policy. Resident access is tied to a current, verified property relationship and a constrained Owner assignment. No role, office, or descriptive fact grants access by implication.
Payments without becoming the ledger
Neighborhub accepts imported balance snapshots, creates payment intents, and reconciles provider events. It does not hold community funds, calculate authoritative balances, or store raw payment credentials. Refunds and payout changes require dual control.
Evidence-assisted property claims
Human residents begin claims through accepted invitations. Approval requires at least two independently sourced evidence classes and a fixed, community-scoped reviewer who is a different person from the claimant. Conflicts and high-risk cases require a second independent reviewer.
Authorization that separates identity from authority
A valid login proves authentication only. Every protected operation re-checks the current person, account, principal, session, MFA, role assignment, relationship, delegation, and authorization epoch. Workers reauthorize before every protected read or effect.
Atomic evidence and durable obligations
Business state, immutable audit evidence, and outbox obligations commit in one transaction. External effects become explicit, idempotent, queryable obligations. Provider events enter a durable inbox with raw-body verification, deduplication, conservative ordering, and reconciliation.
Provider-neutral, portable architecture
The core is a strict TypeScript modular monolith: Next.js, NestJS/Fastify, PostgreSQL, Drizzle, Graphile Worker, and OpenTelemetry. Web, API, worker, database, object storage, and provider adapters are separate by contract. Domain logic never depends on a specific vendor.
Back end first, UI second
NeighborHub is in the foundation stage. The current build is focused on services, workers, data models, and domain functions — the parts that have to be right before a resident or board interface can be trustworthy.
This means there are no public screenshots yet. The interface will be wired once the multi-tenancy, authorization, audit, governance, payments, and resident workflows are locked down and tested against their acceptance scenarios.
It is a slower, more deliberate path than most startups take, and it is why NeighborHub is being built to survive real customers, real disputes, and real transitions of management.
Service boundaries
Web, API, worker, database, object storage, and provider adapters are separated by contract before any UI is wired.
Models and functions
Community, identity, governance, resident, payment, and lifecycle domains are modeled with explicit state machines, commands, and invariants.
Workers and queues
Graphile Worker-backed jobs with durable outbox/inbox semantics, bounded retries, explicit holds, and execution-time reauthorization.
Security hardening
Forced PostgreSQL RLS, authenticated tenant context, append-only command records, and security-definer interfaces are in place before the resident interface is built.
Who it is for
Designed for the people and organizations that run communities.
Management companies
Run multiple communities from one portfolio while keeping each tenant isolated and independently controllable.
Self-managed HOAs
Operate a single community with the same governance, communication, and payment tools as larger portfolios.
Board directors
Participate in meetings, motions, and votes with exact assigned authority — no more, no less.
Residents
View authorized records, respond to polls, read documents, submit requests, and make payments through a verified property relationship.
Build a platform with Pulsar
NeighborHub is in active development. If you manage communities, serve HOAs, or need a similar multi-tenant platform, we would love to talk.