Usher
An AI agent that guides your website visitors to answers, not a chatbot maze.
Useful when replacing: the chatbot your visitors close immediately
Pricing · USD
Own it
$99 once
Run it yourself or use optional managed hosting.
Hosted by us · optional
$9/mo
Cancel any month — it keeps running, because you own it. Or self-host and pay $0 forever.
$99 and it's yours as-is: MIT licensed, unlimited conversations. Point it at your URL and it starts working; add hosting, model gateway, and scheduled re-crawls for $9/mo. Want it styled into your site and tuned against your content? That's a Build Sprint. No per-resolution fees — the thing every AI support vendor is quietly moving to.
Inside Usher
The problem
Website chatbots answer questions with links to the page the visitor was already on. Visitors know this, which is why they close the widget before it loads. The information is on your site — the navigation to it is what's broken.
How Usher solves it
Give it your URL. That's the setup.
Paste your website address and Usher does the rest — it crawls the site, reads every page, follows your sitemap, pulls in linked docs, and builds its own knowledge base. No content to export, no articles to write, no intents to define, no decision tree to draw. It's answering questions about your product in minutes, and it re-crawls on a schedule so it never drifts out of date with the site.
Answers, then evidence
It answers the question directly and cites the exact page section it drew from, so the visitor can verify it — and so can you. If the site doesn't say, Usher says it doesn't know rather than improvising. Refusal is a feature, not a bug.
Knows when to stop
When a question needs a human, it routes to one with the full conversation and its cited sources attached — no 'I didn't understand that' loops, no dead ends.
Your knowledge stays yours
Runs against your own model gateway (it pairs with Vyom), so visitor conversations stay in your infrastructure and never train someone else's product — or ours.
Delivery terms — stated precisely
How Usher is delivered, what you control, and where the boundaries sit.
Source included · MIT
Run it yourself or use optional managed hosting.
Data and hosting
Deploy in your cloud or use the stated optional managed-hosting plan. Data location and operator access are agreed before production use.
Compliance boundary
Residency, controls, and regulatory requirements are implementation decisions documented in the selected plan or delivery scope.
Rented vs. owned
The rented way
the chatbot your visitors close immediately
- Metered pricing that scales with your success, not the value
- Your data sits in their database, exportable only through their API
- Prices rise once you're integrated and can't leave
- Switching is a migration project nobody will approve
The Usher way
$99 once — and then it's yours
- One price, paid once — hosting is $9/mo and optional, or $0 if you run it
- Self-host in your infrastructure, or use the optional managed plan under its stated data terms
- Source included · MIT — the exit terms are stated on this product
- Stop paying and nothing switches off. Leave with a git clone, not a support ticket
Built on
More to run your business
Usher — the questions buyers ask
Who owns the code and IP?
For a Build Sprint, the repository, deployment assets, and work-product IP described in the SOW are handed over to you. Pre-existing products retain the licence shown on their product page; hosted services remain services. We state that boundary before work starts.
What happens if a sprint misses its scope?
We finish it. Fixed price means the risk of estimation is ours, not yours — a missed scope item is completed without a new invoice. Changes you request are re-scoped explicitly, so the line between 'our miss' and 'new ask' stays honest.
How do time zones work with a pod in India?
Every engagement includes 4+ hours of overlap with US or EU working hours. Async by default — written updates, weekly clickable demos — and meetings only when they earn the slot. You'll never chase a status report.
How is our data and code kept secure?
Work happens in your repos and your infrastructure wherever possible — we hold the minimum access needed, revoked at handover. NDAs are standard on request, and everything we self-host for you runs behind your keys, not ours.
How fast can you actually start?
Scoping takes a day; most sprints start within a week of sign-off. Pods are deliberately small and senior, so your start date is confirmed in the sprint plan — not left floating.
Do we need a retainer afterwards?
No — that's the point. A sprint ends with handover docs and training. If you want us to keep maintaining what we built, that's an optional flat monthly add-on you can cancel any month, because the software keeps working without us.
Own Usher, don't rent it.
See the price, deploy on your infrastructure, keep the code. Or scope a sprint and we'll customise it and hand it over.