# Build brief — a focused alternative to Replit

> **Verdict:** Partly, if you narrow it · **Buildability:** 58/100 · **Category:** Dev Tools
> **Source:** https://www.canitbevibecoded.com/replit
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Replit. Verify current pricing and capabilities before acting.

## Context

**Replit** — Browser IDE with agents, instant apps, hosting, and deployment. It currently costs $25/mo.

A dev container plus code-server plus deployment can replace some value, but Replit's beginner-friendly cloud IDE, agents, secrets, hosting, and zero-setup environment are a platform.

This brief describes a focused, single-operator replacement for the part of Replit that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Run code-server in a cloud VM, add templates, secrets, git, AI coding extension, and one-click deploy scripts.

- Build the focused developer workflow you use repeatedly, with local configuration.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Cloud VM/container platform.
- Code-server.
- Domain/HTTPS.
- Deploy target.
- Backups.

### Data and integrations

- LLM API.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a personal cloud dev environment to replace Replit, on a VPS I already have.
Requirements:

- code-server (VS Code in the browser) behind Caddy with HTTPS and basic auth, installed
  by one setup script. This is assembly of good parts, not a new IDE.
- A `dev new <name> --template node|python|static` CLI that copies from a templates/
  folder (each with .gitignore, README stub, and a run script) into ~/projects/<name>
  and runs git init.
- Each project gets a port in projects.json; Caddy routes <name>.dev.mydomain.com to it,
  so anything I run is instantly viewable at a URL.
- `dev deploy <name>` commits and restarts the project's systemd user service; `dev logs
  <name>` tails it.
- Per-project secrets in <project>/.env, never committed; the template .gitignore
  enforces it.
- Nightly tarball of ~/projects to a backups/ folder, keep 7.
- Reachable only over HTTPS with auth (bind to a VPN interface instead if one exists);
  no telemetry.
- Out of scope: multiplayer editing, hosted AI agents, and per-project containers. One
  VPS, one user, my own projects.
- README: the wildcard DNS record, Caddy config, and code-server auth setup.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Zero-setup browser IDE.
- Hosted agents.
- Multiplayer.
- Templates.
- Reliability at the vendor's scale is an operations problem, not a prompt.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [code-server](https://github.com/coder/code-server) — Open-source VS Code in the browser; useful base for a DIY cloud IDE

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/replit