Client feedback,pinned to the page.
Clients draw on your live site and leave a note. Each note stays attached to the element it was drawn on, and lands in an inbox you host yourself. Open source, no monthly bill.
The round button in the corner is SitePing, live on this page. Pin a note on anything, or click the dots.
From their screen to your inbox, and back.
Four steps, and not one of them is an email with a screenshot attached.
Step 1: Your client draws on the page
A button sits in the corner of the live site. They draw a box around what's wrong, pick a type and write a line. No login, no account.
Step 2: The note stays on its element
Each annotation records a CSS selector, an XPath, the text and the structure around it. When the layout changes, every match is scored and the best one wins.
Step 3: It lands in your inbox
With a capture of the area they circled and, if you turn on diagnostics, the last console errors and failed requests. Slack, Discord or your own webhook tells the team.
Step 4: You close the loop
Move through notes with j and k, answer in the thread, set one of four statuses. Synced to GitHub or GitLab, resolving a note closes its issue.
Step 1 of 4: Your client draws on the page
Three steps to the first note.
Install two packages, let the CLI write the Prisma schema and the API route, then start the widget.
- 1
Install
Terminal$ npm install @siteping/widget @siteping/adapter-prismaThe widget, and the adapter that talks to your database.
- 2
Scaffold
Terminal$ npx @siteping/cli init ✓ Prisma schema updated ✓ API route generatedAdds the Prisma models and generates the API route.
- 3
Start the widget
app.tsimport { initSiteping } from '@siteping/widget' initSiteping({ endpoint: '/api/siteping', projectName: 'my-project', })Your clients can now draw on the site.
The widget works with any framework, or none.
- Next.js
- React
- Vue
- Svelte
- Astro
- Nuxt
- Remix
- Express
- Hono
- JavaScript
The details that make it hold up.
Built for the sites you hand over, and for the clients who review them.
Self-hosted
Feedback goes to your own database through Prisma or Drizzle. No vendor in the middle, no monthly fee.
Phones and tablets
Clients tap an element to comment. On a phone, the form and the panel become bottom sheets, and the form stays above the keyboard.
9 languages built in
English, French, German, Spanish, Italian, Portuguese, Russian, Japanese and Korean, in the widget and the inbox.
registerLocale(code, translations)Keyboard-first accessibility
Designed for WCAG 2.1 AA and checked with axe on every change, in light and dark. Clients can annotate without a mouse: Tab to the element, press Enter.
Access and reviewer mode
An API key or your own login. Read-only mode keeps clients to commenting and replying, and reviewer emails stay blanked by default.
readOnly: trueIsolated in Shadow DOM
The widget's CSS never leaks into your site, and your site's CSS never breaks the widget.
Light on the page
About 51 kB gzipped on first load. The panel, screenshot capture and other locales load when they're needed, and CI fails any change that outgrows the budget.
Typed and tested
Written in TypeScript, so every option shows up in your editor with its type. Covered by more than 4,400 tests.
Open source, MIT
Read it, fork it, change it. No account, no vendor key, no signup.
Next to the hosted tools.
Why pay $39–42 a month for feedback you can self-host for free?
| Feature | SitePing | Marker.io | BugHerd | Userback |
|---|---|---|---|---|
| Runs on your infrastructure | Yes | No | No | No |
| Open source | MIT | Browser SDK only | No | Browser SDK only |
| Entry price | Free | $39/mo billed yearly | $42/mo billed yearly | Free plan, $39/mo billed yearly |
| Hosted for you | You run it | Yes | Yes | Yes |
Entry paid plans as listed on marker.io ($59 billed monthly, 3 members), bugherd.com ($50 monthly, 5 members) and userback.io ($49 monthly; the free plan has 2 seats), checked on 2026-10-30. The browser SDKs are MIT on npm; the services behind them are not. Vercel Comments is left out: it is free on every Vercel plan, but every reviewer needs a Vercel account.
Questions, answered.
Something missing? Ask on GitHub.
What databases are supported?
Any database supported by Prisma — PostgreSQL, MySQL, SQLite, MongoDB, CockroachDB, and more — or, with the Drizzle adapter, PostgreSQL and Turso / libSQL.
Does it work with frameworks other than Next.js?
The widget is framework-agnostic — it works with React, Vue, Svelte, Astro, or vanilla JavaScript. The CLI currently scaffolds Next.js API routes, but the server handler (@siteping/server) works with any framework that handles standard Request/Response — Hono, Express, Remix, SvelteKit and more.
What happens when the page layout changes?
Each annotation records several signals for the element it was drawn on — a CSS selector, an XPath, its text and the text around it, a structural fingerprint, and an optional data-feedback-anchor key you set. On reload, every element any of them matches is scored against all the signals, and the best match wins; a match it is unsure of is drawn as approximate. The rectangle is stored as percentages of that element, so it follows responsive layouts.
Is there a dashboard to view feedback?
Yes — install @siteping/dashboard and drop the <SitepingInbox /> React component into your admin page. It is a Linear-style triage inbox with j/k keyboard shortcuts, four statuses, and the client's annotation re-drawn on the screenshot. See it working in the demo inbox.
How big is the widget bundle?
About 51 kB gzipped on first load — the ESM entry and the chunk it imports, everything the browser fetches before the widget runs. The feedback panel (about 21 kB), screenshot capture, and non-English locales load on demand on top of that. CI fails any change that outgrows these budgets.
What about the GDPR?
SitePing stores feedback in your own database, and sends it nowhere else unless you turn that on: webhooks (Slack, Discord, your endpoints), GitHub or GitLab issue sync, a screenshot bucket you choose. Compliance itself — a lawful basis, retention, telling reviewers what you collect — is up to you as the site operator; a library cannot be GDPR-compliant on its own.
Can I customize the widget appearance?
Yes — accent color, position (bottom-right or bottom-left), theme (light, dark, auto), and 9 built-in locales (English, French, German, Spanish, Italian, Portuguese, Russian, Japanese, Korean) plus registerLocale for your own. Try every option live on the demo.
Is it accessible?
The widget and the inbox are designed for WCAG 2.1 AA, and every change runs an automated axe check of both, in light and dark themes, with no exclusions. The full flow works from the keyboard, including drawing an annotation: Tab to the element, press Enter. Actions are announced to screen readers.
How is reviewers' data handled?
Feedback lives in your own database — SitePing is self-hosted. The API blanks reviewer emails on unauthenticated reads by default, and elements marked data-siteping-ignore="true" are masked out of screenshots.
Do I need to create an account?
No. SitePing is an npm package you install and configure. No SitePing account, no vendor key, no signup. It runs on your infrastructure.