The licensing system behind an After Effects extension.
JerryFlow customers using After Effects, and the team managing their accounts and licences.
JerryFlow is an After Effects extension for motion designers and video editors. Our work is the backend behind the extension: the account, licence and activation services that decide who can use it. We rebuilt that system for Jry.media and included the administration and data migration needed to carry existing customers into the replacement backend.
When the extension needs to check access, it talks to the licensing API. The backend connects that request to an account, its licence and its activation state. Keeping those records in one system gives both the extension and the support team a consistent view of the customer’s access.
A customer account, a subscription and a device activation describe different things. We built the services that manage those records together, including licence validation with hardware fingerprinting. This gives the product a way to associate extension access with the right customer and activated machine.
The administration panel covers licence issuance, activation keys and revocation alongside account and subscription management. Staff can handle access changes through the product’s own controls. Monitoring and alerts support the operational side of the service, where a backend problem can interrupt someone working inside After Effects.
Replacing the backend also meant migrating the V1 user data into the new system. We included deployment automation and monitoring in the work, so the project covered the transition and ongoing operation as well as the API implementation. The scope here is the backend rebuild for JerryFlow V2.
A customer’s account and licence establish their access to JerryFlow.
The extension submits an activation or validation request; the backend checks the associated licence and device.
The team manages subscriptions, activation keys and access changes from the administration tools.