whiskSign in

Guides

Move your Replit app to Whisk

A Replit app is usually closer to running on Whisk than you'd think. It already has a server, and it most likely already uses a Postgres database. So moving it is mostly about sign-in: your team signs in with their work email through Whisk, not with Replit accounts.

You get the code out through GitHub, and an AI coding assistant on your computer makes the changes.

What's already done

Replit apps tend to be built the way Whisk expects:

  • There's a server. The code that saves and reads data runs on the server, not in the browser. Whisk needs that, and your app already has it.
  • The database is Postgres. Whisk gives each app its own Postgres database, so your tables and data copy straight across.
  • Keys are kept out of the code. If you used Replit's Secrets, the keys are already separate. They just move from one place to another.

What changes

  • Sign-in. Replit's sign-in goes. Whisk signs people in before they reach the app, and tells the app who they are. Your team uses their work email and doesn't need a Replit account.
  • Where the keys live. You type the same keys into Whisk's secrets.
  • Scheduled tasks. Anything Replit ran on a schedule becomes a Whisk schedule. If a run fails, Whisk tries again and tells you if it still can't finish.

Doing the move

In your Replit project, open the Git pane, connect it to a GitHub repository and push your code. Then copy the repository to your computer. If you'd rather not use GitHub, download the project as a zip file instead.

If the app holds real information, export the database before you leave Replit. Ask Replit's Agent to do it, or run pg_dump in the Shell. Put the file in a folder called export in the project.

Open the project with an AI coding assistant like Claude Code, Cursor or Codex, and give it this prompt:

Read https://whisk.run/skill and follow it to move this Replit app to Whisk. Keep the app working the same. Replace Replit sign-in with Whisk's: people are signed in before they reach the app, and the app reads who they are from Whisk's headers. Use the Postgres database Whisk provides through DATABASE_URL and run the migrations. List the secrets the app needs so I can enter them in Whisk. Turn any scheduled tasks into Whisk schedules. Import the database export in the export folder. Install the whisk command line, run whisk doctor until it passes, then deploy and tell me the web address.

The AI will ask you to approve one login. Open the web address it shows, sign in to Whisk or create an account, and check the code matches. When it's deployed, it lists the secrets the app needs. Enter them in Whisk where it says.

Click through the app and check your data is there. Then invite your team from the app's page in Whisk.

Once it's on Whisk

You can turn off the Replit deployment, so you're not paying for both. Make changes with your AI coding assistant, and ask it to deploy when you're ready. Whisk checks every new version before it goes live, and if a database change fails, it undoes it.

What it costs

On Replit, deployments are charged by the month or by how much they're used. Whisk is a flat price per app. Your first app is free, forever, for up to three people on your team, and it sleeps when nobody's using it. Starter is $49 (US) a month for 10 apps that can stay on, with no limit on people. See pricing.