SLW / devportal Production apps
New here? Read this first

Start here

You don't need to be a programmer. You get one personal workspace in the cloud with every app inside, an AI does the building, and simple guardrails keep anything from going wrong. One command to set up, then you’re building.

What this is

The one idea to get first

Two copies of every app — and a gate between them

Every app exists twice: the live app real people use, and a safe copy you and Claude build on. Your work always starts on the safe copy and only reaches the live app through one reviewed gate — so nothing you do can break the real thing by accident.

Dev · where you work

The safe copy

You + Claude, in your cloud workspace

  • ◆
    Practice data — fake records, never real customer data.
  • ◆
    Your own private copy — you can't clash with a teammate.
  • ◆
    Experiment freely. Break it, undo it, try again.

Nothing here is visible to real users.

🔒
reviewed
gate
Production · the live app

The real thing

Real people, real data, every day

  • ●
    Real data the team depends on.
  • ●
    What teammates open at apps.rivent.dev.
  • ●
    Changes only arrive here after preview + approval.

You never build directly on the live app.

How a change gets proposed and approved

One direction only: Dev → preview → approve → Production. You drive it in plain English; the portal handles the machinery.

1DevYou describe it, Claude builds it on the safe copy. Try it, tweak it until it's right.
2DevIt becomes a proposed change with its own live preview link on the app's Review & publish tab — try the real thing on safe data.
3The gateApprove it. Most changes: you tick it and publish once the automatic checks are green. Risky ones wait for Shawn — Claude tells you which kind yours is.
4ProductionIt goes live. The change crosses into the real app and teammates see it.

What you ship yourself vs. what waits for Shawn

The gate is light for everyday work and firm only where a mistake could hit real data.

✅ You ship it yourself

Publish once the automatic checks pass

  • ✓
    New buttons, screens, and layout changes
  • ✓
    Copy, styling, and behavior tweaks
  • ✓
    Adding a data source or a dev key

🔒 Waits for Shawn

Code-owner review before it can go live

  • ◆
    Database changes — a new field, list, or record type
  • ◆
    Production / deploy config
  • ◆
    Anything touching real data or money — ask first

1 · Set up your computer — one command, once

You do this once, ever. It connects this computer to your personal SLW Workspace — one private cloud environment with every app you have access to already inside.

Once per computer · ~10 min
1

Paste one command

Windows: press the Windows key, type powershell, Enter, then paste:

> irm rivent.dev/setup | iex

Mac: open the Terminal app, then paste:

$ curl -fsSL rivent.dev/setup | bash

It installs the GitHub tool, signs you in (your browser opens — click Authorize, possibly twice), builds your workspace, and ends with an ALL SET box showing your personal connection values. Safe to re-run any time — it repairs whatever is missing.

2

Install Claude Desktop & sign in

Download the Claude desktop app and sign in with your own Claude plan. This is your interface for everything.

3

Connect Claude Desktop to your workspace

Open Claude Desktop → Code → New → click the environment pill above the message box → Add SSH connection → copy in the four values from your ALL SET box (Name, SSH Host, Port empty, Identity file — use the full path it printed).

🧭

Prefer being walked through it? The guided version shows what you should see at every step and has a live assistant if anything looks different.

2 · Every day after

Every time
✓

Open Claude Desktop & say which app you're working on

Make sure the environment pill shows your workspace, then just say it — “work on Terminal”. Every app you have access to is already inside, kept up to date automatically. No terminal, no commands, no per-project setup. It builds on the safe copy; when it's ready, it shows up to review and publish.

💡

Anything acting up — even months from now? Re-run the one command from step 1. It fixes almost everything. Still stuck? Ask the assistant on the setup page.

Remember

Go deeper when you're ready