Website on the main domain
`rentman.al` should explain the platform, build trust, and direct visitors to the right place quickly.
Public website for the RentMan platform
Keep `rentman.al` for the website and move each live app to its own subdomain.
This site is the public front door. Your demo, client portals, and future tenants can live separately on domains like `demo.rentman.al` or `client-name.rentman.al`.
- Public website on `rentman.al`
- Demo on `demo.rentman.al`
- Clients on their own subdomains
Why split them
The website and the app should not compete for the same job.
Demo in a safe app environment
`demo.rentman.al` can keep the full working product without forcing the public site to behave like an application shell.
Clients isolated by subdomain
Client instances or branded portals become easier to organize when each one has its own hostname and deployment boundary.
What RentMan does
A platform for booking, fleet operations, and company management.
Vehicle search and booking
Customers can discover vehicles, compare options, and move into a reservation flow.
Fleet and availability
Rental companies manage inventory, pricing, vehicle status, and operational readiness.
Reservations and billing
Teams can handle pickups, returns, invoicing, service add-ons, and customer follow-up.
Company onboarding
New companies can register, be reviewed, and then operate from their own workspace.
Suggested routing model
Use one public site and many app subdomains behind an edge proxy.
Point `rentman.al` to this website
That becomes the main branded homepage, not the app itself.
Keep each app instance on its own subdomain
`demo.rentman.al`, `client-a.rentman.al`, and future tenants stay separated.
Route by hostname at the VPS edge
A single reverse proxy can decide which container or stack should answer each hostname.
Next step
The website and application are deployed separately.
This site serves `rentman.al`, while the React app runs on demo and client subdomains.