SYNFLOX
SYNFLOX came from a practical licensing problem: some customer installations can validate online, and some have to keep working when the network is not there.
A central licensing system for software vendors that need products, plans, subscriptions and both online and offline validation in one control point.
The licensing problem
Once a vendor has several products, duplicating subscription state and activation rules in every app becomes expensive and inconsistent. Offline installations make it harder because the license still needs a trust model without a live request.
One authority
SYNFLOX centralizes products, companies, plans, subscription state and licensing control. Connected applications can validate against the API; disconnected deployments can use protected license material for offline checks.
Admin and client surfaces
Administrative work and customer-facing work are different jobs. I keep those surfaces separate so operator controls, customer actions and permission rules do not collapse into one oversized dashboard.
Security is part of the product
Authentication, RBAC, protected identifiers, license integrity, audit history and clock-tampering concerns all affect the product model. In a licensing system, those are core behavior—not a security page added at the end.
Current shape
The public repositories show the core backend/frontend split, while later work also explores separate admin and client surfaces. I describe the product capability here without exposing private implementation details.
Back to all work
Work index ↗