Skip to main content

Tally alternative

Tally Alternative for Website Feedback

Looking for a Tally alternative for website feedback? FeedBlox is a feedback widget with bug reports and console logs - not a general form builder. Tally excels at fast form creation when surveys are the job.

Teams searching for a Tally alternative for product feedback usually want an always-on launcher with dev context - not another form URL to maintain.

Choose FeedBlox when you want lightweight live-site feedback and bug reports with developer context, not a heavy analytics or roadmap platform.

Comparison notes as of May 2026. Verify Tally on Tally before you buy either tool.

Honest Comparison

Seven dimensions for teams choosing between form embeds and capture-first feedback. We include rows where Tally is the better fit.

Comparison by topic (one card per row).

Primary job

FeedBlox
Product feedback and bug capture on your live site
Tally
Free form builder for surveys and data collection

Developer context

FeedBlox
Console, network, JS errors, repro summary on every plan
Tally
Custom fields you design; no automatic client debug bundle

Embed model

FeedBlox
One script tag; launcher on every page
Tally
Per-form embed or link; you place each form where needed

Inbox

FeedBlox
Per-site inbox with sentiment and triage
Tally
Form responses in Tally dashboard or integrations

Speed to submit

FeedBlox
Rating plus optional comment in seconds
Tally
Depends on form length you configure

Pricing shape

FeedBlox
Free tier for widget capture
Tally
Generous free forms; paid for advanced features (see tally.so/pricing)

Best for

FeedBlox
Ongoing feedback and production bug reports
Tally
Quick surveys, waitlists, and lightweight forms

When to Choose Tally

Choose Tally if you need flexible forms quickly - waitlists, intake, quizzes - and you will wire responses to your own workflow.

  • You spin up new forms often for marketing or ops
  • Form design flexibility matters more than dev context bundles
  • You already route Tally responses to Slack or spreadsheets
  • Bug capture is handled elsewhere in your stack

When to Choose FeedBlox

Choose FeedBlox when you want lightweight live-site feedback and bug reports with developer context, not a heavy analytics or roadmap platform.

  • You want one always-on feedback widget instead of many form embeds
  • Console logs should attach when users report bugs
  • Product and support triage from one inbox with sentiment
  • You ship a SaaS app and need capture on production, not only marketing pages

Replacing a Feedback Form Embed

You embedded a Tally form in the footer for feedback. FeedBlox on the same site:

  • Shows a launcher on every page, not only the footer
  • Captures sentiment before the comment
  • Attaches console and network context on bug reports
  • Groups all submissions in one inbox per site

Tally is excellent for forms. FeedBlox is built for product feedback loops with engineering context.

See how FeedBlox collects user feedback on your live site.

Use Tally for one-off forms. Use FeedBlox for always-on website feedback and bug capture with console logs.

Start Free forever: 3 sites, 150 reports/month, no credit card..

Try the inbox and debug bundle on your own site

New accounts get Pro free for your first month: unlimited reports, screenshots, recordings, webhooks, and collaborators. No credit card. After the trial, Free forever: 3 sites, 150 reports/month, no credit card.

Start Free

No credit card required