Vibecode RADAAR
track this build5 steps, step by step0%NOT REALLY · don't bother
A basic scheduler can be recreated, but RADAAR's complete product · publishing, engagement, monitoring, analytics, team collaboration, asset management, approval workflows, and multi-network integrations · is not realistically replaceable in a weekend.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of RADAAR. 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 ===== # RADAAR indie build ## Goal Build the smallest trustworthy replacement for the core RADAAR workflow for one developer or a tiny team. ## Scope Schedule posts for one social platform, publish through the official API, manage a simple content calendar, and maintain reusable media assets. ## 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: - multi-network publishing - social inbox and engagement - social listening and keyword monitoring - advanced analytics and reporting - approval workflows - team collaboration - workspace management - media library - URL shortener and tracking - AI-assisted content workflows - API ecosystem - reliable hosted infrastructure If those capabilities are essential, use Postiz 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 personal replacement for RADAAR in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and exactly one official social-platform API; do not offer alternative stacks. The core loop is: create, schedule, preview, publish, and track posts for one social network with a searchable content calendar. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Support drafts, scheduled posts, queues, campaigns, tags, reusable snippets, and a weekly calendar. Connect exactly one social platform using its documented OAuth flow. Validate character, media, aspect-ratio, and file-size limits before scheduling. Publish through idempotent background jobs with retries and clear failure states. Store platform post identifiers and refresh publication status through the official API. Maintain a reusable media library with local storage. Support CSV export and token reconnect. Include clear empty, loading, success, and recoverable error states. Add robust validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for scheduling logic and one end-to-end publishing flow. Create a README covering setup, architecture, permissions, data storage, and backup. Do not add billing, telemetry, hosted infrastructure, enterprise collaboration, social inbox, listening, analytics dashboards, white-labeling, or unofficial scraping. Finish by running the tests and listing the exact commands used. ## Required capabilities - developer application for one social platform - OAuth credentials - MySQL - Redis - background worker - job queue - cloud object storage ## 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 RADAAR. 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 ===== # RADAAR indie build ## Goal Build the smallest trustworthy replacement for the core RADAAR workflow for one developer or a tiny team. ## Scope Schedule posts for one social platform, publish through the official API, manage a simple content calendar, and maintain reusable media assets. ## 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: - multi-network publishing - social inbox and engagement - social listening and keyword monitoring - advanced analytics and reporting - approval workflows - team collaboration - workspace management - media library - URL shortener and tracking - AI-assisted content workflows - API ecosystem - reliable hosted infrastructure If those capabilities are essential, use Postiz 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 personal replacement for RADAAR in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and exactly one official social-platform API; do not offer alternative stacks. The core loop is: create, schedule, preview, publish, and track posts for one social network with a searchable content calendar. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Support drafts, scheduled posts, queues, campaigns, tags, reusable snippets, and a weekly calendar. Connect exactly one social platform using its documented OAuth flow. Validate character, media, aspect-ratio, and file-size limits before scheduling. Publish through idempotent background jobs with retries and clear failure states. Store platform post identifiers and refresh publication status through the official API. Maintain a reusable media library with local storage. Support CSV export and token reconnect. Include clear empty, loading, success, and recoverable error states. Add robust validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for scheduling logic and one end-to-end publishing flow. Create a README covering setup, architecture, permissions, data storage, and backup. Do not add billing, telemetry, hosted infrastructure, enterprise collaboration, social inbox, listening, analytics dashboards, white-labeling, or unofficial scraping. Finish by running the tests and listing the exact commands used. ## Required capabilities - developer application for one social platform - OAuth credentials - MySQL - Redis - background worker - job queue - cloud object storage ## 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 RADAAR. 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 ===== # RADAAR product brief ## Problem A basic scheduler can be recreated, but RADAAR's complete product · publishing, engagement, monitoring, analytics, team collaboration, asset management, approval workflows, and multi-network integrations · is not realistically replaceable in a weekend. ## Product outcome Schedule posts for one social platform, publish through the official API, manage a simple content calendar, and maintain reusable media assets. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - developer application for one social platform - OAuth credentials - MySQL - Redis - background worker - job queue - cloud object storage ## Explicit non-goals for v1 - multi-network publishing - social inbox and engagement - social listening and keyword monitoring - advanced analytics and reporting - approval workflows - team collaboration - workspace management - media library - URL shortener and tracking - AI-assisted content workflows - API ecosystem - reliable hosted infrastructure ## 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 personal replacement for RADAAR in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and exactly one official social-platform API; do not offer alternative stacks. The core loop is: create, schedule, preview, publish, and track posts for one social network with a searchable content calendar. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Support drafts, scheduled posts, queues, campaigns, tags, reusable snippets, and a weekly calendar. Connect exactly one social platform using its documented OAuth flow. Validate character, media, aspect-ratio, and file-size limits before scheduling. Publish through idempotent background jobs with retries and clear failure states. Store platform post identifiers and refresh publication status through the official API. Maintain a reusable media library with local storage. Support CSV export and token reconnect. Include clear empty, loading, success, and recoverable error states. Add robust validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for scheduling logic and one end-to-end publishing flow. Create a README covering setup, architecture, permissions, data storage, and backup. Do not add billing, telemetry, hosted infrastructure, enterprise collaboration, social inbox, listening, analytics dashboards, white-labeling, or unofficial scraping. Finish by running the tests and listing the exact commands used. ## 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 RADAAR capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# RADAAR indie build ## Goal Build the smallest trustworthy replacement for the core RADAAR workflow for one developer or a tiny team. ## Scope Schedule posts for one social platform, publish through the official API, manage a simple content calendar, and maintain reusable media assets. ## 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: - multi-network publishing - social inbox and engagement - social listening and keyword monitoring - advanced analytics and reporting - approval workflows - team collaboration - workspace management - media library - URL shortener and tracking - AI-assisted content workflows - API ecosystem - reliable hosted infrastructure If those capabilities are essential, use Postiz 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 personal replacement for RADAAR in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and exactly one official social-platform API; do not offer alternative stacks. The core loop is: create, schedule, preview, publish, and track posts for one social network with a searchable content calendar. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Support drafts, scheduled posts, queues, campaigns, tags, reusable snippets, and a weekly calendar. Connect exactly one social platform using its documented OAuth flow. Validate character, media, aspect-ratio, and file-size limits before scheduling. Publish through idempotent background jobs with retries and clear failure states. Store platform post identifiers and refresh publication status through the official API. Maintain a reusable media library with local storage. Support CSV export and token reconnect. Include clear empty, loading, success, and recoverable error states. Add robust validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for scheduling logic and one end-to-end publishing flow. Create a README covering setup, architecture, permissions, data storage, and backup. Do not add billing, telemetry, hosted infrastructure, enterprise collaboration, social inbox, listening, analytics dashboards, white-labeling, or unofficial scraping. Finish by running the tests and listing the exact commands used. ## Required capabilities - developer application for one social platform - OAuth credentials - MySQL - Redis - background worker - job queue - cloud object storage ## 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
# RADAAR product brief ## Problem A basic scheduler can be recreated, but RADAAR's complete product · publishing, engagement, monitoring, analytics, team collaboration, asset management, approval workflows, and multi-network integrations · is not realistically replaceable in a weekend. ## Product outcome Schedule posts for one social platform, publish through the official API, manage a simple content calendar, and maintain reusable media assets. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - developer application for one social platform - OAuth credentials - MySQL - Redis - background worker - job queue - cloud object storage ## Explicit non-goals for v1 - multi-network publishing - social inbox and engagement - social listening and keyword monitoring - advanced analytics and reporting - approval workflows - team collaboration - workspace management - media library - URL shortener and tracking - AI-assisted content workflows - API ecosystem - reliable hosted infrastructure ## 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 personal replacement for RADAAR in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and exactly one official social-platform API; do not offer alternative stacks. The core loop is: create, schedule, preview, publish, and track posts for one social network with a searchable content calendar. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Support drafts, scheduled posts, queues, campaigns, tags, reusable snippets, and a weekly calendar. Connect exactly one social platform using its documented OAuth flow. Validate character, media, aspect-ratio, and file-size limits before scheduling. Publish through idempotent background jobs with retries and clear failure states. Store platform post identifiers and refresh publication status through the official API. Maintain a reusable media library with local storage. Support CSV export and token reconnect. Include clear empty, loading, success, and recoverable error states. Add robust validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for scheduling logic and one end-to-end publishing flow. Create a README covering setup, architecture, permissions, data storage, and backup. Do not add billing, telemetry, hosted infrastructure, enterprise collaboration, social inbox, listening, analytics dashboards, white-labeling, or unofficial scraping. Finish by running the tests and listing the exact commands used. ## 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 RADAAR 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
People pay for RADAAR because operating a reliable social media management platform is significantly harder than building a scheduler. The subscription funds continuous API maintenance, publishing reliability, collaboration features, analytics infrastructure, monitoring, and support across multiple social networks.
xmulti-network publishing
xsocial inbox and engagement
xsocial listening and keyword monitoring
xadvanced analytics and reporting
xapproval workflows
xteam collaboration
xworkspace management
xmedia library
xURL shortener and tracking
xAI-assisted content workflows
xAPI ecosystem
xreliable hosted infrastructure
share on X ↗"I just replaced RADAAR ($9.99/mo) with one prompt"
RADAAR pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| basic | $4.99 | $3.49 | 3 social profiles, 1 user, 90 posts, 12 passwords, 3 caption templates |
| standard | $9.99 | $6.99 | 6 social profiles, 3 users, unlimited posts, 3 recurring posts, 6 RSS feeds |
| professional | $29.99 | $20.99 | 12 social profiles, 6 users, unlimited posts, 3 monitoring queries, 6 recurring posts |
| advanced | $149.99 | $104.99 | 24 social profiles, unlimited users/posts, 9 monitoring queries, 12 recurring posts |
| enterprise | $749.99 | $524.99 | Custom integrations, security, support and scalable limits |
free tierno free tier
billingmonthly + annual (-30%); 14-day free trial, no credit card
hidden costsSeparate subscriptions may be needed to keep brands isolated; enterprise starts at $749.99/month; nonprofit discount is 50% for qualified organizations.
verified 2026-08-14 · source ↗
Vibecode RADAAR
Not really. RADAAR's value is not the code: A DIY replacement assumes only a single-network scheduler rather than the full product. See the honest breakdown above.
How much does RADAAR cost?
RADAAR costs about $9.99/month (Standard, checked 2026-08-04), which is $119.88 per year.
What do I lose by replacing RADAAR?
Honestly: multi-network publishing; social inbox and engagement; social listening and keyword monitoring; advanced analytics and reporting; approval workflows; team collaboration; workspace management; media library; URL shortener and tracking; AI-assisted content workflows; API ecosystem; reliable hosted infrastructure. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to RADAAR?
Yes: Postiz (Open-source social media scheduling platform.), Mixpost (Self-hosted social media management platform.). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.