Skip to main content
By the end, every Velocity car, availability slot, and reservation will still be there tomorrow.
Velocity after refresh showing the signed-in customer's My bookings list with two saved reservations and the fleet page with cars in the same order, both unchanged from before the refresh
You added sign-in to Velocity in Add login. But the cars in the fleet and the reservations customers make still disappear when the page refreshes — they only live in the browser. Add a database so everything persists.

Tell Agent to save the data

For Velocity, use Neon, the managed PostgreSQL provider behind Replit’s production databases. Neon handles concurrent bookings cleanly and scales with real customer traffic. For development, Replit uses Helium, its own managed PostgreSQL infrastructure. Agent sets up your app to use Replit’s separate development and production environments. There’s no Neon dashboard signup and no keys to paste. Agent will store the fleet and reservations in your development database and add an overlap check to prevent double-booking. Use the tests below to verify the result.
Agent chat after the Neon migration showing the verification checklist — overlap-prevention, signed-out blocking, user-scoped bookings, invalid date rejection, bad-car rejection — and a Checkpoint made just now indicator, alongside the Velocity preview rendering with the persisted fleet

Test that everything sticks

  1. Sign in to Velocity in Preview and reserve a car for next Saturday.
  2. Refresh the page. The reservation should still be there in “My bookings.”
  3. Restart the app from the Agent chat. The fleet and the reservation should both still be there.
  4. Try to reserve the same car on the same Saturday with a second account. Velocity should say the car isn’t available and offer a different date or car.
  5. Sign out and sign back in. Your reservation should still be there.
If a reservation disappears at any step, paste the exact symptom back to Agent: You can also ask Agent for a simple admin view to see what’s in the database:

Publish and confirm on the public URL

Replit uses separate databases for development and production. For Velocity’s initial database setup, copy your development data so the published app starts with your fleet. On current infrastructure, Replit automatically creates a production database when you publish, provided your development database contains data. Some apps expose additional database setup controls in Publishing. If those controls appear, use them to include your development data:
  1. Check your development database contains only data you want in the live app. Remove test accounts and sample reservations before copying.
  2. Open Publishing and select Adjust settings.
  3. If Database settings shows the setup options pictured below, make sure Create production database and Set up your production database with your current development data are selected.
  4. Review the settings and select Republish. Selecting the data-copy option initializes production with the data and schema from your development database.
  5. Open the public URL and confirm your fleet appears. Make a reservation, refresh, and confirm it’s still there.
Expanded Database settings in Publishing, with Create production database and Set up your production database with your current development data selected

Publishing → Adjust settings → Database settings, with both production database options selected

Copy development data only when setting up production with data that’s safe to publish. Don’t use a copy-to-production action to update an app with live bookings you need to keep: it can replace production data.
If these setup options aren’t available, your app may use automatic production database creation or already have a production database. Don’t remove an existing database to make the options appear. See Create a production database when you publish. Velocity now remembers every car, every available date, and every reservation. The next refresh won’t lose a single booking.

Improve it next

Add payments

Take a refundable deposit when a customer reserves a car.

Add integrations

Send each booking to the customer’s calendar.

Create a dashboard from data

Turn the saved reservations into utilization charts.

Need further help?

  • Reservations save in Preview but not on the public URL: ask Agent to check which database your published app uses, without showing credentials or changing data.
  • Data is hard to inspect: ask Agent to add a simple admin view that lists everything in the database.
  • You want to seed the fleet: ask Agent to add a one-time script that loads your real cars into the database.