What ILSS is
ILSS — Integrated Logistic Support System — is a private B2B platform that runs the operational backbone of complex equipment fleets. It is operated for industrial operators and their authorised service partners. ILSS is not a public SaaS product and accounts are not available for self-signup.
Where it runs
ILSS is built and operated from the Western Cape, South Africa. All web traffic is served from the Cloudflare global edge, with data residency for the operational database (Cloudflare D1) at the Cloudflare edge nearest to the user, replicated globally for read performance.
Why it exists
Field operations on complex equipment — field-deployed equipment, vehicle-mounted systems, supporting infrastructure — generate the kind of operational data that paper logs and disconnected spreadsheets simply cannot keep up with. ILSS replaces that fragmented tooling with a single record of truth: every ticket, every job card, every part consumed, every training certification, every contract obligation, every SLA breach — all linked back to the assets in the field, fully auditable, and available offline.
How it's built
ILSS runs entirely on Cloudflare — Workers for the API, Pages for the web apps, D1 (SQLite at the edge) for relational data, R2 for object storage, KV for sessions, and Queues for events. The mobile apps are progressive web apps (PWA) and, on Android, Trusted Web Activities (TWA). All field-facing screens are offline-first.
The codebase is TypeScript end-to-end, with strict separation between the reusable platform layer and the ILSS-specific domain code. Every endpoint is permission-gated, every action is audit-logged, and every release ships with passing tests, type checks and end-to-end build verification.
Open standards
- REST API documented in OpenAPI 3.0. The spec and Swagger UI live at
api.ilss.co.za/api/docsand are accessible to authenticated users only — anonymous visitors see 401. - Architecture and operating documents at docs.ilss.co.za.
- Source-of-truth schema published in the docs viewer, with migrations tracked in version control.
How to reach us
The team is reachable for service, security and privacy matters at the addresses listed on the contact page. Responsible disclosure of security issues is welcomed — see the security page.