CY-GONEngagements delivered
30
27 of them running in production. Every one is named on the work page.
Track record
Systems that stayed up.
Delivered across individual, corporate, and government clients, in sectors where downtime and bad data have a direct cost.
Client types
03
Individual founders, corporate teams, and government adjacent bodies.
Sectors
05
Each with its own failure mode.
SectorsWhat each one demands
- 01AgricultureField data capture on unreliable connectivity, offline first sync, and pricing or yield models that still have to answer when the network does not.
- 02Fintech and mobile moneyTransaction integrity, reconciliation, fraud signals, and audit trails that hold up when a regulator reads them.
- 03LogisticsRouting, tracking, and dispatch, where a record that is ten minutes stale costs a delivery.
- 04EducationContent and assessment systems serving large intakes on low end devices and shared connections.
- 05Public sectorProcurement constraints, data residency, long support windows, and a handover an internal team can actually run.
How the work is staffed
A small, senior team. One lead, start to finish.
Cy-Gon is led directly by Godfrey Muganyizi, who scopes, architects, and stays accountable for every engagement. It is not a funnel into a bench of unnamed juniors. For builds that need more hands, a small, senior network of engineers and designers is brought in project by project, still under that same direct accountability.
It also sets what Cy-Gon will not do. No retainer billed for people you never meet. No price on custom work before the diagnosis step is finished. No new engagement accepted while an existing one is unstable.
LiveThe conditions we design for
Half of this work runs on connections that are shared, metered, or intermittent. Rather than describe that, here is what your own browser reports about the connection you are reading on right now.
Your browser does not report network conditions to pages. Safari and Firefox both withhold this, which is a reasonable privacy decision and a real constraint when you are building for low bandwidth users.
- Class
- Not reported
- Data saver
- Not reported
- Device memory
- Not reported
- Cores
- Not reported
- Viewport
- Not reported