You saw the pricing. You closed the tab. We built airys for that moment.
Support software has been pricing itself out of the customers it was supposed to help. We think a founder running their own support deserves a tool that respects their time, their budget, and their intelligence.
The problem
Every incumbent in support software was built for an enterprise that doesn't exist anymore. Bloated dashboards. Per-seat pricing. AI features tacked on as a $99/month add-on. A demo call to learn what the demo call would have told you.
The result: thousands of small SaaS teams hand-rolling their own support out of a shared inbox, because the "real" tools cost more than their server bill.
The best support tool for a small team should not require a procurement process.
What we believe
AI-first, not AI-bolted-on.
The widget, the help center, and the inbox were designed around the assumption that an AI is doing the first pass. Not as a feature flag. Not as an upsell.
Sources beat confidence.
Every answer cites the article it came from. If airys can't find a source, it doesn't guess — it asks or escalates. Confidence without grounding is the bug.
Three surfaces, one product.
Dashboard, help center, widget. They share content, branding, and analytics. We don't sell them as modules and we don't gate them by tier.
Pricing you can read in one breath.
$0, $29, $99. No seats. No "talk to sales" for a feature you already needed. If you outgrow us in a way we didn't price for, we'd rather rewrite the page than invent a tier.
How we work
Small team. Slow releases. Conservative defaults. We'd rather ship one feature that holds up than five that need a maintenance window.
We use airys on our own help center. Every question it can't answer goes into our backlog — eating our own gap analytics is the fastest way to know what's broken.
We don't train models on customer data. We don't have an enterprise tier with a separate, special privacy policy. Same product, same promises, everyone.
Where this goes
Eventually, the boundary between docs, help center, and support should disappear. Your product should answer in plain English when a customer is confused. Your team should spend less time copy-pasting and more time on the conversations that actually move the relationship forward.
That's the world we're building toward. Quietly.