Tenant isolation
Production tenants run with separated database configuration and Redis namespacing. Demo tenants include tenant-aware request context so data access stays scoped to the resolved tenant.
Security
Built for trust before growth.
Ride-hailing software touches money, movement, identity, and staff operations. Waslni treats isolation, authentication, auditability, and payment safety as product requirements, not afterthoughts.
Passkeys
for platform operators
RS256
signed platform APIs
Audit log
for sensitive actions
3DS ready
gateway-led card flows
Control model
Defense in layers, not a single gate.
Waslni combines tenant boundaries, signed service calls, role permissions, payment provider controls, and operational audit trails.
Operator access
Platform operators use passkeys and step-up checks for sensitive flows. Admin access is permission-gated so staff only see the actions their role allows.
Signed service APIs
Platform-to-tenant calls use short-lived signed tokens with tenant audience binding, replay protection, and explicit action scopes.
Payment safety
Card details stay with payment providers. Waslni integrates gateway flows, wallets, cash controls, and provider-specific verification without storing raw card numbers.
Auditability
Sensitive platform and admin actions are recorded with actor, action, target, timestamps, and structured metadata for investigation and accountability.
Operational monitoring
Health checks, deployment targets, migration status, and demo lifecycle jobs give operators a clear view of tenant state before small issues become outages.
Security practices
The details operators ask about.
JWT tenant claims are verified in multi-tenant mode before authenticated requests proceed.
Redis key prefixes include tenant database identity to avoid cross-environment collisions.
Role permissions are declared in a single backend registry and enforced at route level.
Demo tenants have a defined lifecycle: approval, trial, archive, retention, and hard delete.
Firebase, maps, database, payment, and backend secrets are kept out of committed source.
Registration documents and uploaded examples are validated and stored through controlled flows.
Security is shared work.
Waslni secures the platform, but each operator is responsible for correct staff access, lawful use of customer data, payment-provider compliance, device security, and local regulatory obligations. We help you put the right operating habits in place before launch.
What's next
Your app.
Your brand.
Your customers.
WASLNI / PLATFORM
14
Try free for 14 days
Launching in 30 days - or less.
-> Palestine · Egypt · you next
A white-label platform to launch your Uber-style app — rides, delivery, restaurants, and shops. Start a free 14-day sandbox, no credit card and no engineering required.
WASLNI / PLATFORM
Launching in 30 days - or less.
-> Palestine · Egypt · you next