This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
aside
Onboarding and support that act through your app's code
aside is a chat copilot inside your web app. It walks new users through setup and answers their questions from your docs, acting through the actions your app registers: your own code fills the forms, and you decide what waits for a click.
What got me started: in-app copilots answer questions, and then the user still has to go and do the thing. Read the answer, find the screen, fill the form. I wanted a copilot that does it for them.
My first two versions let the model explore the page and decide where to click. Both clicked the wrong thing often enough that I wouldn't demo either of them. So I flipped it around. Your page calls aside.register() with the actions it offers: each has a name, a description and an input schema for the model to choose with, and a handler that stays in your page. The model never sees your markup or picks where to click. When a user asks for something, aside picks the action and its arguments, and your own handler runs it, with your validation and your permissions. Fields fill in where the user can see them, and you decide what waits for their click.
Onboarding is built from the same pieces. You write a flow as a list of your actions, each with the question to ask before it. The user starts it from the panel, aside asks one thing at a time, and each answer lands in the right field, on the right screen. Nobody has to press save or say "done". aside's own dashboard onboards you this way: tell it your agent's name, language, greeting and button in one sentence, and it fills in every form.
For support, it answers from the docs you upload, and flags the conversation for a person when it should.
The model calls in the video are live, nothing scripted. Kestrel is a demo invoicing app I built for the launch, not a customer.
You get 25 free conversations to try it on your own app, and plans start at €49 a month. I'd love to hear what you'd have it onboard your users through first.
About aside on Product Hunt
“Onboarding and support that act through your app's code”
aside was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #159 on the daily leaderboard. aside is a chat copilot inside your web app. It walks new users through setup and answers their questions from your docs, acting through the actions your app registers: your own code fills the forms, and you decide what waits for a click.
On the analytics side, aside competes within SaaS, Developer Tools and Artificial Intelligence — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how aside performed against the three products that launched closest to it on the same day.
Who hunted aside?
aside was hunted by Ricardo Morato. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of aside including community comment highlights and product details, visit the product overview.
Ricardo Morato
Hi Product Hunt, I'm Ricardo, and I make aside.
What got me started: in-app copilots answer questions, and then the user still has to go and do the thing. Read the answer, find the screen, fill the form. I wanted a copilot that does it for them.
My first two versions let the model explore the page and decide where to click. Both clicked the wrong thing often enough that I wouldn't demo either of them. So I flipped it around. Your page calls aside.register() with the actions it offers: each has a name, a description and an input schema for the model to choose with, and a handler that stays in your page. The model never sees your markup or picks where to click. When a user asks for something, aside picks the action and its arguments, and your own handler runs it, with your validation and your permissions. Fields fill in where the user can see them, and you decide what waits for their click.
Onboarding is built from the same pieces. You write a flow as a list of your actions, each with the question to ask before it. The user starts it from the panel, aside asks one thing at a time, and each answer lands in the right field, on the right screen. Nobody has to press save or say "done". aside's own dashboard onboards you this way: tell it your agent's name, language, greeting and button in one sentence, and it fills in every form.
For support, it answers from the docs you upload, and flags the conversation for a person when it should.
The model calls in the video are live, nothing scripted. Kestrel is a demo invoicing app I built for the launch, not a customer.
You get 25 free conversations to try it on your own app, and plans start at €49 a month. I'd love to hear what you'd have it onboard your users through first.