Purpose
Boards ask the same three questions before approving software from a small vendor: where does it run, how do we get our data out, and what happens if the company goes away. This page answers them on one printable sheet. Every statement describes the service as it is today; changes are recorded in the history at the bottom.
Where the service runs
- Application. Amazon Web Services, US West (N. California) region: containers on ECS Fargate behind an application load balancer, with Cloudflare in front for DNS and TLS. Deployments are automated through AWS CodePipeline from a single source repository.
- Database. Supabase-managed PostgreSQL in the same region. Supabase is a managed provider; NeighborlyEvents does not operate its own database servers.
- Files and email. Uploaded photos, flyers and documents live in Amazon S3. Email is sent through Amazon SES.
- Second deployment. A second copy of the application runs on owner-operated hardware and serves neighborlyevents.dev against the same database. It is application-tier redundancy — if AWS compute is unavailable the service can be reached there — and it is not a database failover: both deployments depend on the single managed database.
Backups and recovery
- Database. Supabase takes a full physical backup of the production database every day (around midnight UTC) and retains seven days of them on our plan. A backup can be restored into a fresh project without touching production, which is how restores are tested. Point-in-time recovery is available as an add-on and is not enabled today.
- Restore test. Last run 9 September 2026: the previous night's backup was restored into a fresh project, the row counts for users, events and registrations and the latest registration timestamp matched production as of the backup time, and the test project was then deleted. Repeated at least every six months.
- Uploaded files. The S3 buckets keep prior versions of every object — 90 days for community uploads, one year for financial documents — so an accidental overwrite or deletion can be reversed.
- Configuration and secrets are held in encrypted configuration in the source repository, and the infrastructure is defined as code, so the environment can be recreated from the repository.
Your data is portable
- Whole-community archive. From the organizer console (Data export), the neighborhood owner can build a single download of everything the community holds: events with registrations, check-ins and question responses; members with the address on file; organizers; clubs with rosters, dues, polls and votes; facilities and reservations; volunteer roles, shifts and assignments; refunds and payment disputes; communications history (what was sent to whom and when); policy acceptances; and gallery photos by reference. Clubs have the same export for their own data. It is available on every plan, including the free plan, and every export is logged with who requested it.
- Formats. Plain CSV files plus a JSON manifest that names every file and column; no proprietary formats. Photos and documents are referenced by URL, not copied. The archive is kept for seven days after it is built and then removed.
- Per-surface exports. Organizers can also export from individual screens as CSV: a single event's registrations, budgets, reimbursement ledgers, contest results and inventory. Members can request a copy or deletion of their own account data.
If NeighborlyEvents winds down
If the service is going to close, every organizer will receive at least 90 days' written notice, the whole-community archive will be provided before closure, and data will be deleted 90 days after the service closes unless you ask for earlier deletion.
Source code escrow
Source-code escrow is available on request, at cost, for negotiated agreements: an independent escrow agent holds the application code, deployment scripts and the credentials needed to run it, and releases them to the community if NeighborlyEvents ceases operations. Communities on self-serve plans rely on the export and wind-down commitments above.
Key-person risk, plainly
NeighborlyEvents is built and operated by a single founder. What limits the risk of that: the service runs entirely on managed, mainstream infrastructure (AWS, Supabase, Stripe, Cloudflare) with no bespoke servers to inherit; deployments and infrastructure are fully scripted from one repository; money never sits with NeighborlyEvents for ticket sales and dues — it settles to your own Stripe account (see How the money works); and your data is exportable in open formats.
Contact
Continuity questions, including escrow and data-return requests: [email protected].