A quick pulse
Scales for satisfaction, effort and NPS. Single choice, multiple choice and yes/no for a fast answer.
Ask a question at the right moment. Collect the answer in your own stack. Open-source surveys for the web and mobile experiences you already build.
MIT licensed Free to self-host No response fees
Interactive preview · stays in this browser.
Fits the stack
you already ship.
Small questions. Better context.
A checkout just finished. A feature was used. A support conversation ended. Your app chooses when to ask; Likerts handles the answers.
Explore the question typesBuilt for your tools, too
Create and publish a survey. Collect and retrieve the answers. Give your agent access through MCP, or use the CLI and HTTP API directly.
Connect your agentScoped credentials. Typed contracts.
The same operations across all three interfaces.
Tool: usage_get
Arguments: {}
Use a scoped service credential.
See the Codex and Claude Code setup guide.Open source. All yours.
Deploy Likerts with your own PostgreSQL database. Keep your customer journeys, response data and infrastructure decisions under your control.
Explore the sourceEmbed in your app. Your team controls placement and audience; Likerts doesn't send emails or distribute survey links.
Workspace isolation, scoped access, exports, retention and deletion are part of the platform.
MIT-licensed software with no response charges. You cover your infrastructure costs and set operational limits to suit your capacity.
Likerts is survey infrastructure for developers. Define surveys through the API, MCP or CLI, then embed them in your product with an SDK. There is no drag-and-drop form builder or public survey link service.
The software is free under the MIT license, including commercial use. Likerts doesn't charge per response or require a paid plan. You pay for the servers, database and storage you use to run it.
Yes. Use the collection API directly or an SDK client with your own interface. The Web SDK also includes a renderer you can try in the live demo.
Yes. Workspaces separate data through PostgreSQL row-level security and scoped credentials. You can also run separate deployments for customers who require dedicated infrastructure.
Run locally, collect your first response, then make it yours.