Vibecode Later
track this build5 steps, step by step0%KINDA · weekend project
A post calendar and queue are buildable, but Later's value is social API access, visual planning, link-in-bio, analytics, media library, and platform compliance.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Later. 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 ===== # Later indie build ## Goal Build the smallest trustworthy replacement for the core Later workflow for one developer or a tiny team. ## Scope Build a content calendar, schedule posts through social APIs, store media, and track publish status. ## 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: - visual planner - social API maintenance - link-in-bio - analytics - media library - approvals - mobile app 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 me a personal social post scheduler to replace Later. Requirements: - Node + Express + better-sqlite3 on localhost:4870. Posts table: text, media paths, platform, scheduled time, status (queued/posted/failed). - A month-grid calendar page plus a queue list; compose form with image preview and a per-platform character counter. Media files live in a media/ folder. - node-cron checks the queue every minute and publishes via official APIs where they are sane: Bluesky and Mastodon first (tokens in .env). Add X only if my API tier allows posting, check before building it. - For Instagram, do not fight the API: at post time send me an ntfy.sh push with the caption and image path so I can post by hand in twenty seconds. - Failed posts retry twice, then flag red on the calendar with the API error saved. - Published posts store the live URL so the calendar links to the real post. - Single user, binds to localhost only, no accounts, no telemetry. - Out of scope: analytics, link-in-bio pages, and approval workflows. - README: per-platform token setup, plus an honest note that social APIs drift and this needs occasional patching, that upkeep is what Later was charging for. ## Required capabilities - OAuth/API access - hosted scheduler - media storage - database - retry and logging ## 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 Later. 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 ===== # Later indie build ## Goal Build the smallest trustworthy replacement for the core Later workflow for one developer or a tiny team. ## Scope Build a content calendar, schedule posts through social APIs, store media, and track publish status. ## 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: - visual planner - social API maintenance - link-in-bio - analytics - media library - approvals - mobile app 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 me a personal social post scheduler to replace Later. Requirements: - Node + Express + better-sqlite3 on localhost:4870. Posts table: text, media paths, platform, scheduled time, status (queued/posted/failed). - A month-grid calendar page plus a queue list; compose form with image preview and a per-platform character counter. Media files live in a media/ folder. - node-cron checks the queue every minute and publishes via official APIs where they are sane: Bluesky and Mastodon first (tokens in .env). Add X only if my API tier allows posting, check before building it. - For Instagram, do not fight the API: at post time send me an ntfy.sh push with the caption and image path so I can post by hand in twenty seconds. - Failed posts retry twice, then flag red on the calendar with the API error saved. - Published posts store the live URL so the calendar links to the real post. - Single user, binds to localhost only, no accounts, no telemetry. - Out of scope: analytics, link-in-bio pages, and approval workflows. - README: per-platform token setup, plus an honest note that social APIs drift and this needs occasional patching, that upkeep is what Later was charging for. ## Required capabilities - OAuth/API access - hosted scheduler - media storage - database - retry and logging ## 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 Later. 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 ===== # Later product brief ## Problem A post calendar and queue are buildable, but Later's value is social API access, visual planning, link-in-bio, analytics, media library, and platform compliance. ## Product outcome Build a content calendar, schedule posts through social APIs, store media, and track publish status. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - OAuth/API access - hosted scheduler - media storage - database - retry and logging ## Explicit non-goals for v1 - visual planner - social API maintenance - link-in-bio - analytics - media library - approvals - mobile app ## 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 personal social post scheduler to replace Later. Requirements: - Node + Express + better-sqlite3 on localhost:4870. Posts table: text, media paths, platform, scheduled time, status (queued/posted/failed). - A month-grid calendar page plus a queue list; compose form with image preview and a per-platform character counter. Media files live in a media/ folder. - node-cron checks the queue every minute and publishes via official APIs where they are sane: Bluesky and Mastodon first (tokens in .env). Add X only if my API tier allows posting, check before building it. - For Instagram, do not fight the API: at post time send me an ntfy.sh push with the caption and image path so I can post by hand in twenty seconds. - Failed posts retry twice, then flag red on the calendar with the API error saved. - Published posts store the live URL so the calendar links to the real post. - Single user, binds to localhost only, no accounts, no telemetry. - Out of scope: analytics, link-in-bio pages, and approval workflows. - README: per-platform token setup, plus an honest note that social APIs drift and this needs occasional patching, that upkeep is what Later was charging for. ## 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 Later capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Later indie build ## Goal Build the smallest trustworthy replacement for the core Later workflow for one developer or a tiny team. ## Scope Build a content calendar, schedule posts through social APIs, store media, and track publish status. ## 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: - visual planner - social API maintenance - link-in-bio - analytics - media library - approvals - mobile app 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 me a personal social post scheduler to replace Later. Requirements: - Node + Express + better-sqlite3 on localhost:4870. Posts table: text, media paths, platform, scheduled time, status (queued/posted/failed). - A month-grid calendar page plus a queue list; compose form with image preview and a per-platform character counter. Media files live in a media/ folder. - node-cron checks the queue every minute and publishes via official APIs where they are sane: Bluesky and Mastodon first (tokens in .env). Add X only if my API tier allows posting, check before building it. - For Instagram, do not fight the API: at post time send me an ntfy.sh push with the caption and image path so I can post by hand in twenty seconds. - Failed posts retry twice, then flag red on the calendar with the API error saved. - Published posts store the live URL so the calendar links to the real post. - Single user, binds to localhost only, no accounts, no telemetry. - Out of scope: analytics, link-in-bio pages, and approval workflows. - README: per-platform token setup, plus an honest note that social APIs drift and this needs occasional patching, that upkeep is what Later was charging for. ## Required capabilities - OAuth/API access - hosted scheduler - media storage - database - retry and logging ## 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
# Later product brief ## Problem A post calendar and queue are buildable, but Later's value is social API access, visual planning, link-in-bio, analytics, media library, and platform compliance. ## Product outcome Build a content calendar, schedule posts through social APIs, store media, and track publish status. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - OAuth/API access - hosted scheduler - media storage - database - retry and logging ## Explicit non-goals for v1 - visual planner - social API maintenance - link-in-bio - analytics - media library - approvals - mobile app ## 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 personal social post scheduler to replace Later. Requirements: - Node + Express + better-sqlite3 on localhost:4870. Posts table: text, media paths, platform, scheduled time, status (queued/posted/failed). - A month-grid calendar page plus a queue list; compose form with image preview and a per-platform character counter. Media files live in a media/ folder. - node-cron checks the queue every minute and publishes via official APIs where they are sane: Bluesky and Mastodon first (tokens in .env). Add X only if my API tier allows posting, check before building it. - For Instagram, do not fight the API: at post time send me an ntfy.sh push with the caption and image path so I can post by hand in twenty seconds. - Failed posts retry twice, then flag red on the calendar with the API error saved. - Published posts store the live URL so the calendar links to the real post. - Single user, binds to localhost only, no accounts, no telemetry. - Out of scope: analytics, link-in-bio pages, and approval workflows. - README: per-platform token setup, plus an honest note that social APIs drift and this needs occasional patching, that upkeep is what Later was charging for. ## 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 Later 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 publishing workflows and API permissions are a moving target.
xvisual planner
xsocial API maintenance
xlink-in-bio
xanalytics
xmedia library
xapprovals
xmobile app
share on X ↗"I just replaced Later ($25/mo) with one prompt"
Later pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| starter | $25/workspace | $18.75/workspace | 1 social set (8 profiles); 1 user; 30 posts/profile/month; 5 AI credits/month; 3 months of analytics history. |
| growth | $50/workspace | $37.50/workspace | 2 social sets (16 profiles); 2 users; 180 posts/profile/month; 50 AI credits/month; 1 year of analytics history. |
| scale | $110/workspace | $82.50/workspace | 6 social sets (48 profiles); 4 users; unlimited posts; 100 AI credits/month; 2 years of analytics history. |
free tierno free tier (14-day trial only)
billingmonthly + annual (25% lower on annual billing); annual is billed upfront and auto-renews; tax may be added
hidden costsOn annual Growth/Scale, extra social sets cost $11.25/month equivalent, extra users $3.75/month equivalent, and 100 extra AI credits $3.75/month equivalent. Starter cannot buy these add-ons and must upgrade.
verified 2026-08-14 · source ↗
Vibecode Later
Kinda. The core of Later is buildable in a weekend with the prompt on this page, but there are real gaps: visual planner, social API maintenance. Read the honest list above before committing.
How much does Later cost?
Later costs about $25/month (Starter, checked 2026-07-30), which is $300 per year.
What do I lose by replacing Later?
Honestly: visual planner; social API maintenance; link-in-bio; analytics; media library; approvals; mobile app. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Later?
Yes: Postiz (Open-source social media scheduler that can cover much of the DIY core.). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.