Bae vs GlycemicGPT

Bae and GlycemicGPT are both lifestyle tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Bae

Bae lets you create multiple AI companions with distinct personalities and have ongoing conversations that accumulate personal history over time. The free tier gives you a daily message limit and multiple companion slots, which is enough to test the format and see whether the memory model holds up across sessions. The ceiling arrives fast: permanent memory, which is the core differentiating feature, is a paid-only capability. Without it, the relationship continuity the platform is built around does not fully exist. Adult content is also paid-only. For users who hit that wall and want persistent, intimate companionship, upgrading is the only path — there is no workaround on the free tier.

GlycemicGPT

The project connects to Nightscout, reads glucose time-series data, and surfaces pattern analysis plus threshold-triggered alerts to patients and caregivers without routing that data through a commercial cloud. Self-hosting via Docker Compose is the primary deployment path, documented in the repo. The alert pipeline works when your infrastructure stays up — which means the patient or a technically capable caregiver owns uptime. For T1D individuals already running Nightscout DIY stacks, this fits the workflow they have. For anyone expecting a hosted service to just work, the project is not that.

Attribute	Bae	GlycemicGPT
Pricing	Paid	Free
Price	$1.90/week or $99/year for Pro	—
Free trial	7 days	No
Open source	No	Yes
Has API	No	Yes
Self-hosted option	No	Yes
Platforms	Web, implied mobile via responsive design	Docker, Kubernetes, Android, Wear OS, Web (Next.js/React)
Released	—	2026-04
Pros	Multiple companion slots are available on the free tier, so you can test different personalities and archetypes before committing to the paid memory layer. Persistent memory on the paid tier means companions carry forward personal details across sessions, which means the conversation on day thirty actually references what you shared on day one instead of starting over. Explicit support for romantic and intimate relationship dynamics in a private, contained environment, so users exploring those scenarios do not have to work around content filters designed for general-purpose assistants. No integration complexity or technical setup — the platform is fully managed and browser or app-based, so there is no infrastructure overhead standing between you and the companion experience.	Integrates directly with Nightscout without requiring a platform migration, so patients who built their DIY stack over years do not lose historical data or existing tooling to get AI analysis. Self-hosted deployment via Docker Compose and Kubernetes manifests means glucose data stays on infrastructure you control, so you are not subject to a vendor's data retention or sharing policy changing after you depend on the tool. Predictive alerts with caregiver notification routing, so a dangerous glucose trend triggers a message to someone who can act — not just a graph the patient sees after the fact. GPL-3.0 open-source license, so you can read, audit, and modify the analysis logic — which matters when the output of that logic informs a medical decision. API availability, so teams building custom caregiver dashboards or integrating alerts into existing home-automation or on-call systems can pull data out without screen-scraping.
Cons	Permanent memory is a paid-only feature, which means the free tier structurally cannot deliver the long-term relationship continuity that is the platform's core value proposition — free users are testing a diminished version of the actual product. Adult content is gated behind the paid tier, so users who create companions specifically for intimate interactions and start on free will hit a hard content wall before the relationship develops, with no workaround. There is no API and no self-hosted option, which means any user or team that needs data portability, conversation export, or control over where their data lives has no path forward — and at that point the only real alternative is moving to an open-source LLM stack they control entirely. The platform is a single-purpose consumer product with no integration surface, so anyone who wants companion-style memory as a component inside a broader application or workflow cannot use Bae for that purpose — the architecture does not support it.	Alert reliability is entirely dependent on self-hosted uptime. A crashed Docker container, a rebooted home server, or a misconfigured restart policy silently kills the notification pipeline — and the project ships no built-in uptime monitoring or fallback. Families who experience a missed low-glucose alert at night either add a separate monitoring stack or move to a commercial CGM alert platform that owns its own infrastructure. The project is explicitly alpha-stage, and the repo's MEDICAL-DISCLAIMER.md signals the maintainers themselves treat it that way. Clinical accuracy of pattern analysis and alert thresholds is not independently validated. Endocrinologists presented with AI-generated glucose summaries from this tool have no published accuracy benchmarks to evaluate — which means the analysis stays informal and cannot substitute for clinical review, capping the use case at personal awareness rather than care coordination. No hosted option exists. Every deployment requires a patient or caregiver to own, provision, and maintain the server. When the technical person in a family's support network is unavailable, so is the tool. Teams that need reliability without server ownership switch to commercial Nightscout-compatible analytics add-ons.

Bottom line

Bae is paid while GlycemicGPT is free; GlycemicGPT is open source; only GlycemicGPT exposes a public API. Choose based on which difference matters most for your workflow.

Comparison data is sourced and verified by the AIDiveForge data pipeline. AIDiveForge is editorially independent.