Client stories

Names and sectors are used with permission. Stories mention the engagement type so you can judge fit.

“They sat with our intern while he stepped through py-spy samples. The tone was direct without being harsh—exactly what we needed before peak harvest reporting.” — Willem V., engineering manager, agritech (Paarl)

“We booked the hotspot review thinking it would be enough; it wasn't—the problem was cross-service. AeroTensor was upfront that we needed the full profiling week, and they credited part of the review fee toward the larger engagement.” — Aisha K., platform lead, edtech (Durban)

“Documentation arrived as Markdown in our repo, not a locked PDF. My only gripe is we wished they'd joined our retro a day earlier; scheduling was on us though.” — James T., CTO, subscription billing (Cape Town)

Case: municipal open-data export job

Performance profiling engagement · 11 days · Remote

A Western Cape municipality exported CSV bundles nightly. Runtime crept from 40 minutes to over three hours after a library upgrade. We reproduced on anonymized slices, found accidental eager loading in a generator pipeline, and shipped two PRs. Runtime returned to 38 minutes on their hardware.

Constraint: No production profiling allowed; all work in staging with masked rows.

Interaction: Daily 15-minute stand-up with their contractor team; one in-person review at Adderley Street.

Case: websocket fan-out memory climb

Load test interpretation + follow-up profiling · Johannesburg

During a Locust run, worker RAM climbed linearly with connections. Interpretation day pointed to uncached subscription maps; the follow-up week added weakref cleanup and a regression test. They re-ran load tests internally and kept us on a monthly office-hour retainer for one quarter.

Discuss a similar project