Scope Request is a feature-request board, a public roadmap and a changelog, that you host yourself. One install, one database, and the changelog entry you publish is the thing that closes the posts and tells the people who voted.
It exists because the alternatives charge by the person and keep your customers’ accounts on their servers. Here the people voting on your board are rows in your database, and the licence covers the installation however many of them there are.
One install, as many boards as you need
A product is a thing you take requests about. It has its own hostname, its own branding, its own staff and its own statuses, and the hostname is what decides which product a visitor is looking at. So several products on one installation really are several separate boards, not one board with a filter on it. Staff on one cannot see another’s queue.
Several boards per product, for example Feature requests, Integrations and Bugs, each with its own settings and sort order
Board visibility: public, signed-in members only, paying customers only by plan code, or staff only
Categories per board, with a colour, which the person posting has to choose from
Custom fields per board, such as a product version or a hosting plan, each required or optional and public or staff-only
Your own logo, brand colour and custom CSS per product, with the brand colour mixed through the whole palette rather than painted on one button
Board rules that have to be accepted before a first post
British English and Spanish interface files, with a language tag per post and emails sent in the member’s own language
The duplicate that never gets posted
The single most useful thing on the board is the search that runs while the title is being typed. After three characters it shows the closest existing posts with a vote button on each, so the commonest outcome of somebody starting to type an idea is a vote on the idea that is already there.
One idea with forty-one votes tells you more than four copies with ten each, and it leaves nothing for a member of staff to merge by hand.
Moderation you can actually run in public
The free licence has the whole moderation system, not a sample of it: the queue, the trust thresholds and the audit log. Only the AI suggestions are held back.
What the licences cost
Free, £0. One product, one board, fifty ideas. The whole moderation queue, trust system and audit log. Roadmap and changelog. Our name in the footer, documentation rather than support, and no connectors, API or widget. It is for finding out whether your customers will use a board at all before you spend anything on one.
£199 a year, per install. Unlimited boards and unlimited ideas, custom fields, private boards, the REST API with hashed keys, webhooks and chat alerts to Slack, Teams or Telegram, the WordPress connector, CSV import and export, reports and the prioritisation view, your own branding, and support for the year.
£499 a year, per install. Everything above plus unlimited products on one install each on its own hostname, single sign-on from your own application, customer context beside every voter, white labelling throughout, the embeddable widget and AI triage.
A year buys every update released during it, applied from the admin screens, and support on the two paid licences. Havenswift Hosting Ltd is not registered for VAT, so there is nothing to add to either figure.
How it differs from the usual arrangement
No per-seat and no per-user price. The licence covers the installation. A board that succeeds does not cost more than one nobody uses.
Your customers stay in your database. Members arrive from your own application through a signed hand-off rather than registering with a third party, so there is no second set of accounts and no second privacy policy to explain.
The free tier has the whole moderation system. Most of this category holds back the parts that make a public board survivable and sells them as the reason to upgrade.
Several products on one licence. An agency running boards for clients does not buy a licence per client.
It is a file you install. If we stopped publishing it tomorrow, the board would carry on running.
