Why our infusions are unlimited and our flavors aren't

The K1 has two reservoirs that look almost identical from the front panel. One holds infusions (electrolytes, BCAA, vitamins, hydrogen, magnesium). The other holds flavors (passionfruit, lychee, kyoho grape, etc.). Same form factor, same one-twist swap.

But the resupply is totally different. Infusions are unlimited — operators get a flat monthly bill, dispense as much as their guests want. Flavors are metered, billed per drink.

This confuses people. So an explanation.

Infusions are essentially shelf-stable concentrates of well-understood ingredients. Magnesium glycinate. Sodium citrate. Ascorbic acid. The cost of a serving's worth, at our manufacturing volume, is in cents. The bottleneck isn't ingredient cost; it's the cleaning cycle and the drum logistics. Once those are paid for, an extra dose costs us essentially nothing. Charging per dose would mean spending more on metering than we'd recover in revenue. So we don't. Operators get one flat fee, and they push hydration as hard as they want.

Flavors are different. They are real food products: cold-pressed concentrates, refrigerated supply chain, real spoilage, tropical-fruit commodity prices that swing 30% year-on-year. A serving of passionfruit costs us materially more than a serving of magnesium. We can't absorb that into a flat fee without either jacking everyone's monthly bill or cutting corners on the actual fruit. So we meter it. Operators see exactly what they're paying for, can control the cost, and we get to keep using real ingredients instead of "natural flavor compound 47b."

The model isn't pretty. Two billing schemes is more friction than one. But it lets us be honest with operators about what each thing costs, rather than averaging the burden across customers in a way that punishes the ones who don't pour many flavors.

If we ever switched to "everything unlimited," we'd be cutting flavor quality. If we ever switched to "everything metered," we'd be discouraging hydration, which is the actual point of the company. So the awkward two-system model stays.

Sometimes the right answer to a UX problem is to keep the friction and explain it.