Replit bundles three things: an editor and terminal in the browser, an AI agent that writes and runs apps, and hosting for what comes out. For one person, an agent can build the first part over a weekend: a container per project, Monaco, a terminal, a preview proxy and a deploy button. The agent is already something you can run in that terminal, so it isn't worth rebuilding. Hosting is where a copy becomes real work, with public TLS, databases and the risk of running code you didn't write. For most people, code-server or Coder plus Coolify for deploys is a shorter route than a new app.
Before you buildReplit's Starter plan is free, so a small experiment costs nothing; code-server on your own machine is the quickest free replacement for the editor.
Build me a personal cloud workspace to replace Replit. Requirements: - Node.js 22 + TypeScript: a Fastify server and a React front end built with Vite. `npm start` serves http://localhost:4800, bound to 127.0.0.1 unless HOST is set in .env. - Projects live in ./data/projects/<name>/ and run in one Docker container each (`dockerode`, image chosen from templates/*.json: node:22, python:3.13, or a Dockerfile in the project). The project folder is bind-mounted at /workspace; the container has CPU and memory limits from .env and no access to the host network or Docker socket. - Editor: Monaco with a file tree (create, rename, delete, upload) and tabs; saves go through the API into the mounted folder. - Terminal: xterm.js over a WebSocket to `docker exec` with a PTY inside the project's container. - Run button: runs the command in the project's workspace.json and streams logs to a panel. - Preview: a reverse proxy (`http-proxy`) maps <name>.localhost:4800 to the port declared in workspace.json, WebSockets included. - Git: init a repo per project and show a source-control panel (status, diff, commit, push). Per-project secrets are stored in ./data/secrets/<name>.env, injected as environment variables and never placed in the file tree. - Deploy: a button that builds the project's Dockerfile, starts it with a restart policy and serves it at <name>.deploy.localhost:4800. Keep the last 5 build logs. - Optional per-project Postgres container with DATABASE_URL injected as a secret. - Single user: one password in .env and a signed cookie. No accounts, no telemetry, local-first. - Out of scope: an AI agent (use a CLI agent in the terminal), collaboration, autoscaling, custom domains. - README: setup, the security model, why the web port must not be exposed without HTTPS and authentication, and how to back up ./data.
Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.
The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Replit.
Extend the cloud workspace in this folder. Requirements: - Settings page for a deploy target: SSH host, user and key path from .env. - The Deploy button builds the image locally, copies it with `docker save | ssh ... docker load`, starts it with a restart policy and updates a Caddy config on the target through its admin API. - Show the live URL and the last 5 deploy logs; a Rollback button restarts the previous image. - Refuse to deploy a project that has no healthcheck path in workspace.json. - Update the README with the target-server setup.
Add an Agent tab to the cloud workspace in this folder. Requirements: - Setting AGENT_COMMAND in .env (for example a CLI coding agent); the tab starts it in the project's container with the task text and the API key passed as an environment variable. - Stream its output, then show the git diff it produced with Accept and Revert buttons. - Commit before every run so Revert is one `git reset --hard`; limit a run to 30 minutes. - Never mount anything outside the project folder. - Update the README and explain what the agent can reach from inside the container.
Add databases to the cloud workspace in this folder. Requirements: - A Database tab that starts a postgres:17 container per project, with a generated password and a named volume, and injects DATABASE_URL into the project's secrets. - Show tables and run read-only queries from a small SQL panel; offer a download of `pg_dump -Fc` and a restore from an uploaded dump. - Stop the database container after 15 minutes without a connection and start it on demand. - Update the README with the backup advice.
Replit's draw is going from an idea to a live URL without touching a terminal or a server. Beginners and non-developers pay for the agent and one-click hosting, and many keep paying because their app already runs there.
Estimate · Free on your own computer. A VPS that can run a few containers is about $5 to $12 a month. Coding agents you run in the terminal bill by token or by their own plan. The build is token usage on your agent plan.
| Plan | Monthly | Annual, per month | What you get |
|---|---|---|---|
| Starter | $0 | $0 | Free plan. A production database is capped at 1 GiB; apps published from it can go offline when a paid plan ends. |
| Core | $20 | $18 | $20 of monthly credits toward more capable models, Plan mode, unlimited workspaces, Free Mode chat up to 30 hours and 60 projects, 100 GiB of outbound data transfer a month. |
| Pro | $100 | $90 | $100 of monthly credits, 10 parallel agents, up to 15 collaborators and 50 invited viewers, 28 days of database rollback, premium support. |
| Enterprise | custom | — | SSO and SAML, single-tenant environments, static outbound IPs, custom seat limits. |
A free Starter plan exists with limited AI use; the pricing page gives no figures for it.
Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: The built-in agent that plans, edits, runs and fixes an app on its own, One-click publishing with TLS, custom domains, autoscaling and managed databases.
About $20 a month on the Core plan, $240 a year (checked 2026-10-14).
The built-in agent that plans, edits, runs and fixes an app on its own; One-click publishing with TLS, custom domains, autoscaling and managed databases; Real-time collaboration and invited viewers; Mobile apps and the instant start of a hosted workspace; Someone else carrying the risk of untrusted code running on their servers. If any of those matter to you, keep paying.
Yes: code-server (open source), Coder (open source), OpenVSCode Server (open source).