. . ..... . ..::---::.. .::--===--::. .:--==+==--:. . ..... .::--===--::. . ..... ..::---::.. ..::---::.. ..::---::... .::--===--::. .:... .::--===--::. .:--==+==--:. : .:--==+==--:. .::--===--::. : .::--===--::. ..::---::..: : : : ..::---::.. . ..... :: .:::::::::. . : ..... . . ::.::--=======--::.: : .:-==+++***+++==-:. ..... :--=++**%%%%%**++=--: ..::---::.. .:-=++*%%#####%%*++=-:. . .::--===--::.: : : : : :.:-=+**%##@@@##%**+=-:. ..... .:--==+==--:. .:-=++*%%#####%%*++=-:.: : : : ..::---::.. .::--===--::. :--=++**%%%%%**++=--: : :::--===--::. ..::---::.. .:-==+++***+++==-:. .:--==+==--:. ..... :::--=======--::. .::--===--::. : .:::::::::. ..::---::.. :: : ..... . .....: : . ..::---::.. : .::--===--::. . . :.... . .:--==+==--:. ..::---::.. .::--===--::. .::--===--::. ..::---::.. .:--==+==--:. ..... .::--===--::. . ..::---::.. . . ..... .

I did not start Sekiwa as an abstract licensing product. I started it because Musika, software I was building for real businesses, needed licensing that could survive the conditions in which those businesses actually worked.

The problem appeared in real shops

Musika runs on devices used to keep a business moving. In Zimbabwe, the internet can be unstable, costly, or unavailable at the moment it is needed. If a license check depends on reaching a server every time, a legitimate customer can be locked out of software they paid for. A network problem becomes a business problem, even when neither the customer nor the software has done anything wrong.

I could not accept a licensing system that protected my software by interrupting a shop. Customer continuity had to be a design requirement, not a special exception.

Developers still need control

Going fully local was not a complete answer either. Developers need to know which installations are licensed, bind each issued license to its approved device, revoke access when necessary, and protect the revenue that funds continued development. Uncontrolled copied installations make it difficult to run a sustainable software business.

The challenge was to hold both truths at once: customers must be able to keep working offline, and developers must retain meaningful control over paid software.

A signed license the device can verify

The approach is to issue a cryptographically signed snapshot through authenticated online activation and cache it on the device. The application verifies that proof locally with a public key, including when the connection is unavailable. The private signing key stays on the server.

This means the cloud remains the place where developers manage apps, customers, plans, devices, and issuance. After online activation, the customer can keep working offline within the snapshot’s signed expiry and revalidation limits. Later revocations become known when the device reconnects.

From Musika to Sekiwa

Once the model worked for Musika, I realised the problem was not unique to one product or one country. Developers everywhere build for factories, field teams, schools, shops, and other environments where continuous connectivity cannot be assumed.

I turned that solution into Sekiwa so other developers could use the same model without building an entire licensing system themselves. Its roots are Zimbabwean, and those constraints made the product more honest. Its purpose is global: give developers control over paid software while helping legitimate customers keep working.

+

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

+

The internet can make licensing easier. It should not decide whether paid software works.

See how Sekiwa works →