Afrisol
A company presence for a Kisumu-based consultancy, shipped through the same unified build-and-deploy pipeline as every other product on this map, with exactly one documented deviation: the application lives in a subdirectory of its repository, so the build step changes into it before building rather than the pipeline being special-cased for this one client.
The correspondence form went live ahead of its own mail delivery on purpose. Validation, a submission rate limit, a spam honeypot and input sanitization all shipped first and ran for a period with submissions logged rather than emailed, deliberately staged so the first messages to actually reach an inbox would go to a test address before the production mailbox was switched on — the same staged-rollout discipline the estate applies to anything that reaches a real person on the other end.
The site's own healthcheck needed one small, fleet-wide correction on the way to production: a container health probe that resolved a loopback address the wrong way for an IPv4-only application, a mistake worth fixing once, in the shared template, rather than once per product.
← back to the map