Post a trip or a shipment
Travelers publish routes and capacity. Senders create shipment requests with weight, value, route, date, notes, and package photos.
Route-based delivery with safer handoffs
Send packages with travelers already heading your way.
Peke helps senders and travelers meet around real trips, not random delivery routes. Post a shipment, offer available luggage space, chat inside the app, and confirm every handoff with a verification flow built for trust.
2 roles
Use Peke as a sender, a traveler, or both from one profile.
Safer flow
Verification code and email-confirmation steps keep onboarding cleaner.
Route-first
Trips, shipment requests, and matching all center around actual routes.
How it works
Built around real trips, clear shipment details, and handoff confirmation.
Peke is strongest when both sides know exactly what is moving, where it is going, and who is carrying it. The app flow is designed around that.
Match by route, not guesswork
Cairo to Dubai means Cairo to Dubai. Peke keeps the experience focused on real departure and destination pairs, not noisy browsing.
Confirm with verification steps
Account setup, shipment matching, and handoff flows all lean on verification so the app can reduce confusion at the moments that matter most.
Trust layer
Peke gives both sides more context before anything moves.
The app already leans into identity, travel preferences, KYC documents, restrictions, route data, and in-app chat. The landing page should reflect that same level of clarity.
Traveler identity and KYC setup
Profiles support document uploads and selfie verification so higher-trust delivery matches are possible as the platform grows.
Shipment photos, weight, and declared value
Senders can show what is being moved, how heavy it is, and how valuable it is before a traveler agrees to carry it.
Restrictions and safety checkpoints
The app already asks about restricted items and traveler preferences, which makes acceptance decisions much more grounded.
What a safer onboarding flow should feel like
01
Create account
Email + password + basic profile metadata.
02
Confirm email
Verification link opens the landing page, then deep-links into Peke.
03
Finish in the app
The verified session is handed back into the mobile app cleanly.
Waiting for verification
Email confirmation opens here first, then moves into the app.
When Supabase redirects back after confirming an email, this page detects the returned
session, prepares a deep link to peke://auth/callback, and hands the user
back into the app.
If the app does not open automatically, use the button above. If you are still on the
signup screen in Peke, you can also confirm manually with the 6-digit code from your email.
FAQ
Short answers for the moments users get stuck.
The page is especially important during signup, so the most useful copy here is the copy that reduces confusion and gets people back into the app fast.
Why open the website during verification?
Supabase confirms the email first, then redirects to a safe web URL. From there we can open the installed Peke app with the verified session details.
What if the app does not open?
Tap the Open Peke button on this page. If you are already inside the signup flow, the 6-digit code from the email still works as a manual fallback.
Do I need both the email link and OTP code?
No. Either one can get the account confirmed. The deep-link flow is there to make the email-link path feel just as smooth as entering the code manually.