The NanoBase™ Family

Most delivery systems in personal care are built around one hero SKU. A brand balances an emulsifier system against HLB logic, the Hydrophile-Lipophile Balance scale William Griffin published in 1949, until one flagship serum or cream holds together. That balance is specific: one oil, one emulsifier blend, one ratio, one formula. Ask the same brand to extend the range into a cleanser, a hair serum, or a fragrance mist, and the HLB math starts over from zero, because the number was never built to travel across a product line. It was built to hold one emulsion together.

NanoBase™ answers that trap at the level of the chassis rather than the formula. It is not a single architecture but a family of variant architectures, each built on the same tri-domain, DLVO-stabilized, lecithin-based chassis and each tuned for a different class of finished cosmetic. A brand does not re-derive its delivery logic every time it adds a product to a line. It chooses the variant tuned for that format and keeps building on the same NanoBase™ Logic it already trusts from its first SKU.

The HLB “one hero SKU” trap

Give HLB logic its due. Matching an emulsifier’s HLB value to an oil’s required HLB is genuinely useful engineering, and it is why most emulsions on shelf hold together at all. The limitation is not that the math is wrong. It is that the math is narrow: one balance point, solved for one oil, inside one formula. A brand that has mastered HLB for its bestselling moisturizer has not learned anything portable about stabilizing a rinse-off cleanser, a leave-on hair serum, or a fragrance-forward mist. Each new format reopens the same balancing act from the beginning.

That is the one hero SKU trap. A range grows one product at a time, and under HLB logic each new product can mean a new emulsifier system, a new supplier relationship, or a new specialist to solve it. Depth accumulates in a single SKU while the next format starts from a blank page.

One chassis, six tuned architectures

NanoBase™ is built as a family for exactly this reason. Every variant shares the same tri-domain architecture: a nanoemulsion domain, a nanoliposomal domain, and a micellar domain, coexisting by design inside one pourable, lecithin-based chassis stabilized by an electrostatic wall reasoned about through DLVO theory. What changes from variant to variant is tuning, how that chassis is calibrated for the sensory profile, active load, or format a given finished product needs. What does not change is the underlying design logic. A brand can build its serum on one variant, its cleanser on another, and its hair care on a third, without leaving the tri-domain logic it already understands.

The six variants below make up the current family. Each is presented here purely in terms of cosmetic performance and sensory fit. “Clinical” names a cosmetic performance tier tuned for a heavier active load, not a medical or clinical claim, and none of the six carries a disease or structure-function claim.

What every variant shares

Tuning changes from one variant to the next. The engineering underneath does not. Every architecture in the family shares the same four commitments:

• Tri-domain coexistence: a nanoemulsion, a nanoliposomal, and a micellar domain engineered to coexist in one continuous phase, never blended into a single average.
• DLVO electrostatic stabilization as a design principle: an engineered interfacial charge intended to hold the domains apart, reasoned about through DLVO theory and stated as a design principle rather than a measured or certified value.
• DLS characterization on every batch: dynamic light scattering is the assay Pensive Beauty® runs on every lot of every variant, and it reports hydrodynamic size, not structure.
• A finished formula that cold-processes on top: whichever variant a brand selects, the finished product built on it is cold-processable at any qualified contract manufacturer on standard equipment, by gentle, room-temperature mixing.

Pensive Beauty® designs, manufactures, and characterizes every variant in the family. A brand or its contract manufacturer does not produce the architecture itself, on any variant. What a brand builds is the finished formula on top, loading its own actives and fragrance into the chassis it has chosen. That division of labor holds across the whole family; only the chassis tuning changes.

The same standard holds across the family too. Every variant of NanoBase™, like the architecture itself, is formulated to align with the Clean at Sephora standard.

Choosing a variant for a range

Most brands do not start with all six variants at once. They start with the format closest to their first SKU, often Classic or Luxe, and add Cleanse, Cortex, or Aroma as the range extends into cleansing, hair, or fragrance. Because every variant sits on the same tri-domain architecture, what a formulator learns on one variant, how actives partition, how the batch reads on DLS, how the finished formula cold-processes, carries forward to the next.

The fastest way to find the right variant for a specific finished product is to scope it directly. Use the free NanoBase™ AI Chemist to reason through a formula against a given variant, or request a sample and full spec of the variant closest to your next SKU and run it on your own bench. Brands and contract manufacturers planning a multi-product launch should talk to our partners team about sequencing a rollout across the family. For the company behind the architecture, visit pensivebeauty.com.