Customer feedback operating system
Ship what your customers actually asked for
Feedback boards, roadmaps, release notes, and status pages in one workspace — so the request, the decision, and the announcement stay attached to each other.
- Free plan, no card
- Live in five minutes
- Passwordless sign-in
- Sign-in
- Passwordless
- Codes and passkeys. No password store.
- API
- 14 scopes
- Versioned REST, per-key permissions.
- AI
- 9 MCP tools
- Claude reads your workspace directly.
- Hosting
- AWS
- TLS 1.3 in transit, AES-256 at rest.
How it works
One loop, closed
Most feedback dies in the gap between where it arrives and where the work is planned. SignlOS keeps the request, the decision, and the announcement attached to each other.
- 01
Capture
Customers post ideas and bugs and vote on what matters. Every vote carries the person who cast it, so eight votes from your largest accounts never look like eight votes from trials.
Feedback boards → - 02
Decide
Promote a post to a roadmap item. The item keeps a link back to every post that fed it — the requester list travels with the work instead of living in someone's spreadsheet.
Roadmaps → - 03
Announce
Publish a release note. Everyone who voted for a linked post is told automatically. Nobody maintains a mailing list, and nobody gets forgotten.
Release notes → - 04
Stay up
When something breaks, the status page answers 'is it you or me?' before the ticket is written. Component health, incident timeline, your own domain.
Status pages →
The platform
Seven modules, one workspace
Buy them separately from four vendors and you own four integrations. Here they already know about each other.
Feedback boards
A public or private board where customers post ideas and bugs, vote on what matters, and discuss the details. Duplicates merge, votes carry across, and every post keeps its requester list.
Learn more →Roadmaps
Group work into Planned, In progress, and Shipped. Each roadmap item stays linked to the feedback posts that asked for it, so the people who requested it get told when it moves.
Learn more →Release notes
A changelog with an editor, categories, and a public feed. Publishing notifies everyone who voted for the linked posts — the loop from request to announcement closes itself.
Learn more →Status pages
A hosted status page with per-component health, incident timelines, and operator notices. Serve it from your own domain and point customers there instead of your inbox.
Learn more →Knowledge base
Searchable help articles that deflect the questions your team answers twice a week. Lives on the same portal as the boards, so customers never have to find a second site.
Learn more →Forms & surveys
When an open board is too open. Ask specific questions, route the answers to the right board, and keep the respondent attached to the post that results.
Learn more →Widgets
Drop-in embeds for the board, roadmap, and changelog. The feedback arrives with the context of the screen the user was on when they wrote it.
Learn more →New
MCP server & REST API
Point Claude at your workspace and ask what four hundred posts add up to. Same scoped key as the REST API, same permissions, no second credential.
Connect an assistant →Model Context Protocol
Ask your feedback a question
Reading four hundred posts is a job for a machine. SignlOS speaks MCP, the open standard for connecting AI assistants to real systems — so Claude can read your boards, votes, roadmap, and changelog and answer in English, grounded in your actual data.
- Same key, same limits
- The assistant uses your existing scoped API key. A read-only key can read and nothing else, whatever it is asked to do. Revoking the key revokes the assistant.
- 9 tools
- Search posts, read a post in full, summarise the board, get the roadmap, list releases, check status — and, with write scopes, file posts and move them.
- No second integration to run
- Streamable HTTP (stateless). One URL, one header, nothing to host.
Things people ask
- What are the top ten requests we haven't planned yet?
- Summarise what customers said about billing this quarter.
- Which shipped roadmap items have no release note?
- Draft a release note for everything we moved to Shipped.
Add it to Claude Code
claude mcp add --transport http \
signlos https://api.signlos.com/mcp \
--header "Authorization: Bearer sk_live_…"Why SignlOS
Six decisions that make the difference
Every feedback tool has boards and votes. These are the choices that change how the thing feels to run.
The loop is one product, not four
Board, roadmap, changelog, and status share a data model. Shipping a roadmap item already knows which posts it closes and which customers to tell. Stitching four tools together with webhooks gets you the same diagram and none of the guarantees.
No passwords, anywhere
Sign-in is a one-time code by email or SMS, or a passkey using Touch ID, Face ID, or a hardware security key. There is no password database to breach, no reset flow to phish, and nothing for a customer to reuse from another site.
Built for assistants, not just browsers
A REST API with 14 scopes and an MCP server on the same credential. Most tools in this category will sell you an export; this one answers questions.
Your domain, your brand
The public portal and status page serve from your own domain. Customers do not leave your brand to file a request or check whether you are down.
Priced like a tool, not a seat tax
$29 per month for unlimited boards, posts, and teammates. Per-seat pricing on a feedback tool punishes you for letting support agents read the feedback.
Honest about what it is not
There is no Jira sync, no Zapier app, and no SOC 2 certificate yet. The API and MCP server are how you bridge to what you already run, and the roadmap is public.
Weighing us against something specific? Read the comparisons — including where the other tool wins.
Pricing
Flat pricing, not a seat tax
A feedback tool priced per seat punishes you for letting your support team read the feedback. Pro is one price for the whole company.
Free
Enough to prove the loop works before you pay for it.
- 1 feedback board
- 50 posts
- 3 team members
- Public roadmap
- Public portal on signlos.com
- Passwordless sign-in and passkeys
- Changelog publishing
- Status pages
- Custom domain
- REST API and MCP
Pro
The whole loop, with no per-seat maths.
or $290/year — save 16%
- Unlimited boards, posts, and votes
- Unlimited team members
- Changelog publishing and subscribers
- Status pages with incidents and badges
- Knowledge base, forms, and widgets
- Custom domain for portal and status
- REST API and MCP server
- Prioritised email support
Enterprise
For teams with procurement, and a security questionnaire.
- Everything in Pro
- Contracted support response times
- Invoicing and purchase orders
- Security review and documentation
- Custom limits and data-handling terms
Billed through Stripe. No credit card required to start. Free plan support is by email with no response-time commitment. Pro is prioritised. Enterprise response times are set in the contract.
Questions
Frequently asked
Your customers already told you what to build
It is in a support inbox, three Slack threads, and a spreadsheet nobody has opened since March. Put it somewhere it can be counted.
No credit card required to start. $0 forever.