● Food Intelligence · Sweetener
Across 2,592 logged allulose meals, members averaged +21.6 mg/dL — but allulose itself has a glycemic index of 0. The rare sugar passes through unmetabolized, so the cohort signal is the meal context: granular allulose anchors at +22 mg/dL in the cohort (n=924), and the recipe-builder form is set to 0 because GI is 0. Bakers reach for it because it's the one non-nutritive sweetener that browns and caramelizes like sucrose.
Tap any ingredient below to swap it for a glucose-friendlier alternative. Your Signos Glucose Score, predicted curve, and nutrition update in real-time. Every swap is data-backed by real CGM response measurements.
No — allulose alone is glycemically inert (GI=0, passes through unmetabolized). The +21.6 mg/dL cohort average across 2,592 logs is driven by the meal context, not the sweetener. Allulose is a rare sugar that the body absorbs but doesn't metabolize, which is why the published glycemic index is 0 and every form anchor in our recipe builder is zeroed accordingly. The cohort mean of +21.6 mg/dL exists because members log allulose in coffee, in keto baking, in yogurt — the rest of the meal is what shows up on the trace. The vehicle deltas confirm it: allulose in coffee tracked −1 mg/dL below the alone baseline (n=1,176), allulose in tea sat flat (n=220), allulose in yogurt was effectively unchanged (+0.4 mg/dL, n=241), and keto-baked-good logs added +3 mg/dL — the almond flour, eggs, and butter in those recipes, not the allulose. Where the cohort spike does climb is on total meal carb load: heavy-carb meals (70–110g) averaged +29.1 mg/dL versus +20.5 mg/dL in the light-carb bucket (n=2,179) — a 42% escalation that's about the surrounding food. Bakers reach for allulose because it's the one non-nutritive sweetener that browns and caramelizes like sugar.
Some members spike +17.3 mg/dL. Others spike +29.1. The only way to know how you'll spike is to measure with a Signos CGM.
Allulose produces a cohort-mean peak of +21.6 mg/dL across 2,592 logs from 374 members — but the sweetener itself contributes essentially zero metabolizable carbohydrate, which is why the published glycemic index is 0 and every form anchor in our recipe builder is zeroed accordingly. The body absorbs allulose but doesn't metabolize it; the rare sugar passes through largely intact, which is why the FDA exempts it from total-sugar and calorie nutrition labels. The cohort signal reflects the meal context — coffee, yogurt, keto baked goods, surrounding starch. In matched-pair vehicle data, allulose-in-coffee tracked −1 mg/dL below the alone baseline (treatment mean 21.2 vs 22.1, n=1,176 vs n=951), allulose-in-tea sat flat (21.6 vs 22.1, n=220), and allulose-in-yogurt was effectively unchanged (22.5 vs 22.1, n=241). The headline structure: zero from the sweetener, low single-digit shifts from the vehicle, and large carb-load escalations when allulose lands inside a heavier meal.
This page draws on 2,592 logged allulose meals from 374 unique Signos members, captured through the Signos production CGM platform between Mar 2025 and Apr 2026. Data were filtered to postprandial glucose responses (PPGR) between 0 and 100 mg/dL to exclude sensor artifacts. Modifier effects were estimated using Welch's t-test on matched pairs against a defined baseline; reported effects carry p<0.05 minimum, with the dominant modifiers reaching p<0.001. Because allulose has a published glycemic index of 0 and glycemic load of 0, the recipe-builder form anchors are overridden to 0 mg/dL — the underlying cohort means (preserved in `option_mean_full_cohort`) reflect the carbs members ate alongside each form, not the allulose itself. Allulose logs were identified by a regex matching the bare term "allulose"; no compound-term exclusions were required because the term doesn't over-match into other food categories. A minimum of 30 matched meals was required for any sub-cohort to appear in the modifier table.