THE WEB, BETTER TOGETHER
Comment on the page, not a screenshot.
Review any page together, even when it sits behind a login.
Almost yours.
Review your details before placing the order.
Subtotal £84.00
Delivery £5.00
Can we make this field easier to spot on mobile?
Yes. I'll bring it above the fold.
Does this total match the pricing sheet we approved?
Someone ships a page. Then they become the router.
A client demo, a staging build or an internal dashboard goes live as a bare URL. It has no way to discuss it in place, so the person who built it fields screenshots, chat messages and emails, then manually reconstructs which comment belongs to which part of the page before anything gets fixed.
Existing tools stop at the loginDesign-review and bug-capture tools run the target page through their own proxy so a viewer needs no login of their own, which is exactly why they break on a staging build, an internal admin panel or a client's authenticated account.
Feedback scatters across every channelScreenshots in one chat, replies in another, a follow-up email that never quite matches the thread. Nothing points back to the exact element it's about.
The builder becomes the single point of failureEvery reaction has to pass back through the person who shipped the page before it can turn into a fix, even when the fix itself is small.
"A build last month cost me a full week, and it was pure project management, not code."
r/SiteManagement, September 2026"We shipped two versions of the same section to staging and the client asked why it looked broken."
r/SiteManagement, September 2026"By the time everyone is talking about the same element, you've already wasted a bunch of time figuring out what they're actually referring to."
r/SideProject, September 2026How it works
No proxy, no re-hosting. Alongside runs inside the browser session you're already authenticated in, so it sees exactly what you see.
01
Install the extension
Add Alongside to your browser once. No server setup, no changes to the page or app you're reviewing.
02
Activate on any page
Turn it on for a staging build, an internal dashboard or a client's logged-in environment, the same way it would work on a public page.
03
Highlight and comment
Pin a threaded comment to the exact element. Teammates and clients see it, and each other's cursors, live.
04
Reply, or ask the assistant
The page owner replies in place, or a grounded AI assistant answers routine questions using the page and the team's own docs.
Built for the pages other tools can't reach
The benefit isn't another comment box. It's getting feedback exactly where the work already lives, without asking anyone to leave the page.
No screenshot relay
Comments live on the pixel they're about, so nobody has to describe where something is before discussing what's wrong with it.
The client isn't stuck opening a ticket
A client who would never file a project-management ticket can still leave a comment in the moment they notice something.
Works exactly where you're logged in
Staging builds, internal admin tools and client accounts behave like any other page, because nothing is proxied or re-hosted.
Handles trust the way a login-gated tool has to
Reading a page behind a login raises real questions for security-conscious teams. Alongside is built around the fact that it never sees more than the page already shows the person using it.
Runs inside your sessionNothing about the underlying page is proxied or re-hosted on a new server; the extension only sees what your own login already grants.
Comments stay scoped to the pageA thread is tied to the exact element and URL it was left on, visible only to people invited into that workspace.
Admins control who can install itWorkspace owners approve which teammates and clients can activate Alongside on which pages.
This is also the honest open question in the idea itself: the extension is the only way to comment on a page behind a login, but it's also the adoption barrier, since a client who has never installed a vendor's browser extension may simply not do it. The weekend test is whether a real client will.
Priced like a team tool, not a per-comment fee
The page owner pays; the person leaving a comment never needs to.
$0 / workspace
- 1 workspace, unlimited pages
- Threaded comments and live cursors
- Up to 2 seats
$15 / seat / month
- Everything in Free
- Unlimited seats
- AI assistant grounded in the page and team docs
- Admin controls for who can install
Custom
- Multiple client workspaces
- Expanded AI usage
- Priority support for review cycles
The shift making this more urgent
More working pages are shipped by people without a software background, and more of that software lives outside formal review, which means more logged-in, feedback-starved pages every week.
New projects created daily on one large AI app-building platform, each a URL with no built-in way to collect feedback.
Of enterprise teams had already replaced a purchased tool with a custom build, and most of that outside official IT channels.
Typical entry pricing for comparable proxy-based feedback tools by seat count, the pricing band Alongside is anchored against.
Where the first customers come from
Agencies and contract shops reviewing client work, where the client is the reviewer who would never open a project-management ticket.
Five agencies, one review cycle each. Offer free use of Alongside on a client's next review cycle and track whether the client actually installs it and comments, compared with the existing screenshot-and-chat routine.
Start on one staging site. A minimal version that works on the team's own staging environment and one partner agency's client site, testing only whether a second person installs it, not the AI assistant.
Go where the pain is already discussed. Agency and freelance-adjacent communities already describe feedback scattered across email, chat and screenshots.
See the mechanism above, then take it back to the top.
Open a comment thread, watch the cursors move, and picture it on your own staging build.
Back to the top