Before a language model learns from your data, someone has to label it well; Argilla gives AI engineers and domain experts a shared workspace to label, review, and refine the datasets that fine-tune language models and train NLP pipelines. You build each dataset from the Python SDK, mixing text, chat, and image fields with the exact questions your task needs: single-label classification for intent detection, span questions for named entities, ratings for response quality, rankings for preference tuning, or free text for corrections. Annotators then work through records in a focused labeling interface where model predictions already sit attached as suggestions, turning most reviews into a fast confirm-or-correct decision instead of a blank-page exercise. Full-text search, metadata filters, and status filters slice a hundred thousand records down to the ones needing attention, while vector-based semantic search finds lookalike examples, near-duplicates, and the disagreement hotspots where guidelines need sharpening. Dataset owners watch completion progress, manage who has responded to what, and split work across workspaces with owner, admin, and annotator roles for each team or client. Finished datasets export with responses, suggestions, and metadata intact, locally or straight to the Hugging Face Hub, ready for fine-tuning and evaluation runs. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Before any AI model reads a single customer message, Obsei has already stripped out the names, email addresses, card numbers, and ID numbers hiding inside it. Obsei pulls in what customers are saying from App Store and Google Play reviews, Zendesk, Freshdesk, and Intercom tickets, GitHub issues, surveys, YouTube comments, Bluesky, RSS feeds, SQL databases, and even Gong call transcripts. Every record is pseudonymised on the way in and stored in an encrypted database that never phones home. Then the labelling starts: sentiment, intent, language, and your own custom questions, each answered with a confidence score by a zero-shot classifier running locally on your machine, or by an LLM you choose through your own keys. Answers the model is unsure about are escalated to a stronger model or queued for a human instead of being silently wrong. Related complaints roll up into stable themes with week-by-week trends, and anything mentioned by fewer than five people stays hidden, so individuals cannot be picked out of a chart. When a theme spikes, alerts and digests land in Slack, and individual findings can be routed straight into Jira, Linear, or GitHub issues. Your analysts browse it all in the built-in Studio, and your AI agents can ask questions over MCP and get cited, redacted evidence back, with any action they propose waiting for your approval. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

In-app, website, link, and email surveys feed one open-source experience management platform: Formbricks. Its distinguishing strength is targeted in-app research: a JavaScript SDK triggers surveys on user events and attributes, with segmentation rules like "power users who have not seen a survey in 10 days," so questions reach the right cohort at the right moment instead of a mass email blast. The no-code editor offers 20+ question types including NPS, CSAT, CES, matrix, ranking, and file upload, with skip logic, conditional branching, best-practice templates, and full brand theming. Responses feed built-in analytics with summaries and CSV/JSON export, and integrations push data to Slack, Notion, Google Sheets, Airtable, Zapier, and n8n, with webhooks and an open API on every tier. Because self-hosted surveys load from your own domain rather than a blacklisted third-party script host, ad blockers do not suppress them - in-app surveys reach users that Hotjar-style tools silently miss, which measurably raises response rates. Self-hosting also removes the third-party sub-processor from your privacy policy entirely: survey responses often contain PII, and keeping them on your own server matters for GDPR-sensitive and regulated industries. The Community Edition has no response caps or tier-gated features, so core functionality and your data stay accessible regardless of any subscription. Next.js on PostgreSQL, AGPLv3.

Typeform's conversational format, self-hosted: HeyForm is the open-source form builder that presents one question at a time. Forms present one question at a time, which measurably improves completion rates compared to long static pages. It supports 40+ field types, from text, email, and phone inputs to picture choices, date pickers, star ratings, signatures, and file uploads. Conditional logic shows or hides questions based on earlier answers, routes respondents to different endings, and redirects to URLs, so a single form can serve multiple flows. Completed submissions land in a results dashboard with drop-off and completion analytics, and connect outward through webhooks or integrations with Zapier, Make, Google Sheets, Notion, Airtable, and Slack. Theming covers fonts, colors, backgrounds, and custom CSS, so embedded forms look native to your site rather than like a third-party widget; the JavaScript embed library renders them inline, as popups, or full-page, with shareable standalone links as the default. Team workspaces and projects with member management let multiple teams share one instance without mixing data. Self-hosting removes per-response pricing entirely - unlimited forms and submissions for flat hosting cost - and keeps lead data, feedback, and quiz answers in your own MongoDB, simplifying GDPR compliance. The stack is a NestJS server and React webapp backed by MongoDB and KeyDB, distributed under GPLv3 as a Docker image.

Feature requests, bug reports, upvotes, and a public roadmap: Astuto (Ruby on Rails backend, React frontend) gives users a Canny-style feedback portal so product decisions rest on visible demand rather than the loudest voice in the room. Feedback organizes into as many boards as you want (features, bugs, integrations), each post carrying a custom status you define - "planned," "in progress," "shipped," or whatever matches your process - and those statuses feed a public roadmap view showing users what is actually being worked on. Participation friction is adjustable at both ends: sign-in works with plain email or any OAuth2 provider, anonymous feedback can be enabled for unregistered users, and a moderation queue lets you approve posts before they appear when spam is a concern. Integration hooks are practical rather than sprawling - webhooks fire on events to connect Jira, Trello, or Slack, and a REST API manages the whole feedback space programmatically. Brand customization, an invitation system, private-site settings, and recap emails for administrators complete a deliberately minimal tool: it collects, organizes, and prioritizes feedback well, for free, forever.