App collaborating options - what is the best mechanism to collaborate on client apps?

Workspace
, , ,
1

I need to do the following, but it seems almost impossible. What do other do or suggest?

  • I want to work on an app for a client, including access to their secrets, and ability to deploy and manage deployment for them. The collaboration would possibly be for up to 1 month only, and then they want to take control of the app in their own Replit account

  • The client is happy to pay for their own core/teams account - payment is not the issue

  • Ideally we want the Chat tool, although I believe this may have been removed?

The options seem to be:

  1. They signup and pay for a core/team account, and give me their login details so I do everything in their account. Issue: I would see their billing details

  2. They signup and pay for a core/team account, and make me a collaborator. Issues: (1) It seems they cannot invite my Teams account as a collaborator, so I would need to setup/pay for a separate Core account; (2) as a collaborator I do not have the ability to deploy and manage deployment for them

  3. I signup and pay for a new core/team account (completely separate from my own accounts). When the app is finished I change the email to theirs. Issue: I would need to delete my billing details ready for them to add theirs, and I believe this would mean the deployment was removed during the temporary “free status” period

  4. I have a Teams account, so I could make the client part of my team by paying for them to be a member for 1 month. Issue: As far as I see, I am unable to split their team member account away from my team into their own independent Replit account once the work was done

  5. I build the app completely inside my own account. Then when the client is happy, I would have to guide them through importing the app from my Github into their own Replit account, and show them how to setup the secrets and deploy it. Issue: This doesn’t really let me provide a fully “idea → live app” solution

  6. What obvious option am I missing? What do other people do?

@FranciscoCM - any ideas? :blush:

3 Likes
2

You don’t need to use Github to do the transfer. Make the repo public, remix it from their account, then make the original private again. Takes just a minute or so and it’s all native inside Replit. This is what I have done.

3 Likes
3

Appreciate another option 5(ii) Eric :blush: But Replit-remix or Github-remix, doesn’t really make much difference. It still requires building it afresh in the clients account. Setup secrets, re-publish, etc.

And who remixes it in their account - them or me?

  • Me means logging into their account (naughty), or
  • Them means me having to guide them through (not really offering the fluid “I’ll get it fully installed for you” service).

Sorry, but I thought Replit was originally (pre-AI) a collaborative platform. It so is not.

Having said all this, I probably will go with an option 5, as the failings are the least bad.

1 Like
4

You ask too many questions, Steve. Just get to work! :rofl:

2 Likes
5

You’re not wrong though, the collaborative features are a bit discombobulated as of late. The inability to invite a teams account as a collaborator is particularly confusing and nonsensical.

Secrets is sticky because, well, they’re secret.

I think the client getting an account and giving you access is the easiest way, with what you’ve outlined above. And you don’t really see their billing info beyond their last four and their address, right? You probably won’t get much pushback there.

2 Likes
6

I know, questions, questions, questions :rofl: I’m just trying to figure out a nice workflow for all of this, so I can ramp up production. Already got something nice going with the actual app building and chatting to the agent (I haven’t forgotten I’m going to write that up when I get a moment). But the process outside of the actual vibing still feels quite clunky.

Sharing accounts: I could click through to their Replit-Stripe account and cancel their account it seems. But yeah, not much else. So might do this.

discombobulated - you win word of the week :rofl:

2 Likes
7

It’s the proper word in this case.

2 Likes
8

Hey Steve appreciate your insight on the Replit transfer workflow. I’m currently working through a real client handoff situation where I built and deployed a live site under my personal Replit account, connected a custom domain, and now need to transition operational ownership and billing cleanly to the client without downtime if possible.

Right now I’m evaluating:

  • Team/Workspace transfer path
  • GitHub/remix fallback path
  • DNS/domain continuity concerns
  • collaborator structure after transfer

The app is already live and production-facing, so I’m trying to avoid breaking the deployment or forcing unnecessary DNS reconfiguration if there’s a cleaner operational route.

If you have any practical advice or lessons learned from similar handoffs, I’d definitely appreciate it.

9

Worth noting this got a lot easier since October — Replit added proper app transfer between accounts (think it landed around Feb). So you can just hand the whole app over at the end instead of messing with shared logins or email swaps.

One thing that’s still annoying: a collaborator can’t edit Secrets unless you make them full admin. And if you do transfer, don’t delete your copy until you’ve checked it came across properly — possible lose stuff that way.

10

That is a good feature. However, I wish they would make it easier for non-organization or non-team members to make a transfer . As of right now that’s the only way to make a clean transfer inside of Replit.