AI-native workflows at Gruve | License key utility

Sanath Devadiga:

Every product team here was writing its own licensing logic. Generation, validation, seat limits, renewals. The same problem solved five times, with different bugs each time.

So I built it once. A product registers, gets an API key, and embeds it. Issuing a key takes seconds: subscription, trial or perpetual, metered by device seat, token usage or feature. Every key is signed with Ed25519, so a product verifies one offline against the public key and a tampered key fails instantly.

The customer side runs itself. They redeem in their own portal and the product unlocks against the seat limit. Expiry reminders send themselves. Renewal requests land in an approval queue instead of an inbox, revoking a leaked key locks the product, and every action writes to an audit trail. Integration is about five lines.

Then I stopped reading the dashboard to run it. An assistant sits on the live license data, so “which license is expiring” comes back as a customer, a product, and two days remaining. Licensing is easy to get wrong. Now nobody has to get it right twice. Built during our engineering AI hackathon, and recognized by our global jury.