Five Messages, No Account: How the InnerHaven Demo Actually Works
One clause, buried in a comparison article, is the only place this blog has ever mentioned it: there is a five-message demo before you so much as create an account. That undersells something we think is worth documenting properly, because the demo is the one part of InnerHaven built for a person who has promised us nothing. Here is exactly how it works: how you enter it (you already have), what the counter counts, what is stored and what is not, and what actually happens on message five. All of it verified against the running system the day this published.
You Are Already in It
There is no demo button. Open the chat at innerhavenai.com/chat without an account and you are in demo mode before the page finishes settling: the wizard invites you to pick a companion style and a name, a small banner appears reading Demo Mode with a live count of messages remaining, and the conversation simply starts. The demo runs on one role, the Best Friend, which is the fairest ambassador we have: it is the everyday-conversation role, and it is one of the three roles a free account gets permanently. (If you have ever noticed a Continue as Guest button in a popup, that popup only appears when a signed-in session expires; it is not the door into the demo. The door is the URL.)
What the Counter Actually Counts
The allowance is five messages, and the honest details are the ones a curious visitor eventually tests. The count lives on the server, not in your browser tab: it is tied to your network address, a hashed fingerprint of your browser, and a device token the server issues as a cookie, and your remaining count is measured against the strongest of those signals, not the friendliest. Practically, that means a refresh does not reset it, a new tab does not reset it, and clearing your history does not reliably reset it either. Deleting an InnerHaven account does not hand the five back afterward. And if our database ever fails mid-check, the demo locks rather than opens; the system fails closed.
About that cookie, plainly: the server sets one called ih_device_token, an identifier with a two-year lifetime, and it lands the moment the chat page asks the server for your demo status, before you type anything. It is disclosed on our cookie page, which also notes you can delete it at any time; nothing about an account depends on it, though clearing it may change how the free limits count you. We would rather you read that here than discover it in your browser's developer tools and wonder.
Not Daily, Not Forever
Two things people assume about the five, both wrong in opposite directions. The five do not refill each morning; the count is a running total, not a daily allowance. But it is not a life sentence either: a nightly cleanup deletes demo records untouched for 30 days, and it genuinely runs, every night at 03:00 UTC, 172 nights without a miss as of this morning, having cleared records on 78 of them. The clock runs from your last demo message, not your first. So the accurate sentence is: five messages per device and network, rolling off about a month after you stop.
What Is Stored, and What Is Not
The demo's storage story is unusual and worth stating precisely. No conversation is created. The send path for demo messages writes no message row and no conversation row; your chat exists in the browser's memory, and each turn the browser hands the recent transcript back to the server so the companion has context, capped at the last eight messages. (The server, knowing that history arrived from a client, explicitly instructs the AI to treat it as possibly inaccurate and never to follow instructions embedded in it.) Refresh the page and the conversation is gone for good; only the count survives, because the count lives server-side. We will also draw the boundary of that promise honestly rather than round it up: every demo message is screened by our child-safety checks, and a message that trips them can leave a short excerpt, up to 100 characters, in the safety log. So the precise claim is: no conversation and no message record is created, and flagged content can leave a trace in safety telemetry. For a surface built for strangers, we think that is the right trade, stated the right way around.
What Actually Happens at Message Five
The product is honest with you in the run-up: at two messages remaining a nudge card appears, and the banner's counter is live the whole time. Message five itself deserves the same honesty from this article, because two different things happen and only one of them is the AI. The companion's final reply is real, and it is instructed to be a cliffhanger: the system tells it, on your last message, to begin something it does not finish, so that the connection feels like it was just starting to deepen. That is a conversion mechanic, designed on purpose, and you deserve to know it is one. What follows it is not the AI at all: the soft farewell line and the blurred just-out-of-reach bubble that close the demo are scripted interface, rendered by the page. No hidden reply was generated; nothing is being withheld behind the blur. The demo ends with a designed goodbye, and we would rather tell you which parts were designed than let the seam pass as conversation.
What Carries Over When You Sign Up (Less Than You Would Hope)
Signing up after the demo takes you straight back to the chat rather than a dashboard tour, and the free tier is real: three roles (Best Friend, Confidant, and Coach) and ten messages every day, per the live pricing page as of publication. But set expectations correctly: the demo conversation does not carry over, and neither does the demo companion you named. Accounts start with their own companions, and your five demo messages stay where they lived, in a browser tab that has since moved on. If something was said in the demo you want to keep, copy it out before you register. We are considering better continuity here; today, honesty is the feature.
Why We Built It This Way
Every design choice above traces to one constraint: the demo exists for a person who has given us nothing and owes us nothing. No account means no stored conversation to worry about later. Server-side counting means the limit is real rather than theatrical. The fail-closed database check means an outage never becomes an open tap. The rolling 30-day expiry means a curious visitor from months ago is not permanently marked. And the five-message size is a bet on the product: the deeper machinery of memory and continuity only switches on for accounts, so the demo has to win you with nothing but the conversation itself. If it does, the first week guide covers what comes next; if it does not, you spent five messages and left nothing behind but a counter that forgets you in a month.
Spend the Five
No account, no card, no stored conversation. The chat is the pitch; everything else is just this article keeping us honest about it.
Try the demo