One place for every app. Apps go Experiment → Incubating → Operational. The whole framework — dev app, dev database, CI, previews, the progress board, approvals — gets built while an app is Incubating, with production built but dark. Going live just flips it on.
Everything you need to go from zero to shipping. Read how it works, do the one-time setup, connect your first project — then you're working. About 10 minutes the first time; seconds every day after.
The Codespace is your environment — a cloud computer with the app running. Claude Desktop is your interface — you connect it to that workspace and build by talking. Nothing runs on your laptop; production data never reaches you.
Open rivent.dev and sign in with your @slw.vc email. Bookmark it — it's the front door to every project.
GitHub builds a cloud workspace from the repo's .devcontainer — dependencies and dev-database wired up, identical for everyone. It runs on practice data; production is never injected. You never open the browser editor — you reach the workspace through Claude Desktop.
The native Claude app connects to that workspace over SSH. You get the Claude interface, with the real running environment behind it — one place to work.
Tell Claude what you want in plain English. It runs inside the Codespace — sees the real code, runs the app, uses the dev database.
Changes are reviewed before they go live, and the workspace persists — reconnect tomorrow right where you left off.
It installs what's needed, signs you into GitHub (your browser opens — click Authorize, maybe twice), and builds your personal SLW Workspace in the cloud with every app you have access to already inside.
Press the Windows key, type powershell, Enter, then paste:
Open the Terminal app, then paste:
Safe to re-run any time — it repairs whatever's missing.
Download the Claude desktop app and sign in with your own Claude plan (Pro or Max). This is your interface for every project.
Each work session you open a secure link, then pick the app you want.
In PowerShell, run this and leave the window open — wait for the big TUNNEL OPEN box, then minimize it:
This opens the tunnel that lets Claude Desktop reach your workspace. Closing it (or a reboot) disconnects — just run it again next session.
On Mac, Claude Desktop connects to your workspace directly — no command needed. Go straight to the next step.
Click the environment pill (bottom of the Code window) → your SLW Workspace connection. First time only: + Add SSH connection and enter these (also saved on your Desktop as Rivent-Workspace-Connection.txt):
When Select Remote Folder appears, clear the box, type /workspaces, click Go, then click into your app and Select Folder:
You'll only see the apps you have access to. To switch apps later, reopen the folder picker.
Claude runs inside the workspace — it sees the real code, can run the app on the dev database, and makes the change. Your work goes up as a reviewed change; nobody edits the live app directly.
Coming back after a restart? Your workspace, sign-in, and Claude Desktop connection all stay saved — just re-run irm rivent.dev/connect | iex (Windows) to reopen the link, then open Claude Desktop.
Each session: run connect (Windows), open Claude Desktop, pick your app under /workspaces, build.
An App Operator can take an app from idea to fully live in our stack — repo, database, hosting, portal — without being an account admin anywhere. This page is the rulebook: what the role grants, who holds it, the rules of the road, and exactly how a migration works.
Code, hosting, env vars, CI, portal listing. Unrestricted on green CI — this is most of the work.
Creating a database and copying data runs through the migration script (backup → restore → verify), so the one destructive step can’t be fumbled.
Least privilege on every platform: enough to build and run apps, never enough to touch billing or delete an organization.
| Platform | Can do | Can’t do |
|---|---|---|
| GitHubrivent-dev | ✓Create app repos, push, merge PRs, set CI & secrets on their own apps | ✕Change settings on shared repos, delete the org, billing |
| SupabaseSLW Databases | ✓Create & manage project databases, run migrations | ✕Delete the org, billing, manage members |
| Vercelslw1010 | ✓Deploy apps, manage project env vars | ✕Billing, delete the team |
| Cloudflarerivent.dev | ✓Deploy Pages, edit rivent.dev DNS | ✕Account admin, other zones |
| Replitsource apps | ✓Open, edit & export Repls | ✕Team billing & members |
| Person | Role | Status |
|---|---|---|
| Loading the roster… | ||
One command on the server grants the role — it handles GitHub + Vercel automatically and prints the three manual invites (Cloudflare, Supabase, Replit). Remove someone by taking them out of the same five places.
Seven rules cover every scenario. They keep operators fast on the safe things and careful on the few that matter.
You’re admin on any repo you create. Org rules still gate the database and production paths — those changes need review, no matter who you are.
If it’s small and tests pass, ship it. Features, migrations, and anything risky go through a pull request with green CI.
Data moves only through the migration script. It backs up first, restores, and verifies row counts — so the one irreversible step can’t go wrong quietly.
A production DB plus a -dev twin, following the house pattern. Spinning them up is your call — just be intentional: each active database ≈ $10/mo (~$20 for the pair).
Practice data only in dev and experiment databases. Real SLW data or secrets go into a dev environment only with Shawn’s OK.
Named for the app; its database matches the name. Keeps the portal, Codespaces, and databases lined up one-to-one.
Use add-app-operator to grant the role. Reverse it by removing them from the same five platforms — membership is the access.
Five stages, same every time. The one that decides the path is Stage 1 — whether the app has a real database.
Run the report prompt in the Replit Agent. It reports the stack, the secrets it needs, and — the deciding question — whether it has a Postgres database.
A new repo in rivent-dev, code pushed, Replit-specific bits stripped out.
If it has one, the script creates its Supabase project (prod + dev), copies the data across, and verifies it. Skipped entirely for apps with no database.
Deploy to Vercel or Cloudflare, load the secrets, add a devcontainer + CI, and list it on the portal.
Smoke-test the live app, then turn the Replit app off. Nothing is deleted until the new one is proven.
Where it ends up living — the same shape as every other SLW app:
The situations that actually come up — click any to expand.
-dev twin). The migration script copies your data across with a backup taken first and a row-count check after, so nothing is lost. Budget ≈ $10/mo per active database (~$20 for the pair), billed to the org.add-app-operator <github-username> <email> on the server. It adds them to GitHub + Vercel automatically and prints the three manual invites (Cloudflare, Supabase, Replit). They accept the GitHub and Vercel emails, and they’re in.Builds your workspace. Windows: PowerShell. Mac: Terminal (curl -fsSL rivent.dev/setup | bash).
Run this in PowerShell and leave the window open — wait for the TUNNEL OPEN box. (Mac skips this step.)
Claude Desktop → environment pill → your SLW Workspace connection. On Windows the values are codespace@localhost, port 2222, identity = the path the connect command printed. Then in Select Remote Folder type /workspaces → Go → pick → Select Folder.