AI onboarding and customer success agent for SaaSA specialistfor every user.

Stiro is an AI onboarding and customer success agent for SaaS and web apps: it lives inside your product and does the work instead of explaining it. You add one script tag, and your users can ask for what they want in plain words. They can type or speak. Stiro clicks, types and navigates your real interface to do it while they watch, or points out where something is, and hands back anything that sends, spends or deletes for them to confirm.

It does the in-app part of customer success for every user, not just your largest accounts: getting set up, the “how do I” requests and finding the features that matter, done in your product while they watch. Account planning, renewals and relationships stay with your team, which spends less time on routine questions. Teams often call this digital or tech-touch customer success.

A tour shows people where to click, and a chatbot tells them how. Stiro does the steps for them, in your live product. There are no flows to record or maintain, so it keeps working as your interface changes.

Copilot frameworks need your team to write and maintain code for every action the assistant can take, and to keep it in step with your product. Stiro works through the interface you already have, so there is nothing to wire up, and it can use new features as soon as they ship.

No. Paste one script tag and it works with the interface you already have. There are no tours to record and no flows to maintain, and it keeps up as your product changes.

Yes. On paid plans you choose its colours for light and dark mode, its font, how rounded it is, its cursor (Stiro’s mark, an arrow, a dot or your own image) and the name your users see, and the “Powered by Stiro” badge goes away. On every plan you can tell it about each page and signed-in user with one attribute, choose where its launcher shows, and set daily limits per user.

It stops and says why. A signed-in user can then message your team from the same panel, with what they asked and why it stopped already attached. Your team replies from the dashboard and the answer shows up in your user’s panel. Stiro reuses those answers: the next time someone asks something similar, it starts from what your team said. Already on Intercom, Zendesk or another helpdesk? One line hands the request to it instead.

It only acts on what your user asked for, with the permissions they already have in your app. It is built to hand anything that sends, spends or deletes back to them to confirm, and they can stop it at any moment. AI can still get things wrong, so keep your app’s own confirmations and permissions in place.

It only runs in apps whose owners installed it, on the domains they list. It does not browse or scrape other websites, sign in as anyone, solve CAPTCHAs or get around access controls. It never types passwords or card numbers, and it cannot do anything your user could not do themselves.

What it needs to carry out the request: the request itself and the page your user is on, including what is on screen and in form fields. Values of password, card and ID fields it recognises never leave the browser. The AI providers we use never train on it, and nothing learned from your app is used for anyone else. Your dashboard lists each request with the values it filled in replaced by placeholders, such as “invite {email} as {role}”. Our Data Use page has the details.

Any web app: React, Vue, Svelte, Angular, Rails, Phoenix LiveView or plain HTML. If it runs in a browser, Stiro can work in it.

It loads asynchronously after your page and stays out of the way until a user asks for something.

Yes. Each site’s key is tied to the domains you list. Add your signed-in user’s id to the tag and each user gets at most 50 runs a day, a limit you can change. Sign the id on your server with your site secret, one line of code, and nobody can make up users with a copied key; you can accept only signed ids. Every plan stops at its monthly tasks, and you can switch it off for a site at any time.