# Build brief — a focused alternative to Circle

> **Verdict:** Partly, if you narrow it · **Buildability:** 58/100 · **Category:** Community
> **Source:** https://www.canitbevibecoded.com/circle
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Circle. Verify current pricing and capabilities before acting.

## Context

**Circle** — Community platform for memberships, courses, live events, and payments. It currently costs $99/mo.

A private forum/community is buildable, but Circle's value is member management, courses, events, payments, mobile apps, automations, AI, and migrations.

This brief describes a focused, single-operator replacement for the part of Circle that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Self-host or build a private community with posts, spaces, members, access roles, payments, and notifications.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Auth.
- Database.
- Forum/community app.
- Payments.
- Email/push notifications.
- Hosting.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a small private community site to replace Circle. Requirements:

- Scope honestly: this is for a group of a few dozen people. If it needs
  payments or hundreds of members, self-host Discourse instead, and say so
  in the README.
- Node + Express + better-sqlite3, server-rendered EJS plus htmx, no build
  step.
- Spaces I create, threads with Markdown posts and replies (marked),
  newest-activity-first listing.
- Magic-link auth: a member enters an email that must already be on my
  invite list and receives a login link via Resend (key in .env). No
  passwords, no self-signup.
- Email notifications: reply-to-your-thread immediately, plus a daily digest
  of new threads, with per-member mute toggles.
- Member profiles: name, avatar (resized with sharp), joined date, post
  count.
- Moderation for me only: delete post, remove member.
- Deploys on a $5 VPS behind Caddy; one SQLite file with a nightly dump.
- Out of scope: payments and memberships, courses, live events, and mobile
  apps. Member operations at scale are the Circle product.
- README: deploy steps and Resend setup.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Polished member UX.
- Mobile apps.
- Payments.
- Course/events integration.
- The value comes from the people already using it.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Discourse](https://github.com/discourse/discourse) — Mature open-source community/forum software suitable for many Circle-like communities

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/circle