Developer tooling · 2025
Fluxa
A generative identity system that redraws itself with every product release.
In short
Fluxa shipped weekly but its brand could not keep pace, so Sparza replaced the fixed logo lockup with a rule set: a parametric mark whose geometry is driven by release data. Marketing, product, and documentation now generate on-brand artwork in minutes without a designer, from one system shipped as code alongside the guidelines.
The challenge
Fluxa is a developer tooling company with a weekly release train. Every release wanted an announcement, every announcement wanted artwork, and artwork was made by whoever had an hour free. Over eighteen months that produced roughly four hundred assets with no shared logic between them.
The visible symptom was inconsistency. The real cost was time: a launch took two to three designer-days of artwork production, which meant either the design team stopped doing design work or the launch shipped with something improvised. Both happened regularly.
What we found
We audited eighteen months of released artwork and interviewed the four teams producing it. What we found:
- Nobody was going off-brand deliberately. Every improvised asset was made by someone who could not find, or could not open, the correct source file.
- The bottleneck was one person. A single designer was the only one who could produce launch artwork, and they were the constraint on every release date.
- The artwork carried no information. Four hundred assets were decorative; none encoded anything about the release they announced.
- Guidelines were never opened. The existing forty-page PDF had been downloaded eleven times in a year, mostly by new hires in week one.
The strategy
A static identity would have reproduced the problem in a nicer typeface. Instead we designed a rule set: a parametric mark whose geometry is a deterministic function of release metadata — version number, release type, and component touched.
Determinism was the point. The same input always produces the same mark, so artwork can be generated by anyone, in any tool that reads the spec, without review. The brand stops being a file someone owns and becomes a function anyone can call.
Three decisions that shaped it
The mark is a function, not a file
The mark's construction takes three parameters and returns one geometry. Because it is deterministic, the same release always renders identically whether it is generated in the docs pipeline, a marketing template, or a designer's canvas — which removes the review step that was the actual bottleneck.
Constrained on purpose
The parameter space is deliberately narrow: a bounded stroke range, six permitted rotations, and two colour states. Wide-open generative systems produce novelty and then drift. A narrow one produces variation that still reads as one brand at the four-hundredth asset.
Shipped as code beside the guidelines
We delivered a small, dependency-free module and a one-page written spec rather than a manual. The module is what teams actually use; the spec exists so the system can be reimplemented if the module is ever replaced. Nobody has to open a PDF to stay on brand.
How it was built
The generator was built as a plain module with no framework dependency, so it drops into the marketing site, the docs build, and the design tooling without three separate implementations. Output is vector, sized from a single scale parameter.
We tested it against the eighteen-month archive: every historical release was regenerated through the new system to confirm the parameter space produced distinguishable, on-brand results across four hundred real inputs rather than a handful of chosen demos.
How the work ran
The system went live with one release as a controlled test, then became the default for all release artwork the following week. The previous asset library was archived rather than migrated.
Audit and discovery
Eighteen months of artwork catalogued; interviews with the four teams producing it.
Rule design
Parameter space defined and pressure-tested against historical releases.
Implementation
Generator module built dependency-free, plus motion behaviour and colour states.
Rollout
Pilot release, then default for all launches. Spec and module handed to the platform team.
The outcome
Release artwork moved from a two-to-three-day production task to a generated step inside the existing release process. The design team stopped being a dependency on the release train, and the brand now reads as a single system across a corpus that keeps growing weekly.
Minutes
Release artwork, down from days
400+
Historical releases regenerated in testing
Zero
Design handoffs to ship launch art
What we handed over
- Parametric identity system and written construction spec
- Dependency-free generator module
- Motion behaviour specification
- Colour states for light and dark surfaces
- Templates for marketing, product, and docs
- Handover to the platform team
Work with us on something similar
Fluxa drew on the services below. Tell us what you’re building, or see the rest of our work.