What's the difference between Aule and Ohai?

Because they are different products in different categories. Ohai is an AI chatbot you subscribe to and operate yourself - the model is software-at-software-prices. Aule is a managed household intelligence layer that closes loops on your behalf with per-household approval gates, a three-layer compounding memory that strengthens monthly, a nightly synthesis loop, and a backend QA loop targeting 95%+ closed-loop completion before you ever see the work. The right comparison is not Aule vs Ohai; it is the gap between an AI chatbot and a household intelligence layer. Ohai's pricing trajectory - $25 at launch, $9.99 now - is the unit-economics signal that the chatbot category cannot sustain its own promise. Aule's pricing is structurally different because the work is structurally different.

No. Ohai's defining trust failure - documented across Trustpilot, Slashdot, and App Store reviews - is the AI telling the user it completed a task when it did not. That is a category failure of the chatbot-as-household-manager model, not a feature gap that pricing fixes. Aule's architecture starts from the opposite premise: the layer closes the loop or it does not claim to have closed it. The backend QA loop catches the 5% where the layer would have hallucinated success. Per-household configurable approval gates put the household in the seat for any grocery order, any spend at or above $200, and anything the household has flagged as judgment-sensitive. The full-auto default loosens as the layer earns trust. None of that is a more expensive chatbot.

Aule closes loops end-to-end and returns receipts. Examples today include meals from a household-aware plan through Kroger or Instacart or Whole Foods delivery, service appointments from the quote calls through the booking and payment, dinner reservations, summer-camp registration, and the everyday cycle of vendor coordination that does not have a name. Travel is in final integration with our partner stack and ships at public launch. Ohai's surface stops at extract, organize, and remind: the user still does the work. The architectural difference is between a chatbot that prepares the work and a layer that performs it.

Honest answer: there is no real Ohai data to migrate. The product surface is conversational - threads, calendar parsings, lists - and the conversational state is not the kind of household memory that compounds. What we will do during your onboarding call is rebuild the household memory layer from the actual primitives: who lives in the house, the recurring rhythms, vendor preferences, dietary patterns, kid-specific patterns, the household-specific judgment calls. That is the substrate Aule needs and Ohai does not produce. If you have specific calendar exports or notes you want carried over, your onboarding partner will incorporate them.

Two structural answers. First: the layer itself - not a human and not a chat thread - is what does the work, with a backend QA loop catching the cycles that would otherwise fail silently. The 95%+ target is engineered, not aspirational. Second: the approval gates put the household in the seat at the moments that matter. The layer cannot claim it ordered the groceries when it did not because the household confirmed the order. The layer cannot claim it booked the appointment when it did not because the household saw the booking confirmation. Confidence is built from confirmed, receipted closes - not from chat-thread assertions.

Yes, because Aule's human team is not the product. The layer is the product. Human operations show up where the layer escalates - sensitive moments, judgment calls, the edge cases the household has flagged. The household's primary relationship is with the layer, which holds the memory and closes the loops; the operations partner is a real person on your account at the layer above, not a queue. Ohai's 10% human tier was structurally positioned as a fallback for what the AI could not handle, and that is also where users encountered the failure. Aule inverts the question: the layer handles the work, the human handles the escalation.

There is no entry-level Aule. The Founding Charter at $299/mo or $2,999/yr is one consumer tier; it is what the work costs. Bespoke at $50,000 and up is by inquiry, for households with concierge-level requirements. We did not build a chatbot tier because the chatbot category is structurally racing to the bottom and the work the household needs is not chatbot work. If Aule is not the right shape for you today, Cozi or Ohai or any of the other apps in their category will give you a calendar and a list at app-store prices.