Multi sided execution, errand and delivery platform that turns a funded request into a verifiable real world outcome across five connected applications.
JYRO converts a user request, its funding and its instructions into a completed real world outcome that can be proven. Where a standard delivery app moves a package between two points, JYRO coordinates the whole execution chain: a user creates and funds an errand, an agent coordinates fulfilment and sources items, a rider handles physical movement, and the platform captures evidence that the requested outcome actually happened. As CTO I led the technical direction, the system architecture and the coordination between all five applications, so the ecosystem behaves as one execution system rather than five separate products. Every meaningful action ties back to a recognised actor, a timestamp, a task status and supporting evidence, and payment is connected to verified execution rather than to someone simply marking a job done.
Highlights
Five connected applications plus an offline execution partner role
Verification gated payments tied to evidence, not to manual completion
Real time rider location and task status across every application
Cluster model for local accountability, recovery and escalation
Prepared a 282 case QA scope spanning authentication, KYC, errands, delivery, batching, chat, wallets and cross application workflows
Architecture direction
- Node.js/NestJS
- React Native
- React/Next.js
- PostgreSQL
- WebSockets
- Cloud object storage
- Docker
- CI/CD
The JYRO Application Ecosystem
JYRO is made up of five digital applications and one offline execution role. Each one owns a distinct part of the execution chain, and the platform is structured so that no participant can bypass an approval, payment or verification step.
JYRO User App
Where customers create, fund, monitor and confirm errands. Covers registration with OTP and KYC verification, pickup and delivery selection, budget and payment configuration through wallet or card, live task tracking, chat with the assigned agent or rider, approval of sourced items, confirmation of completed errands and dispute reporting.
JYRO Agent App
The execution controller. Agents discover and accept errands, confirm a request can be carried out, source or purchase items, submit item details for user approval, request and monitor riders, update task progress, run several active tasks at once and escalate exceptions that normal execution cannot resolve.
JYRO Rider App
Handles the physical movement. Riders manage availability, accept delivery requests, view pickup and delivery details, broadcast live location, confirm pickup and handover, capture photo, note, location and time evidence, manage batch deliveries and report failed deliveries.
JYRO Cluster Manager App
Operational supervision for groups of agents and riders. Cluster managers build teams, vouch for participants through cluster codes, monitor active errands and delivery performance, resolve team level issues, support reassignment of failed or delayed jobs and escalate serious problems to administrators.
JYRO Admin Application
Central authority over the whole ecosystem. Administrators manage every actor type, review KYC, control roles and permissions, oversee wallets and transactions, investigate failed tasks, resolve disputes, perform operational overrides and recover errands stuck in an invalid state.
TIP, offline execution partner
An operational channel rather than an app. TIPs bridge the gap between the platform and the physical world where a task cannot be finished entirely through the digital workflow: local sourcing, location specific support and verified handovers, all still traceable to an accountable actor.
