Skip to content
Free plugin · connects with a Pro API key

your board in wp-adminyour widgets in a block

Paste an API key once. Your feedback, release notes and uptime then live in the dashboard you already have open, and the widgets go on your site without a theme edit.

FeedFast for WordPressA free plugin, on the WordPress plugin directory
  1. 1Install the plugin from your WordPress dashboard.
  2. 2In FeedFast, create an API key under Settings → API keys.
  3. 3Paste it, pick your project, and drop a block where you want a widget.

WordPress 6.4+ and PHP 8.0+. GPLv2 or later.

four screensin the tab you have open

A feedback board gets ignored when it lives somewhere else. This puts it where the rest of the work already happens.

  • OverviewCurrent uptime, open incidents, the top feedback by votes and the latest changelog entry, on one screen.
  • FeedbackThe board as a WordPress list table with status, category and sort filters. Change a status, reply in public, or resolve a request and publish the release note in one step.
  • ChangelogEvery entry, and a Markdown editor for new ones: save a draft, or publish straight to your hub page, RSS feed and every embedded widget.
  • UptimeMonitors with their uptime windows, latency and last check, open incidents and their history, and scheduled maintenance with the next window called out.
  1. An outage finds you

    A dashboard widget, a coloured dot in the admin bar whose menu names the next maintenance window, and an admin notice when a monitor goes down. A Site Health entry reports the connection, the key's scope and the last successful sync.

place a widgetwithout a theme edit

The embed script is only loaded on pages that use one of these, and never in wp-admin.

  1. Search the inserter for FeedFast

    Blocks for the changelog, the uptime bars, a feedback button and a public roadmap. Drop one in, pick its options in the sidebar, and it renders the live widget.
  • A What's new badgeSite-wide, with its corner, theme and accent colour set from the settings screen.
  • Four blocksThe changelog, the uptime bars, a feedback button and a public roadmap.
  • The same four as shortcodesFor the classic editor or a page builder.
  • Three uptime sizesFull, compact bars, or a one-line badge sized for a footer. You tick which monitors appear.
  • Menu items as triggersAny navigation menu item can open the feedback form or the What's new panel.
  • Posts to your changelogA box on the post editor publishes a WordPress post as a changelog entry, converted to Markdown for you.

boring about your siteon purpose

Three decisions that matter more than any feature above.

  1. 1

    Your API key never reaches a browser

    It’s stored server side with autoloading off and used only by PHP. Public pages read the public widget payload, which needs only the project slug. Search the source of a page with every widget on: no ff_ anywhere.
  2. 2

    No page load waits on FeedFast

    FeedFast is never called while a visitor's page renders. Responses are cached in transients (uptime for a minute, feedback and changelog for five) and refreshed in the background on an interval you set, or not at all.
  3. 3

    It fails quietly

    When FeedFast is unreachable, admin screens show the last known data and say so. A read-only key hides every write control instead of offering a button that fails. Uninstalling removes its options, transients and cron events.

questionspeople ask first

WordPress is one of several ways in. See all integrations, or the docs for the REST API it uses.

Do I still need a FeedFast account?

Yes. The plugin is a client for FeedFast, not a copy of it. It reads and writes one FeedFast project through the REST API, so it needs a Pro account for the API key it connects with.

Where does my API key live?

In your WordPress database with autoloading off, used only by PHP. It never appears in page source, in an enqueued script, in a block attribute or in a REST response. Your public pages only ever carry the project slug.

Does it slow my site down?

Nothing is fetched from FeedFast during a front-end page load. Everything public comes either from the embed script your visitor's browser loads, or from data cached in WordPress ahead of time by a background refresh you control. The embed script is only enqueued on pages that use a widget, and never in wp-admin.

What happens if FeedFast is unreachable?

Admin screens fall back to the last known data and say so. Nothing white-screens and no front-end page waits on the network.

Can I give it a read-only key?

Yes, and it behaves properly: full read access with every write control hidden, rather than a button that fails when you press it.

Does it work with WP-CLI?

Yes, wp feedfast status, feedback list, changelog publish and refresh.

Is anything sent about my visitors?

No. Your visitors' browsers load the widget payload from FeedFast directly, which needs only the project slug. There is one optional setting, off by default, that passes a signed-in WordPress user's name and email to the feedback form so it can pre-fill. It never applies to logged-out visitors.

Five minutes from a fresh install to a live hub

Create a project, generate a key, paste it into WordPress. API keys come with Pro.