bring it insidethe app they already use
A public page only reaches the people who go looking. The widgets put the same changelog, board and uptime inside your product: one script tag, then an attribute wherever you want something to appear.
<script src="https://feedfa.st/embed.js" data-project="your-project" defer></script>That’s the whole installation. Everything below is one more attribute.
a feedback buttonon any element
Not a fixed bubble in a corner you can’t move. Put the attribute on your own button or menu item, styled however you like, and it opens the submit form in a modal.
<button data-feedfast="feedback">
Send feedback
</button>
<!-- Any element works, styled however you like -->
<a href="#" data-feedfast="feedback">Report a bug</a>Nobody has to make an account. The modal asks for a category, a title and, optionally, an email. If they’re signed in to your app, pass their identity and they type nothing at all. Need a button to start from? The feedback button gallery has 27 designs to paste, and the feedback form builder swaps our modal for your own markup.
release notesinside your product
Cards with excerpts for a dedicated What’s new page, or a compact list for a settings sidebar or footer. Both read from the same entries as your public page and RSS feed.
<div data-feedfast="changelog"
data-variant="card"
data-limit="2"></div><div data-feedfast="changelog"
data-variant="inline"
data-limit="4"></div>your statusin your own footer
The signature bar strip, embedded. People check a footer they’re already looking at; they don’t check a status page they’ve never been told about.
<div data-feedfast="uptime" data-days="60"></div><div data-feedfast="uptime"
data-labels="none"
data-size="sm"
data-days="30"></div>No text at all: the bars link to your status page, and each one shows its day on hover. This is the one in our own footer.
a what’s new badgethat knows what they’ve read
On by default, in the corner of every page. When there’s an entry they haven’t read, an accent disc with a sparkle pulses beside “New”, the version and the latest title. Once they’ve opened it, it settles back to a quiet What’s new.
The floating badge is switched off on this page. This site runs its own in the same corner. On your site it appears by itself.
<!-- On by default. To move it: -->
<script src="https://feedfa.st/embed.js"
data-project="your-project"
data-position="bottom-left"
defer></script>
<!-- Or turn it off and open it yourself: -->
<script ... data-badge="false" defer></script>
<button onclick="Feedfast.openChangelog()">What's new</button>five dialssensible defaults
The widgets inherit your project’s accent and match the page they sit on unless you say otherwise.
data-theme
auto | light | dark
Defaults to auto, which matches the page behind the widget, light or dark. Pin it if you'd rather choose.
data-accent
#4F46E5
Overrides your project's accent for this embed. Label contrast is recalculated from it, so text on the button stays readable whatever you pick.
data-position
bottom-right | bottom-left
Where the floating badge sits. Set data-badge="false" to remove it entirely.
data-limit / data-days
5 / 90
How many changelog entries, and how many days of uptime history. Both clamp to what the plan allows rather than erroring.
data-skin
card | drawer | paper | glass | bold
The look of the feedback modal and the What's new panel: the rounded card, a full-height drawer from the badge's side, ruled paper with a serif, frosted glass, or bold ink borders. Set it on the loader for both, or on one feedback button for just that one. Every plan.
Every attribute, including the ones this page skips, is in the docs, along with the JSON payload the widgets read, so you can build your own. To see every skin and option change live before you paste anything, open the widget playground.
know who’s askingprovably
Embedded inside your app, you already know who the user is. Pass it along and they never type their name.
<script src="https://feedfa.st/embed.js"
data-project="your-project"
data-user-id="${user.id}"
data-user-name="${user.name}"
data-user-email="${user.email}"
data-user-hash="${hmac}"
defer></script>Signed, or just attributed
Unsigned identities work and are attributed. They just carry no more weight than a typed name, because anyone can edit your HTML. Sign the identity with your project secret and the post renders with a verified badge.
Why the distinction matters
A board where every name might be someone else is a board you can’t decide anything from. The badge is the difference between a claim and a fact, so FeedFast only shows it when it can prove it.
what it costsyour page
A third-party script is a liability until proven otherwise, so here is what this one actually does.
- About 12 KB gzippedOne file, no dependencies, loaded with
deferso it never blocks rendering. - No cookiesOnly localStorage: the last changelog entry read, so the badge knows what's new, and the email typed into the feedback form.
- No analytics, no fingerprintingThe script talks to one endpoint, your project's public JSON payload, and nothing else.
- Shadow DOM throughoutYour CSS can't reach in and the widget's can't leak out, on any site.
- Fails quietlyIf the payload doesn't arrive, the mount points stay empty. Your layout doesn't move and nothing lands in your console.
- No framework requiredPlain HTML, React, Vue, Rails or a static site. Call
Feedfast.mount()after a client-side route change.
beforeyou paste it
The full attribute list and the JavaScript API are in the docs.
How much does the embed script weigh?
About 12 KB gzipped, served with a five-minute edge cache and a day of stale-while-revalidate. It has no dependencies and no framework. It is one file of plain JavaScript that you load with defer, so it never blocks your page.
Will the widgets clash with my CSS?
No. Every widget renders inside a shadow root, so your styles cannot reach in and its styles cannot leak out. That is also why it looks the same on a Tailwind site and a Bootstrap one.
Do the widgets set cookies or track anyone?
No cookies at all. The only client storage is two localStorage keys: which changelog entry you last read, so the badge knows whether to show what's new, and the email you typed into the feedback form, so you don't type it twice. There is no analytics, no fingerprinting and no third-party request.
What happens if FeedFast is down?
Your page is unaffected. The script loads with defer and renders nothing until its data arrives, so a failed request leaves the mount points empty rather than breaking layout or throwing into your console.
Can I attribute feedback to the signed-in user?
Yes. Pass their id or email on the script tag and posts arrive attributed without anyone typing their name. Sign that identity with your project secret and it renders with a verified badge, so you can tell an assertion from a fact. Unsigned identities still work. They just don't get the badge.
Can I open the widgets from my own buttons?
Yes. The script exposes window.Feedfast with openFeedback, openChangelog, setBadge, close, refresh and mount. Use the data attribute for the common case and the JavaScript API when you need it from a menu item, a keyboard shortcut, or after a route change in a single-page app.
Paste one script tag and see it on your own site
Free for one project, widgets included on every plan. The badge starts working the moment you publish your first entry.