Platform map
Each block below says what it does, what it's for, and why doing it this way matters. Every product at the top is a configuration of what sits underneath — never a separate system.
Accounts, users, authentication — social login included.
One identity across the platform: the same person is a respondent, a community member and a dashboard user — and we know it is the same person. That is what makes data joinable at all.
The component engine. A survey, a dataset, a board, a flow, a bucket — all resources of one kind, living in a customer's space.
Add one resource and it inherits access control, activity log, API, stats, billing and flow integration for free. Competitors rewrite all of that for every feature.
Every activity is logged; every action can be invoked from UI, API, another resource, MCP, a scheduler or a flow.
An action written once works everywhere with the same rules and the same audit entry. The log is simultaneously audit, statistics and invoice.
The execution engine: background tasks, application events, intents ("what should I do now?") and plugins.
Intents let a new capability join an existing process without touching old code. The system asks; the components answer.
Roles and granular permissions on every resource.
Permissions are a property of the resource, not a system beside it. A new component type is secured on day one — nothing ships "open for now".
Scalable infrastructure under everything.
Scale is the platform's problem, not the project's. Nobody sizes a study to fit a server.
Billing engine and invoicing.
Billing is computed from the same activity log as statistics — so the invoice always matches what the customer sees in the panel.
Configurators and a library of ready solution templates.
A blueprint turns experience into product. What we learnt with one customer, the next one gets as a starting point.
System monitoring and per-resource statistics.
Every resource publishes its own stats. Customers see the health of their solution through the same mechanism we use to see the health of the platform.
The internal panel and its polish.
Every hour spent on the panel comes back as an hour not spent on support — and a customer who does things alone.