Vibecode PlanetScale
track this build5 steps, step by step0%NOT REALLY · don't bother
price variesbuild time closest consolation build: one sittingcategory ☁️ hostingreplaced by 0 people
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For PlanetScale, operate a small MySQL-compatible database with migrations and backups on one server. The hard boundary is vitess operations, branching, nonblocking schema workflow, scale, and support, plus infrastructure scale, operations, and reliability.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of PlanetScale. 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 ===== # PlanetScale indie build ## Goal Build the smallest trustworthy replacement for the core PlanetScale workflow for one developer or a tiny team. ## Scope Operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. ## 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: - Vitess operations, branching, nonblocking schema workflow, scale, and support - global edge network - managed databases - autoscaling - DDoS protection, support, and compliance If those capabilities are essential, use Coolify 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 closest honest personal substitute for PlanetScale in an empty repository. Use Docker Compose, Caddy, PostgreSQL, Redis, and a small Go control plane; do not offer alternative stacks. The core loop is: operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. 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. Accept a Git repository or container image and one explicit Dockerfile-based build path. Implement applications, environments, secrets, domains, health checks, and rolling container replacement. Use Caddy for automatic TLS and route only to healthy local containers. Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions. Back up PostgreSQL metadata and document backups for each deployed application's data volumes. Add host metrics, disk alerts, update instructions, disaster recovery, and a prominent single-server warning. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out multi-region or serverless infrastructure. Deliberately leave out managed data stores and global edge delivery. Deliberately leave out DDoS response, compliance, and guaranteed uptime. Finish by running the tests and listing the exact commands used. ## Required capabilities - Linux server - Docker - domain and DNS access - backup destination - basic systems administration ## 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 PlanetScale. 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 ===== # PlanetScale indie build ## Goal Build the smallest trustworthy replacement for the core PlanetScale workflow for one developer or a tiny team. ## Scope Operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. ## 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: - Vitess operations, branching, nonblocking schema workflow, scale, and support - global edge network - managed databases - autoscaling - DDoS protection, support, and compliance If those capabilities are essential, use Coolify 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 closest honest personal substitute for PlanetScale in an empty repository. Use Docker Compose, Caddy, PostgreSQL, Redis, and a small Go control plane; do not offer alternative stacks. The core loop is: operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. 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. Accept a Git repository or container image and one explicit Dockerfile-based build path. Implement applications, environments, secrets, domains, health checks, and rolling container replacement. Use Caddy for automatic TLS and route only to healthy local containers. Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions. Back up PostgreSQL metadata and document backups for each deployed application's data volumes. Add host metrics, disk alerts, update instructions, disaster recovery, and a prominent single-server warning. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out multi-region or serverless infrastructure. Deliberately leave out managed data stores and global edge delivery. Deliberately leave out DDoS response, compliance, and guaranteed uptime. Finish by running the tests and listing the exact commands used. ## Required capabilities - Linux server - Docker - domain and DNS access - backup destination - basic systems administration ## 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 PlanetScale. 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 ===== # PlanetScale product brief ## Problem A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For PlanetScale, operate a small MySQL-compatible database with migrations and backups on one server. The hard boundary is vitess operations, branching, nonblocking schema workflow, scale, and support, plus infrastructure scale, operations, and reliability. ## Product outcome Operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Linux server - Docker - domain and DNS access - backup destination - basic systems administration ## Explicit non-goals for v1 - Vitess operations, branching, nonblocking schema workflow, scale, and support - global edge network - managed databases - autoscaling - DDoS protection, support, and compliance ## 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 closest honest personal substitute for PlanetScale in an empty repository. Use Docker Compose, Caddy, PostgreSQL, Redis, and a small Go control plane; do not offer alternative stacks. The core loop is: operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. 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. Accept a Git repository or container image and one explicit Dockerfile-based build path. Implement applications, environments, secrets, domains, health checks, and rolling container replacement. Use Caddy for automatic TLS and route only to healthy local containers. Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions. Back up PostgreSQL metadata and document backups for each deployed application's data volumes. Add host metrics, disk alerts, update instructions, disaster recovery, and a prominent single-server warning. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out multi-region or serverless infrastructure. Deliberately leave out managed data stores and global edge delivery. Deliberately leave out DDoS response, compliance, and guaranteed uptime. 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 PlanetScale capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# PlanetScale indie build ## Goal Build the smallest trustworthy replacement for the core PlanetScale workflow for one developer or a tiny team. ## Scope Operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. ## 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: - Vitess operations, branching, nonblocking schema workflow, scale, and support - global edge network - managed databases - autoscaling - DDoS protection, support, and compliance If those capabilities are essential, use Coolify 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 closest honest personal substitute for PlanetScale in an empty repository. Use Docker Compose, Caddy, PostgreSQL, Redis, and a small Go control plane; do not offer alternative stacks. The core loop is: operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. 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. Accept a Git repository or container image and one explicit Dockerfile-based build path. Implement applications, environments, secrets, domains, health checks, and rolling container replacement. Use Caddy for automatic TLS and route only to healthy local containers. Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions. Back up PostgreSQL metadata and document backups for each deployed application's data volumes. Add host metrics, disk alerts, update instructions, disaster recovery, and a prominent single-server warning. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out multi-region or serverless infrastructure. Deliberately leave out managed data stores and global edge delivery. Deliberately leave out DDoS response, compliance, and guaranteed uptime. Finish by running the tests and listing the exact commands used. ## Required capabilities - Linux server - Docker - domain and DNS access - backup destination - basic systems administration ## 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
# PlanetScale product brief ## Problem A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For PlanetScale, operate a small MySQL-compatible database with migrations and backups on one server. The hard boundary is vitess operations, branching, nonblocking schema workflow, scale, and support, plus infrastructure scale, operations, and reliability. ## Product outcome Operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Linux server - Docker - domain and DNS access - backup destination - basic systems administration ## Explicit non-goals for v1 - Vitess operations, branching, nonblocking schema workflow, scale, and support - global edge network - managed databases - autoscaling - DDoS protection, support, and compliance ## 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 closest honest personal substitute for PlanetScale in an empty repository. Use Docker Compose, Caddy, PostgreSQL, Redis, and a small Go control plane; do not offer alternative stacks. The core loop is: operate a small MySQL-compatible database on one user-owned server, run schema migrations, retain logs, and perform regular backups. 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. Accept a Git repository or container image and one explicit Dockerfile-based build path. Implement applications, environments, secrets, domains, health checks, and rolling container replacement. Use Caddy for automatic TLS and route only to healthy local containers. Capture bounded build and runtime logs and expose restart, rollback, and redeploy actions. Back up PostgreSQL metadata and document backups for each deployed application's data volumes. Add host metrics, disk alerts, update instructions, disaster recovery, and a prominent single-server warning. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out multi-region or serverless infrastructure. Deliberately leave out managed data stores and global edge delivery. Deliberately leave out DDoS response, compliance, and guaranteed uptime. 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 PlanetScale 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 still pay for PlanetScale because hosting products sell an operations team and failure-domain diversity, not merely a deploy button. The recurring cost buys patching, certificates, isolation, secrets, builds, deploys, logs, metrics, backups, capacity, incidents, and security response, not just the visible interface.
xVitess operations, branching, nonblocking schema workflow, scale, and support
xglobal edge network
xmanaged databases
xautoscaling
xDDoS protection, support, and compliance
share on X ↗"I just replaced PlanetScale with one prompt"
Don't feel like building it? These folks already made it free.
CoolifyA MySQL container with TLS, monitoring, scheduled backups, and restore controls on one server; branching is gone with PlanetScale.open source↗
DokployRun MySQL on your own host with managed deployment and backups; schema branching is the thing you give up.open source↗no votes, no pay-to-list · just what's real
PlanetScale pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| base - single-node postgres | $5/workspace | — | Starts at $5/month; single-node Postgres; 10 GB included egress. |
| base - high-availability postgres | $15/workspace | — | Starts at $15/month for a 3-node HA configuration; 100 GB included egress. |
| metal | $50/workspace | — | Starts at $50/month for dedicated-metal database compute. |
| vitess | custom | — | Resource-based MySQL/Vitess pricing; exact public starting total is not exposed as one fixed plan price. |
| enterprise | custom | — | Custom resources, security, support and contract terms. |
free tierno free tier
billingmonthly pay as you go for Base and Metal; Enterprise custom; no public annual self-serve plan
hidden costsEgress above the included amount is $0.06/GB; extra production branches duplicate the selected cluster cost. Development branches include 2x the month's hours and then cost about $0.014/hour; HA storage can effectively cost $1.50/GB because it is replicated across 3 nodes. SSO and support can be add-ons.
price historyMetal minimum monthly price: $589 → $50 (2025-12)
verified 2026-08-14 · source ↗
Vibecode PlanetScale
Not really. PlanetScale's value is not the code: Recheck price before merge. See the honest breakdown above.
How much does PlanetScale cost?
PlanetScale's pricing is usage-based or varies by plan · Typical entry paid database package; usage terms apply..
What do I lose by replacing PlanetScale?
Honestly: Vitess operations, branching, nonblocking schema workflow, scale, and support; global edge network; managed databases; autoscaling; DDoS protection, support, and compliance. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to PlanetScale?
Yes: Coolify (A MySQL container with TLS, monitoring, scheduled backups, and restore controls on one server; branching is gone with PlanetScale.) Dokploy (Run MySQL on your own host with managed deployment and backups; schema branching is the thing you give up.) The prompt is for when you want it exactly your way.