Iceland: get the company and money rails right — then the car node is the easy part.
For US operators, Iceland is often a setup + compliance story first:
entity (ehf.), digital ID, bank AML, VAT, and how money moves.
The mobility product still uses the same four tools: Cloudflare · Stripe · Google · screening.
Order of work (do not skip)
1
Legal houseCompany form, board/residency rules, kennitala / system ID path — with local professionals
2
Money pathBank or EMI + how Stripe (or local processor) takes cards without becoming an unlicensed payment institution by accident
3
Data & securityGDPR / NIS2 posture for any guest or driver data you store
4
Then the nodeSite, fleet list, Calendar blocks, driver screens, Owner approves keys
🏢
Owner / advisor
Runs install package (illustrative ~11% of eligible volume under signed agreement). Teaches the stack — does not invent Icelandic licenses.
🚗
Fleet programs
Same menu as elsewhere: rent, employee access, driver lease, airport ride+park — only if insurance and transport rules allow.
🧰
Stack
Google Workspace as daily ops. Cloudflare for the public edge. Stripe for cards when banking allows. AI explains process, never signs coverage.
What “self-managed through Google” means
Drive folders per car (photos, registration copies — not SSNs in chat)
Calendar = human-readable booking block
One Google sign-in (OAuth) so staff are not pasting API keys into email
Informational only. Iceland banking, company, tax, and payment rules require local counsel and the bank.
Fee percentages are discussion drafts until written. See terms.