Everything for a better project.

Build: ask people
to show you.

Intentional feedback, right on your website. Use it on a prototype, a new feature or an existing project. Your project plan includes the feedback workflow; metered AI and service work use project capacity. Written feedback stays available even when your project’s shared pool is empty.

Point it out.
Or talk it through.

Mark a detail, share an idea or turn on voice feedback while you test. Astor keeps your input with the page context and helps turn it into clear tickets.

Shift + Option / Alt + FOn mobile, add ?astor to the website address.

Astor
Choose a tool to see how it works.

Your feedback

Reopen a conversation or check the feedback you have already left on this project. The Astor logo opens your project in a separate tab.

The toolbar appears on connected websites. Your project controls which tools are enabled, and Missions appears when a task is available to you.

Point to the problem.

Mark an element or an area. Comment on the page with a reviewed screenshot, or explore an idea.

Make the feedback useful.

Clarify the feedback with Astor. Choose an answer or write your own. Manual feedback stays available.

Keep the original context.

The page, visual marker, original comment and conversation stay with the feedback you submit.

A little clarification.
A clearer brief.

When context is missing, Astor asks a short follow-up question. Choose a suggested answer or write your own. Save the draft for later or continue manually.

Your original comment, conversation and page context arrive together in Inbox. Written feedback and follow-up questions stay available without a separate charge.

Example conversation
Astor

What did you expect after clicking?

Choose a suggested answer, or write your own.

Try the choices above. This example does not send feedback.

Missions: give people
a real task.

“Complete a purchase.” “Find the cancellation terms.” “Book a visit.” A mission turns a broad request for feedback into a focused journey.

  • Define the task and a successful outcome.
  • Start from an existing problem, a ticket or a new question.
  • Let testers record steps with consent, pause or report being stuck.
  • Save the tester’s result with the same improvement.
See how results support a ticket
Example mission

Reserve a studio visit

Choose a space and book a date. Finish when you can see that your visit is confirmed.

  1. 1Open the booking page
  2. 2Choose a space
  3. 3
    Submit the bookingTester reports: “I’m stuck”

A useful question for the teamDoes the confirmation clearly explain what happens next?

Illustrative result. Review recorded steps and the tester’s report before drawing a conclusion.

Live: learn from
everyday use.

Follow the pages, actions and outcomes you choose to collect. Investigate patterns that might otherwise stay invisible.

  • Review browser journeys and repeated actions.
  • Add confirmed outcomes from your application with server signals.
  • Turn a finding into an Inbox item or supporting information for a ticket.
  • Keep collection separate from feedback, with explicit activation.

Live records declared steps, not a video of private page content. One Astor installation controls feedback, Missions and Live. Live uses a temporary session in the permitted browser tab, with no visitor profiles or fingerprinting. You choose collection and retention.

Illustrative Live finding

Checkout deserves a closer look.

Checkout openedContinue clickedContinue clicked again
Observed
A repeated action with no recorded success signal.
What it might mean
The next step may be unclear, or an expected signal may be missing.
Next action
Investigate the journey. Run a mission or check the confirmed purchase outcome.
A missing signal does not, on its own, prove that a purchase failed.

One ticket.
The whole story.

Build feedback, a mission result and a Live finding can all describe the same problem. Keep them together instead of creating three separate tasks.

Inbox brings feedback and results together.

Review observations, link related items and choose what to take forward. Astor’s suggestions stay separate from what was observed.

Tickets keeps the next action clear.

Use Bug, Improvement or Idea. Clarify, review, prioritize, copy the implementation brief and verify the updated version.

A useful brief has four parts: Problem, Feedback & results, Proposed change and What to check.

Example · CheckoutImprovement

Make checkout confirmation clearer

Problem
People are unsure whether their purchase succeeded.
Feedback & results
Build: “I clicked, but nothing seemed to happen.”Mission: a tester reports being stuck after checkout.Live: repeated checkout actions, with no recorded success signal.
Proposed change
Show a clear confirmation and explain what happens next.
Acceptance criteria
A successful purchase shows confirmation. A failed purchase explains how to recover.
Review the comments, test results and recorded activity before approving the change.

Agents: help where
the problem lives.

Give Astor a concrete assignment inside the improvement. See what it reviewed, what it found and what it recommends doing next.

Investigate

Look for missing context and review the feedback, screenshots and test results saved with this ticket. Review Astor’s assessment against the original observations.

Prepare implementation brief

Turn the agreed problem and supporting feedback into a clearer handoff for your builder, with acceptance checks attached.

Follow the work

Optional automatic reviews react to new and changed tickets within a daily limit from your project’s shared pool. Progress and results stay connected to the improvement.

Bounded reviews and supported connected jobs show their total project allowance before start. Separate prepaid work budgets are planned; general cloud coding agents are not available. Follow-up questions are included. Stop the job or review its results; your team keeps the final decision.

See pricing

Start solo.
Bring the right people in.

Free includes 1 internal team member, including the project owner. Use @mentions, share the review and assign an owner. Invite external testers by email or a personal link to a testing task or Mission. They create a free tester account or sign in, then open the assigned project. The same account works across projects, without a subscription or payment details.

Pro increases capacity to ten internal people and 500 monthly units. Project permissions are included on both plans. Manage team members and testers in Users, with access limited to the projects they join.

Find your setup

Check the change.
Keep the whole story.

Approve the brief before building. Bring the updated version back and verify each acceptance criterion on the same ticket.

  1. Take the brief to your builder.Copy the agreed problem, feedback, proposed change and completion checks into your building tool.
  2. Add the updated version.Return with a preview or release reference and explain what changed.
  3. Verify the result.Check each criterion on the updated website. Close the ticket when verification passes, or request changes and try again.

Help Astor understand
your project.

Save your audience, goals, product details and constraints in Project context. Astor uses the approved context to ask more useful questions and prepare clearer work.

Each project keeps its own context. A website review proposes an update for you to check; existing approved context stays unchanged until you accept it.

Start with what you already know.

Add the details yourself, or ask Astor to learn from your published website before installing the script.

Astor shows the website review’s total allowance before starting. Its follow-up questions are included in that job. Reading and manual editing use no capacity.

Install once.
Choose what comes next.

Add your website or app, then paste Astor’s installation prompt into your builder. The unique script connects it to the right project and environment.

Activate feedback, Missions and Live from Astor without changing the script. Preview and public addresses can belong to the same project.

  1. Copy the installation prompt.Paste it into Lovable, Codex, Claude Code or your team’s building tool.
  2. Let your builder add Astor.Install the script across the pages you want to review, then publish the updated website.
  3. Check the installation.Use Verify installation to check the script and its verification code. Astor also checks pending installations hourly and emails a reminder if the website is still unverified after 24 hours. Once Verified appears, you can start testing. Live collection stays off until you activate it.

Help Astor understand your project before installation. Review what it learns from your website, or add the details yourself.

Your next improvement starts here.

Turn feedback into a clear next step.

Start freeNo card required.