Enterprise, API & white label
Three ways in, depending on how much of Surdatics you want your users to see. Below, plainly, is what a white-label partner receives and what stays with us — including the one thing that cannot move, and why that is in your interest rather than ours.
Create studies, pull responses and reports, and receive webhooks on response, approval and dataset sale. Field teams connect over OpenRosa with ODK Collect or KoboCollect.
Read the API docs →A public embed key, locked to an origin allowlist, renders surveys inside your pages. It is deliberately not an API key — it ships in your HTML where anyone can read it, so it is protected by origin rather than by secrecy.
Talk to us →Your brand, your domain, your users. Everything in the left column below, none of the right.
Talk to us →A university, association or agency adopts Surdatics as the research portal its members use — students and members file research through it, and every dataset carries a seal their examiners and funders can check.
Talk to us →Surdatics is multi-tenant, not installed on your servers. You get the entire surface and none of the engine — which is a deliberate design decision, not a licensing tactic.
Logo, colours, typography, custom domain and email sender. Respondents see their organisation, not ours.
Surveys render in their app or portal. Users never leave the site they started on.
Exports and shared report links carry their branding.
Their team manages their own studies, members, roles and permissions.
They set what they charge their own users. We settle with them, not with their customers.
Every dataset they collect is theirs, in open formats, at any time.
Their studies reach our verified pool. That reach is the thing they are buying — it is not something that can be handed over.
Facial liveness and uniqueness checking runs on our infrastructure. Biometric matching is not something to hand to a third party, and we would not accept it from one.
This is the one that cannot move, for a reason worth stating plainly: a seal you issue to yourself proves nothing. Verification only means something while the party operating it is not the party being verified.
Contributor payouts settle from our treasury against rails we operate and are accountable for.
Question generation, translation, bias review, theme and sentiment extraction.
Listings, licensing and resale revenue share run on the shared network.
A seal an organisation issues to itself establishes nothing. The value of a Surdatics seal is precisely that the party operating it is not the party being verified — so a dataset collected under your brand carries Verified by Surdatics, and anyone can check that fingerprint against the ledger without an account and without asking you.
That is what a university is buying when students submit coursework research through its portal, and what a funder is reading when an agency files a report. The badge is not our watermark on your product — it is the reason your users believe the numbers.
See what anyone can check →Whether that is our name, your name, or nothing at all — we will tell you honestly which of the three is possible.
