What’s in the box
React Native SDK
Singleton
MicroSurvey client + <InsitoProvider> for the modal
UI. Survey rendering, persistent offline queue, screen-map
tracking, and 4 theme presets ship in the package.Flutter SDK
The same
MicroSurvey API and InsitoProvider widget as a Dart
package on pub.dev — offline queue, navigator-based screen tracking,
theming, and dark mode, all mirroring the React Native SDK 1:1.Hosted dashboard
Build surveys with the visual builder, watch NPS trend lines
update in real time, browse per-response transcripts, and wire
integrations like Slack notifications.
REST API
A full SDK endpoint set + dashboard surface. Use them directly
if you’re integrating from a platform we don’t ship an SDK for yet.
MCP server
Connect Claude Desktop, Cursor, or any MCP client to Insito. Create
surveys, publish them, and read NPS analytics in natural language.
Per-org isolation
Every project belongs to one organisation, each app’s responses count
against a monthly cap, every dashboard route is RLS-scoped.
Cross-org access returns 404 by design.
How it works
The mental model is three pieces:- Triggers are short event names your app calls (
MicroSurvey.trigger("checkout_completed")). They’re attached to surveys in the dashboard, so non-engineers can change what gets asked without shipping a new app build. - Surveys are 1–N questions of four types: NPS (0–10), rating (1–5), multiple choice, and open text.
- Responses land in the dashboard with the user’s
userId, the trigger that fired the survey, and every answer.
Pricing
Plans are response-based — each app’s submitted responses count against a monthly cap (per app). Triggers, impressions, and “no survey shown” responses don’t count. See plan limits for the full matrix.Next steps
5-minute Quickstart
Sign up, install the SDK, fire your first trigger end-to-end.
Triggers explained
The model that decides whether a survey shows.