Hey Product Hunt! I've spent the last ten years building B2B SaaS, from senior engineer to CTO. The same request followed me from product to product: customers eventually ask "can we add a custom field here?" It starts with one request. Then ten. Then each customer wants different fields. Before you know it, your team has spent months on EAV tables, dynamic form renderers, per-tenant field configs, validation rules, and a settings UI. None of that is your actual product. So I built Kopra: custom fields as a service. What it does: - Drop in a TypeScript SDK or use the REST API - Your customers get a field editor that looks native to your app (embeddable, white-label) - Each tenant can add their own fields without touching your codebase - 9 field types (string, textarea, number, boolean, date, email, url, select, multiselect) - Webhooks on every change, audit logging, usage tracking - MCP server so AI agents can manage fields too The integration is about 15 minutes: npm install @kopra-dev/sdk Build a token endpoint on your backend, initialize the SDK, call loadCustomFields(). That's it. Your customers see a field editor. You see a dashboard with usage stats. What makes it different: Nobody sells this, everyone rebuilds it. I want to find out which of those two facts matters more. My bet is that a dedicated service beats the 50th in-house reimplementation, but that's exactly what today is for. Free tier: 3 field groups, 10 tenants, 5,000 API calls per month. Enough to validate the integration before committing. I'd love honest feedback. Is this something you'd use? Would it have saved you time on a past project? What's missing? Try the live demo on the landing page (no signup needed) or check the API docs at https://api.kopra.dev/api/docs.

Kopra

Custom fields as a service for SaaS products

Custom fields as a service for SaaS products