Set Up Atlas — Car Rental Management SaaS
Get the free Atlas SaaS, let Claude set it up on your own Supabase project, and publish your working copy on Hostinger. View live demo (opens in a new tab)
Roadmap & resources
Requirements
Hostinger hosting
Atlas's code is free; hosting is a paid plan. Your live website runs here.
Choose a Hostinger Plan
Use the Unlimited plan or a Cloud plan with Web App deployment.
Claude Desktop
Your AI assistant for the setup. Claude does the technical work in its Code tab.
Download Claude Desktop
https://claude.ai/download
Node.js
Version 20.19 or newer. Claude handles the rest.
Download Node.js
https://nodejs.org/en/download
Git
Used to publish your copy of Atlas. Claude runs the Git commands for you.
Download Git
https://git-scm.com/
Supabase account
The free plan is enough to start. You'll create a new project when Claude asks for it.
Create Supabase Account
https://supabase.com/dashboard
GitHub account
Free. It holds your own private copy of Atlas, which Hostinger deploys from.
Create GitHub Account
https://github.com/signup
Get Atlas
Download Atlas
Atlas is free and open source under the MIT License.
Open Atlas on GitHub
https://github.com/salhiworks/atlas-car-rental-saas
Click Code, then Download ZIP Unzip the downloaded file Keep the atlas-car-rental-saas-main folder somewhere easy to find, such as Documents
Already use Git? You can clone the repository instead. Claude's setup works with either.
Open Atlas in Claude Desktop
Claude Desktop Code Local Select Project Folder Open Trust Workspace
Choose the Atlas folder itself — the one with README.md inside.
Set Up Supabase with Claude
Ask Claude to Set Up Atlas
In the Code tab, with the Atlas folder open, send this message:
Atlas Setup Prompt
Starts Atlas's built-in setup. Claude does the technical work for you.
Set up Atlas for me.
Claude follows Atlas's built-in setup skill. It checks your computer, installs what Atlas needs, and does the technical work itself. It stops only when it needs you, and each of those moments is a task in this guide.
Create Your Supabase Project
Claude asks for this first. Atlas always goes into a new, empty project.
Open Supabase Dashboard
https://supabase.com/dashboard
Click New project — the Free plan is fine Name it and save the database password somewhere safe When it's ready, copy its Project ID and paste it into Claude
Supabase Project Settings General
If Claude asks you to sign in to Supabase or connect your project, follow the exact instructions it gives you.
Approve the Install
Claude shows your project's name, region and creation date and asks to install Atlas into it. Check it's the project you just created, then reply yes. That one yes covers the rest:
Creates the Atlas database (54 migrations, previewed first)
Deploys and verifies Atlas's 4 Edge Functions
Configures the app with your publishable key only
Runs Atlas's automated build and checks
It takes a few minutes, and there's nothing for you to open or test. If the project isn't empty, Claude stops and changes nothing.
Prepare GitHub
Create an Empty Private Repository
This is your own copy of Atlas on GitHub. Hostinger deploys your website from it.
Create GitHub Repository
https://github.com/new
Name the repository Choose Private Leave README, .gitignore and license turned off Click Create repository Copy the repository URL
Approve the Publish
Paste the repository URL into Claude when it asks. Claude prepares Git, checks that no secrets are included, and shows a short summary: your repository and the main branch. Check the repository is yours, then reply yes.
Claude never pushes to the original Atlas repository. If Git asks you to sign in, Claude asks you to run the push yourself — sign in through the browser, because GitHub doesn't accept your account password there.
Deploy on Hostinger
Import Your Repository
No hosting yet? Get a plan in Requirements first.
Hostinger Websites Add Website Web App Import Git Repository
Connect GitHub and choose Only select repositories Select your Atlas repository and the main branch Choose the free temporary domain or your own domain
Set the Build and Deploy
Keep the Vite framework preset Hostinger detects Choose Node.js 22, or the newest version offered Set the build command to npm run build Set the output directory to dist
Add exactly these two environment variables. Claude shows you both values, and you can ignore any other suggestions:
VITE_SUPABASE_URL VITE_SUPABASE_PUBLISHABLE_KEY
VITE_SUPABASE_URL
Project URL
VITE_SUPABASE_PUBLISHABLE_KEY
Publishable key
Get these values from Supabase
Open Connect
https://supabase.com/dashboard/project/_?showConnect=true
Security
Only the Publishable key goes here. Never add a Secret or service_role key to a VITE_ variable — anything starting with VITE_ is visible in the browser.
Click Deploy and wait for the build to finish Copy your website's address and paste it into Claude
Claude checks that the live website loads over HTTPS and is connected to your Supabase project.
Go Live & Create Your Agency
Add Your Live Address to Supabase
Sign-up and password emails link to these addresses. Claude sends the exact Site URL and four Redirect URLs for your Hostinger domain — copy them from Claude's message.
Supabase Authentication URL Configuration
Set the Site URL to your live address, starting with https:// Add the four Redirect URLs, one at a time Click Save, then tell Claude it's done
Each Redirect URL is your live address followed by one of these paths:
/auth/callback
/accept-invite
/auth/reset-password
/confirm-email
Create Your Agency
Open the sign-up link Claude gives you — your live address followed by /sign-up Create your agency with the same email as your Supabase account Open the confirmation email in the same browser Sign in, then tell Claude when the dashboard shows your agency
Why the same email: Supabase's built-in email only reaches your Supabase team's addresses, about two messages an hour. Claude then confirms your agency exists with you as its Owner — there's nothing for you to test.
Atlas is live. Every push to the main branch now redeploys it on Hostinger, so ask Claude for any change, including your own name, logo or colors, then ask it to push.
Before real customers
Connect your own email provider (Custom SMTP) before customers or staff outside your Supabase team sign up:
Supabase Authentication Emails SMTP Settings