Vibecode Circle
track this build5 steps, step by step0%KINDA · weekend project
A private forum/community is buildable, but Circle's value is member management, courses, events, payments, mobile apps, automations, AI, and migrations.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Circle. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Circle indie build ## Goal Build the smallest trustworthy replacement for the core Circle workflow for one developer or a tiny team. ## Scope Self-host or build a private community with posts, spaces, members, access roles, payments, and notifications. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - polished member UX - mobile apps - payments - course/events integration - automations - migrations - community admin If those capabilities are essential, use Discourse instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build 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. ## Required capabilities - auth - database - forum/community app - payments - email/push notifications - hosting ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Circle. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Circle indie build ## Goal Build the smallest trustworthy replacement for the core Circle workflow for one developer or a tiny team. ## Scope Self-host or build a private community with posts, spaces, members, access roles, payments, and notifications. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - polished member UX - mobile apps - payments - course/events integration - automations - migrations - community admin If those capabilities are essential, use Discourse instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build 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. ## Required capabilities - auth - database - forum/community app - payments - email/push notifications - hosting ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Circle. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Circle product brief ## Problem A private forum/community is buildable, but Circle's value is member management, courses, events, payments, mobile apps, automations, AI, and migrations. ## Product outcome Self-host or build a private community with posts, spaces, members, access roles, payments, and notifications. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - auth - database - forum/community app - payments - email/push notifications - hosting ## Explicit non-goals for v1 - polished member UX - mobile apps - payments - course/events integration - automations - migrations - community admin ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Circle capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Circle indie build ## Goal Build the smallest trustworthy replacement for the core Circle workflow for one developer or a tiny team. ## Scope Self-host or build a private community with posts, spaces, members, access roles, payments, and notifications. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - polished member UX - mobile apps - payments - course/events integration - automations - migrations - community admin If those capabilities are essential, use Discourse instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build 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. ## Required capabilities - auth - database - forum/community app - payments - email/push notifications - hosting ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Circle product brief ## Problem A private forum/community is buildable, but Circle's value is member management, courses, events, payments, mobile apps, automations, AI, and migrations. ## Product outcome Self-host or build a private community with posts, spaces, members, access roles, payments, and notifications. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - auth - database - forum/community app - payments - email/push notifications - hosting ## Explicit non-goals for v1 - polished member UX - mobile apps - payments - course/events integration - automations - migrations - community admin ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Circle capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
They pay because communities need engagement mechanics and member operations, not just threads.
xpolished member UX
xmobile apps
xpayments
xcourse/events integration
xautomations
xmigrations
xcommunity admin
share on X ↗"I just replaced Circle ($89/mo) with one prompt"
Don't feel like building it? These folks already made it free.
MoodleA school wearing work boots: courses, forums, calendars, badges and paid enrolment, without Circle's polished creator clubhouse.open source↗no votes, no pay-to-list · just what's real
Circle pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| professional | $89/workspace | — | Unlimited members; 3 admins; 10 moderators; 20 spaces; 200 GB storage; 100 live-stream attendees; 15 live-room participants; 10 live hours/month; 20 workflows; 2,500 AI actions/month; 5,000 Admin API calls/month; 2% transaction fee |
| business | $199/workspace | — | Unlimited members; 5 admins; 15 moderators; 30 spaces; 500 GB storage; 200 live-stream attendees; 20 live-room participants; 15 live hours/month; unlimited workflows; 2,500 AI actions/month; 30,000 Admin API calls/month; 1% transaction fee |
| plus | custom | — | Unlimited admins and moderators; flexible spaces/live limits; 1 TB storage; 10,000 Email Hub contacts; 0.5% transaction fee |
free tierno free tier; 14-day trial with no credit card and a 30-day money-back guarantee
billingmonthly prices published; annual billing is offered, but public annual-equivalent prices were not verified
hidden costsCircle adds 2%/1%/0.5% transaction fees on top of payment-processor fees. Overage/add-on examples: $10 per 1,000 AI actions; Admin API overages at $0.005/$0.002 per call; Headless MAU overages at $0.50/$0.30; extra admin $10/month; 10 extra moderators $20/month; 10 extra spaces $20/month; +100 live attendees $20/month; +10 live hours $50/month; Email Hub 10,000 contacts starts at +$99/month.
verified 2026-08-12 · source ↗
Vibecode Circle
Kinda. The core of Circle is buildable in a weekend with the prompt on this page, but there are real gaps: polished member UX, mobile apps. Read the honest list above before committing.
How much does Circle cost?
Circle costs about $89/month (Professional, checked 2026-08-12), which is $1068 per year.
What do I lose by replacing Circle?
Honestly: polished member UX; mobile apps; payments; course/events integration; automations; migrations; community admin. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Circle?
Yes: Moodle (A school wearing work boots: courses, forums, calendars, badges and paid enrolment, without Circle's polished creator clubhouse.) The prompt is for when you want it exactly your way.