Bring the repo you already have. Deploy wherever you already deploy.
TL;DR
Replit Agent is tuned for projects that live and deploy inside Replit's platform.
rigless works with a GitHub repo you already have and deploys wherever you already deploy.
Every rigless session is a full Linux VM with the real toolchain — not tuned to one hosting stack.
Replit still wins if you want its whole editor-plus-hosting stack in one place.
Replit Agent is built into Replit's platform — an IDE, hosting, and a deployment pipeline that work well together if you're building a new project inside Replit from scratch. That's a real strength for what it's designed for.
The tradeoff: it's Replit's world. If your project already lives in a GitHub repo, deploys to your own infrastructure, or has a CI/CD pipeline you're not replacing, you're either migrating into Replit's ecosystem or working around it.
rigless doesn't ask you to move your project anywhere. Connect a GitHub repo, work on a branch in a full Linux sandbox, and open a pull request back to that same repo. Your existing CI, deploy pipeline, and review process keep working exactly as before.
Every rigless session is a real Ubuntu VM with the full toolchain available. Install whatever your project needs, run whatever services it depends on, use the terminal directly. It's not tuned around one deploy target — it's tuned around being a real development environment for whatever you're already building.
Replit Agent runs on models Replit has selected. rigless lets you choose: OpenAI, Anthropic, Google, OpenRouter, Moonshot, Zhipu, or the bundled starter tier to get oriented.
Replit Agent | rigless | |
|---|---|---|
Repo | Built for projects native to Replit | Any existing GitHub repo |
Deploy target | Replit's hosting | Wherever you already deploy |
Environment | Replit's container | Full Ubuntu VM, real toolchain |
Model | Replit's choice | Any — BYO key or bundled starter |
Starting a project from zero and want editor, hosting, and deploy in one place.
You're already deep in Replit's ecosystem and don't need to leave it.
You have an existing repo, existing infrastructure, or a team workflow already in place.
You want a general-purpose Linux environment, not a platform-specific one.
You want to choose your model instead of using Replit's default.