NanoBase™ vs HLB
Six failure modes brands are patching around HLB today, matched against the tri-domain architecture that replaces the design logic instead of patching it.
One 1949 balance number vs one tri-domain chassis | ~185 nm design target · DLS-characterized every batch
The failure modes brands keep patching
Most emulsified skincare is still designed to an HLB target, a number invented in 1949. Formulate long enough and you stop noticing it, the way you stop noticing a load-bearing wall you have learned to build around. William Griffin’s Hydrophilic-Lipophilic Balance, HLB, was built to answer exactly one question: will this oil phase and this water phase stay married in the jar. Seventy-plus years later, it still answers that question well. It was never built to answer the questions a brand actually has now: how many classes of active one system can carry, how many SKUs one chassis can support, and how many times R&D has to start over when the next active gets added. This page is the head-to-head, six failure modes brands are patching around HLB today, matched against the tri-domain architecture that replaces the design logic instead of patching it: TDA Logic.
What HLB actually optimizes for
Griffin’s system assigns every surfactant a single number, roughly 0 to 20, describing how hydrophilic or how lipophilic it is. Match the blended HLB of an emulsifier system to the required HLB of the oil phase and the two phases stay married instead of splitting on the shelf. That is the entire job, and HLB still does it well: it gave the industry a shared language and a predictive shortcut where trial and error used to be the only method. Nothing here disputes the arithmetic.
HLB is a jar-stability instrument pressed into service as a full formulation strategy, and that mismatch is where the patching starts.
What brands keep patching around HLB
| Failure mode | The patch brands reach for today | The tri-domain design response |
|---|---|---|
| One scalar cannot describe a system meant to carry several classes of active at once. | Split the range across separate emulsion bases per active class and manage the INCI overlap by hand. | One architecture, three polarity-matched domains. Polarity becomes a routing decision, not a compromise. |
| Push the active load or mix polarities and an HLB-tuned emulsion tends to destabilize. | Cut concentration, add extra stabilizers, or quietly shorten the shelf claim. | Three homes for actives, lipophilic, amphiphilic, hydrophilic, are designed to raise the practical payload ceiling without a re-solve. |
| Re-balancing is costly, so ranges stall on one optimized hero emulsion. | License or engineer a second base from scratch for the next launch, doubling stability testing. | One chassis supports a whole family of finished formulas, not one hero SKU. |
| Droplet size is often not set as a design target or tracked batch to batch. | Treat size as whatever the process produces and test only the finished product. | A ~185 nm design target for the Architecture, DLS-characterized every batch. |
| Adding one new ingredient shifts the required balance and forces reformulation. | Re-run the HLB math and re-test stability every time R&D touches the formula. | Dose the new active into the domain that matches its polarity. The chassis does not move. |
| Classic HLB emulsification is usually a hot process, which limits what it can carry. | Add process steps and cooling stages to protect heat-sensitive actives. | The finished formula built on the architecture cold-processes on standard equipment. |
One point of discipline sits underneath all six rows. Pensive Beauty® manufactures the NanoBase™ Architecture and ships it as a finished raw material. Your team does not make or run the architecture itself; you formulate on top of it, adding actives, fragrance, and sensory into a chassis that has already done the colloidal engineering. The cold-processable step above belongs to that finished formula, not to the architecture underneath it.
Inside the tri-domain architecture
When you formulate on a modern architecture like NanoBase™, polarity stops being a compromise you tune around and becomes a routing decision. The NanoBase™ Architecture is a pourable aqueous system built on a single lecithin-based chassis and designed to an electrostatic (DLVO) stabilization specification, not a blend of emulsifiers tuned to one balance number. It is engineered as a tri-domain architecture (design specification), with three domains designed to coexist inside that one chassis: a nanocolloidal domain for lipophilic actives, a nanoliposomal domain for amphiphilic actives and peptides, and a nanomicellar domain for hydrophilic actives. That coexistence is the tri-domain architecture, and HLB has no equivalent concept to offer, because HLB was built around the assumption of one emulsion, one balance number, one job. The stabilization design is electrostatic (DLVO): surface charge intended to keep droplets, vesicles, and micelles from coalescing into each other or averaging into a single phase. That wall is the design principle behind the architecture’s stability, not a measurement we are reporting. The colloidal terms are defined precisely in the glossary.
Multi-angle dynamic light scattering (DLS) is the only characterization assay behind this page, and we describe what it shows honestly. DLS reports a size distribution, not a picture of structure, so the Architecture is DLS-characterized every batch against a ~185 nm design target: a size and distribution-width measurement, not a real-space image of structure. A single-population system reads narrow. A tri-domain design, three kinds of carrier sharing one continuous phase, is expected to read as a broader, multimodal distribution rather than one narrow peak.
The physics HLB never had to answer
HLB is not the only single-number convention in emulsion science, and the deeper one is worth naming because it explains why coexisting domains are rare by default. Israelachvili, Mitchell and Ninham’s 1976 packing-parameter framework holds that a given amphiphile’s molecular geometry predicts one preferred equilibrium morphology, micellar, bilayer, or planar, depending on its effective shape. TDA Logic does not contest that framework, and it does not claim to have disproven it. It engineers within the kinetic-stability paradigm the framework leaves open. McClements (2012) established that nanoemulsions are kinetically, not thermodynamically, stable systems, held apart by an activation-energy barrier rather than by sitting at a single global energy minimum. Gupta, Eral and Hatton (2016) describe that same activation-barrier behavior as the general mechanism of kinetic colloidal stability. An electrostatically stabilized system can, in principle, hold a deliberately co-populated, kinetically trapped set of nanocolloidal, nanoliposomal and nanomicellar domains for the working shelf life of a finished product, which is what the NanoBase™ Architecture is designed to do.
In the polymer self-assembly literature, coexisting morphologies inside one system have often been framed as a loss of synthetic control to be engineered away, not a feature to design for (Doncom et al., 2017, a polymer-field convention describing that field’s chemistry, not a study of NanoBase™ chemistry). TDA Logic takes the opposite position on purpose. What one field framed as a defect, a co-populated system, NanoBase™ makes the design: a tri-domain architecture (design specification), DLS-characterized every batch and designed to an electrostatic (DLVO) stabilization specification rather than an HLB target. Deeper citation detail lives on the research and evidence page.
HLB vs the NanoBase™ Architecture
| Attribute | HLB (1949) | NanoBase™ Architecture |
|---|---|---|
| Design goal | Stop oil and water from separating in the jar | Deliberate tri-domain coexistence (design specification) |
| Core instrument | A single balance number, roughly 0 to 20 | A tri-domain architecture on one lecithin-based chassis: nanocolloidal, nanoliposomal, nanomicellar |
| Stabilization principle | HLB matching of a surfactant blend | Designed to an electrostatic (DLVO) stabilization specification |
| Particle profile | Droplet size set by the process; not usually specified as a design target | ~185 nm design target, DLS-characterized every batch |
| Where it lives | A calculation performed per formula | A finished raw material formulated on top of |
| Status | Established convention since 1949 | Commercial raw material since 2025 |
Why the design logic matters for a brand
For a brand, the difference is strategic, not academic. HLB logic quietly caps what a range can become: one hero emulsion, a bounded active load, a reformulation project every time R&D wants the next ingredient. The tri-domain architecture is designed around each of those constraints from the start.
NanoBase™ is used by brands from first-batch founders to multinational producers. See the current tiers on the partners page. NANOBASE is the subject of a US trademark application in Class 001, with first commercial use in 2025, and the tri-domain framework is part of the curriculum entering the EVCC Medical Aesthetics Certificate Program in 2027. The open preprints describing the architecture’s DLS characterization are posted as preprints on Zenodo at https://zenodo.org/records/21971474 and https://zenodo.org/records/18616576.
NanoBase™ ships as an empty chassis for leave-on cosmetic use on intact skin. It carries no actives and makes no claim of its own; your formula, your actives, and your positioning ride on top of it. Explore the variant architectures tuned for different product classes in the NanoBase™ Family, or see how a finished formula comes together in the skincare formulation lab.
HLB taught the industry to stop separation. NanoBase™ teaches it to build.
If your range has hit an HLB ceiling, build on the architecture yourself: request a sample and spec sheet, or hand your brief to the free AI Chemist and watch it route your actives across three domains by polarity in minutes.