What we build.

Five things, done properly, by two engineers who see the whole chain. If a project needs something outside this list we will say so on the first call rather than learn it on your budget.

Capabilities in detail

  • Web platforms & SaaS

    Multi-tenant, billing, auth: the whole product

    The whole product, not a front end. Accounts, roles and permissions, subscription billing with the VAT handled, and the admin side that keeps it running once real customers are on it. Built so the second tenant does not need a rewrite.

    • Multi-tenancy, roles and an audit trail
    • Subscription billing with VAT-ready invoices
    • Auth, SSO and account recovery flows
    • Admin and support tooling from day one

  • Backends, APIs & integrations

    Queues, webhooks, systems that talk to systems

    Systems that talk to systems. Queues, webhooks, idempotency and retries. The unglamorous reliability work that decides whether an integration survives its first bad week rather than its first demo.

    • REST and webhook APIs, versioned and documented
    • Queues, background jobs and retry policies
    • Payment, accounting and CRM integrations
    • Migration off spreadsheets and legacy databases
    • Observability: logs, metrics and alerts

  • Dashboards & data systems

    Real-time, reporting, operations at a glance

    Operations at a glance. A live feed in, one calm screen out, with the history, the roll-ups and the exports the finance side asks for sitting underneath the same data.

    • Real-time feeds over websockets
    • Time-series storage and roll-ups
    • Scheduled, exportable reporting
    • Threshold alerting and escalation

  • Mobile & internal tools

    Field apps, admin panels, automation

    The apps a crew carries and the panels the back office lives in. Offline-first where the signal drops, and internal tools measured by how much time they remove from a process, not by how they look in a screenshot.

    • Offline-first field apps that sync on reconnect
    • Photo and signature proof-of-work
    • Admin panels and back-office consoles
    • Process automation and scheduled jobs

  • Beyond the screen

    Embedded firmware, electronics, IoT, control

    When the software needs a body. Firmware, a board, sensing and control, designed alongside the platform it reports to, by the same two people, so nothing is lost in translation between the app and the hardware.

    • Embedded firmware in C, on STM32
    • PCB design and board bring-up
    • Sensing, power and telemetry
    • LTE-M, BLE and MQTT links
    • Control systems and prototyping

This is what an operations screen looks like when it is finished.

The machine below is a demonstration. Everything on its screen was drawn by us to show density, hierarchy and the shape of a real dashboard. It is not a client system, it holds no client data, and none of the numbers on it are anyone's revenue.

The ELX workstation, running a concept dashboard.

CONCEPT

  1. 01 KPI band

    Dashboards and reporting. The numbers a founder actually checks, in one glance.

  2. 02 Quotes table

    Workflow and automation. Quotes become jobs, jobs become invoices, without a spreadsheet.

  3. 03 Left rail

    Internal tools. One login for ops, sales and finance, with roles that match the org chart.

  4. 04 Chart

    Live data. Pipeline in rands, updated as it happens, no refresh button.