Vibecode Bazzly
track this build5 steps, step by step0%KINDA · weekend project
The listening half of this is not hard: Reddit exposes search and subreddit feeds, and an agent can rank hits for relevance and draft a comment in your voice by lunchtime. The half you cannot build is the account layer, meaning aged handles with real karma, subreddit-specific posting history, and enough trust to not get shadowbanned on the first link drop. If you are promoting one product from one account you actually own and post from, the DIY version covers most of the real value. If the reason you were paying is account inventory and rotation, no amount of code fixes that, because the scarce thing is time served on someone else's platform. Also worth saying out loud: the moment you are automating replies from accounts that are not yours, you are doing the thing Reddit bans people for, and no tool makes that safe.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Bazzly. 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 ===== # Bazzly indie build ## Goal Build the smallest trustworthy replacement for the core Bazzly workflow for one developer or a tiny team. ## Scope Polls Reddit search and chosen subreddits on a schedule, scores each new post for how relevant it is to your product, and drafts a comment or DM you approve before anything is posted. ## 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: - Aged, high-karma accounts with credible posting history - Multi-account rotation, proxies, and whatever ban-avoidance heuristics they have learned the hard way - Their curated map of which subreddits tolerate product mentions and which will nuke you - A hosted dashboard, team seats, and shared approval queues - Someone else's problem when the API terms or rate limits change If those capabilities are essential, use Bazzly 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 a local Reddit opportunity monitor called reddit-radar. No hosting, no accounts, no telemetry. Stack, no substitutions: - TypeScript on Node 20, run with tsx - SQLite via better-sqlite3 for storage - snoowrap for the Reddit API - A single Hono server on port 8787 serving a plain server-rendered HTML review page, no React, no build step - Secrets in .env: REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_REFRESH_TOKEN, REDDIT_USER_AGENT, OPENAI_API_KEY Config lives in config.json at repo root: product name, one paragraph product description, list of subreddits to watch, list of search keywords, and a minimum relevance score from 0 to 100. What it does: 1. A poll command fetches new posts from each watched subreddit and results for each keyword from Reddit search, deduping by post id against SQLite. 2. For each new post, one LLM call returns strict JSON: relevance score 0-100, a one line reason, whether the post is actually asking for a recommendation, and a suggested reply of at most 120 words written as a normal human who happens to have built the thing. 3. Store everything. Anything at or above the minimum score lands in a review queue. 4. The web page lists the queue newest first: subreddit, title, score, reason, link to the thread, the draft reply in an editable textarea, and buttons for Copy, Dismiss, and Mark handled. Explicitly out of scope, do not build these: posting or commenting through the API, DM sending, multiple account support, proxy rotation, scheduling of posts. This tool suggests, the human posts. Print a warning at startup saying exactly that. Also include: respect Reddit rate limits with a simple queue and backoff, an npm script for a cron style loop every 30 minutes, a seeded demo mode that works with fake data and no API keys, and a README with how to get a Reddit refresh token for a script app. When done, run the demo mode and show me the review page output. ## Required capabilities - Reddit account and a script-type OAuth app with client id and secret - An LLM API key for relevance scoring and drafting - Somewhere to run a cron job, a laptop is fine - Willingness to read Reddit's API terms and each subreddit's self-promo rules ## 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 Bazzly. 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 ===== # Bazzly indie build ## Goal Build the smallest trustworthy replacement for the core Bazzly workflow for one developer or a tiny team. ## Scope Polls Reddit search and chosen subreddits on a schedule, scores each new post for how relevant it is to your product, and drafts a comment or DM you approve before anything is posted. ## 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: - Aged, high-karma accounts with credible posting history - Multi-account rotation, proxies, and whatever ban-avoidance heuristics they have learned the hard way - Their curated map of which subreddits tolerate product mentions and which will nuke you - A hosted dashboard, team seats, and shared approval queues - Someone else's problem when the API terms or rate limits change If those capabilities are essential, use Bazzly 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 a local Reddit opportunity monitor called reddit-radar. No hosting, no accounts, no telemetry. Stack, no substitutions: - TypeScript on Node 20, run with tsx - SQLite via better-sqlite3 for storage - snoowrap for the Reddit API - A single Hono server on port 8787 serving a plain server-rendered HTML review page, no React, no build step - Secrets in .env: REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_REFRESH_TOKEN, REDDIT_USER_AGENT, OPENAI_API_KEY Config lives in config.json at repo root: product name, one paragraph product description, list of subreddits to watch, list of search keywords, and a minimum relevance score from 0 to 100. What it does: 1. A poll command fetches new posts from each watched subreddit and results for each keyword from Reddit search, deduping by post id against SQLite. 2. For each new post, one LLM call returns strict JSON: relevance score 0-100, a one line reason, whether the post is actually asking for a recommendation, and a suggested reply of at most 120 words written as a normal human who happens to have built the thing. 3. Store everything. Anything at or above the minimum score lands in a review queue. 4. The web page lists the queue newest first: subreddit, title, score, reason, link to the thread, the draft reply in an editable textarea, and buttons for Copy, Dismiss, and Mark handled. Explicitly out of scope, do not build these: posting or commenting through the API, DM sending, multiple account support, proxy rotation, scheduling of posts. This tool suggests, the human posts. Print a warning at startup saying exactly that. Also include: respect Reddit rate limits with a simple queue and backoff, an npm script for a cron style loop every 30 minutes, a seeded demo mode that works with fake data and no API keys, and a README with how to get a Reddit refresh token for a script app. When done, run the demo mode and show me the review page output. ## Required capabilities - Reddit account and a script-type OAuth app with client id and secret - An LLM API key for relevance scoring and drafting - Somewhere to run a cron job, a laptop is fine - Willingness to read Reddit's API terms and each subreddit's self-promo rules ## 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 Bazzly. 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 ===== # Bazzly product brief ## Problem The listening half of this is not hard: Reddit exposes search and subreddit feeds, and an agent can rank hits for relevance and draft a comment in your voice by lunchtime. The half you cannot build is the account layer, meaning aged handles with real karma, subreddit-specific posting history, and enough trust to not get shadowbanned on the first link drop. If you are promoting one product from one account you actually own and post from, the DIY version covers most of the real value. If the reason you were paying is account inventory and rotation, no amount of code fixes that, because the scarce thing is time served on someone else's platform. Also worth saying out loud: the moment you are automating replies from accounts that are not yours, you are doing the thing Reddit bans people for, and no tool makes that safe. ## Product outcome Polls Reddit search and chosen subreddits on a schedule, scores each new post for how relevant it is to your product, and drafts a comment or DM you approve before anything is posted. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Reddit account and a script-type OAuth app with client id and secret - An LLM API key for relevance scoring and drafting - Somewhere to run a cron job, a laptop is fine - Willingness to read Reddit's API terms and each subreddit's self-promo rules ## Explicit non-goals for v1 - Aged, high-karma accounts with credible posting history - Multi-account rotation, proxies, and whatever ban-avoidance heuristics they have learned the hard way - Their curated map of which subreddits tolerate product mentions and which will nuke you - A hosted dashboard, team seats, and shared approval queues - Someone else's problem when the API terms or rate limits change ## 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 a local Reddit opportunity monitor called reddit-radar. No hosting, no accounts, no telemetry. Stack, no substitutions: - TypeScript on Node 20, run with tsx - SQLite via better-sqlite3 for storage - snoowrap for the Reddit API - A single Hono server on port 8787 serving a plain server-rendered HTML review page, no React, no build step - Secrets in .env: REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_REFRESH_TOKEN, REDDIT_USER_AGENT, OPENAI_API_KEY Config lives in config.json at repo root: product name, one paragraph product description, list of subreddits to watch, list of search keywords, and a minimum relevance score from 0 to 100. What it does: 1. A poll command fetches new posts from each watched subreddit and results for each keyword from Reddit search, deduping by post id against SQLite. 2. For each new post, one LLM call returns strict JSON: relevance score 0-100, a one line reason, whether the post is actually asking for a recommendation, and a suggested reply of at most 120 words written as a normal human who happens to have built the thing. 3. Store everything. Anything at or above the minimum score lands in a review queue. 4. The web page lists the queue newest first: subreddit, title, score, reason, link to the thread, the draft reply in an editable textarea, and buttons for Copy, Dismiss, and Mark handled. Explicitly out of scope, do not build these: posting or commenting through the API, DM sending, multiple account support, proxy rotation, scheduling of posts. This tool suggests, the human posts. Print a warning at startup saying exactly that. Also include: respect Reddit rate limits with a simple queue and backoff, an npm script for a cron style loop every 30 minutes, a seeded demo mode that works with fake data and no API keys, and a README with how to get a Reddit refresh token for a script app. When done, run the demo mode and show me the review page output. ## 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 Bazzly capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Bazzly indie build ## Goal Build the smallest trustworthy replacement for the core Bazzly workflow for one developer or a tiny team. ## Scope Polls Reddit search and chosen subreddits on a schedule, scores each new post for how relevant it is to your product, and drafts a comment or DM you approve before anything is posted. ## 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: - Aged, high-karma accounts with credible posting history - Multi-account rotation, proxies, and whatever ban-avoidance heuristics they have learned the hard way - Their curated map of which subreddits tolerate product mentions and which will nuke you - A hosted dashboard, team seats, and shared approval queues - Someone else's problem when the API terms or rate limits change If those capabilities are essential, use Bazzly 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 a local Reddit opportunity monitor called reddit-radar. No hosting, no accounts, no telemetry. Stack, no substitutions: - TypeScript on Node 20, run with tsx - SQLite via better-sqlite3 for storage - snoowrap for the Reddit API - A single Hono server on port 8787 serving a plain server-rendered HTML review page, no React, no build step - Secrets in .env: REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_REFRESH_TOKEN, REDDIT_USER_AGENT, OPENAI_API_KEY Config lives in config.json at repo root: product name, one paragraph product description, list of subreddits to watch, list of search keywords, and a minimum relevance score from 0 to 100. What it does: 1. A poll command fetches new posts from each watched subreddit and results for each keyword from Reddit search, deduping by post id against SQLite. 2. For each new post, one LLM call returns strict JSON: relevance score 0-100, a one line reason, whether the post is actually asking for a recommendation, and a suggested reply of at most 120 words written as a normal human who happens to have built the thing. 3. Store everything. Anything at or above the minimum score lands in a review queue. 4. The web page lists the queue newest first: subreddit, title, score, reason, link to the thread, the draft reply in an editable textarea, and buttons for Copy, Dismiss, and Mark handled. Explicitly out of scope, do not build these: posting or commenting through the API, DM sending, multiple account support, proxy rotation, scheduling of posts. This tool suggests, the human posts. Print a warning at startup saying exactly that. Also include: respect Reddit rate limits with a simple queue and backoff, an npm script for a cron style loop every 30 minutes, a seeded demo mode that works with fake data and no API keys, and a README with how to get a Reddit refresh token for a script app. When done, run the demo mode and show me the review page output. ## Required capabilities - Reddit account and a script-type OAuth app with client id and secret - An LLM API key for relevance scoring and drafting - Somewhere to run a cron job, a laptop is fine - Willingness to read Reddit's API terms and each subreddit's self-promo rules ## 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
# Bazzly product brief ## Problem The listening half of this is not hard: Reddit exposes search and subreddit feeds, and an agent can rank hits for relevance and draft a comment in your voice by lunchtime. The half you cannot build is the account layer, meaning aged handles with real karma, subreddit-specific posting history, and enough trust to not get shadowbanned on the first link drop. If you are promoting one product from one account you actually own and post from, the DIY version covers most of the real value. If the reason you were paying is account inventory and rotation, no amount of code fixes that, because the scarce thing is time served on someone else's platform. Also worth saying out loud: the moment you are automating replies from accounts that are not yours, you are doing the thing Reddit bans people for, and no tool makes that safe. ## Product outcome Polls Reddit search and chosen subreddits on a schedule, scores each new post for how relevant it is to your product, and drafts a comment or DM you approve before anything is posted. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Reddit account and a script-type OAuth app with client id and secret - An LLM API key for relevance scoring and drafting - Somewhere to run a cron job, a laptop is fine - Willingness to read Reddit's API terms and each subreddit's self-promo rules ## Explicit non-goals for v1 - Aged, high-karma accounts with credible posting history - Multi-account rotation, proxies, and whatever ban-avoidance heuristics they have learned the hard way - Their curated map of which subreddits tolerate product mentions and which will nuke you - A hosted dashboard, team seats, and shared approval queues - Someone else's problem when the API terms or rate limits change ## 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 a local Reddit opportunity monitor called reddit-radar. No hosting, no accounts, no telemetry. Stack, no substitutions: - TypeScript on Node 20, run with tsx - SQLite via better-sqlite3 for storage - snoowrap for the Reddit API - A single Hono server on port 8787 serving a plain server-rendered HTML review page, no React, no build step - Secrets in .env: REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_REFRESH_TOKEN, REDDIT_USER_AGENT, OPENAI_API_KEY Config lives in config.json at repo root: product name, one paragraph product description, list of subreddits to watch, list of search keywords, and a minimum relevance score from 0 to 100. What it does: 1. A poll command fetches new posts from each watched subreddit and results for each keyword from Reddit search, deduping by post id against SQLite. 2. For each new post, one LLM call returns strict JSON: relevance score 0-100, a one line reason, whether the post is actually asking for a recommendation, and a suggested reply of at most 120 words written as a normal human who happens to have built the thing. 3. Store everything. Anything at or above the minimum score lands in a review queue. 4. The web page lists the queue newest first: subreddit, title, score, reason, link to the thread, the draft reply in an editable textarea, and buttons for Copy, Dismiss, and Mark handled. Explicitly out of scope, do not build these: posting or commenting through the API, DM sending, multiple account support, proxy rotation, scheduling of posts. This tool suggests, the human posts. Print a warning at startup saying exactly that. Also include: respect Reddit rate limits with a simple queue and backoff, an npm script for a cron style loop every 30 minutes, a seeded demo mode that works with fake data and no API keys, and a README with how to get a Reddit refresh token for a script app. When done, run the demo mode and show me the review page output. ## 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 Bazzly 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
Because karma cannot be compiled. People pay for the part of the product that is a stockpile of trusted accounts and a running list of which communities will let a link live for more than eleven minutes, and both of those are accumulated rather than built. There is also the boring reason: the DIY build gives you a feed of opportunities, and most people do not want a feed, they want the comment already posted, by something that looks like a person who has been on Reddit for six years.
xAged, high-karma accounts with credible posting history
xMulti-account rotation, proxies, and whatever ban-avoidance heuristics they have learned the hard way
xTheir curated map of which subreddits tolerate product mentions and which will nuke you
xA hosted dashboard, team seats, and shared approval queues
xSomeone else's problem when the API terms or rate limits change
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Bazzly ($99/mo) with one prompt"
Vibecode Bazzly
Kinda. The core of Bazzly is buildable in a weekend with the prompt on this page, but there are real gaps: Aged, high-karma accounts with credible posting history, Multi-account rotation, proxies, and whatever ban-avoidance heuristics they have learned the hard way. Read the honest list above before committing.
How much does Bazzly cost?
Bazzly costs about $99/month (All in One (single plan), checked 2026-08-18), which is $1188 per year.
What do I lose by replacing Bazzly?
Honestly: Aged, high-karma accounts with credible posting history; Multi-account rotation, proxies, and whatever ban-avoidance heuristics they have learned the hard way; Their curated map of which subreddits tolerate product mentions and which will nuke you; A hosted dashboard, team seats, and shared approval queues; Someone else's problem when the API terms or rate limits change. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Bazzly?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.