Vexo review

Vexo is a hosted product analytics service with a client library for React Native and web apps. You add its client to an application; it records app behavior and events, sends them to Vexo’s servers, and presents the resulting metrics in a web dashboard. It is not described as a self-hosted server or a database you operate.

The service sits alongside your application code to help product and engineering teams inspect user activity. The vendor lists application overview metrics, session replays, heatmaps, custom events and custom dashboards. Out-of-the-box data includes active users, session time, drop-off rate, popular screens and paths, version adoption, and user country. Vexo says its SDK also records taps, screen changes, network requests and errors; each recorded event counts toward monthly usage. That makes it useful for behavior analysis without manually defining every interaction, while custom events cover business-specific actions. It is an analytics layer, not a replacement for application logging or an operational monitoring system.

The vendor’s integration flow is account signup, obtaining an app API key, installing the client package called vexo-analytics, then initializing the library with one line of code. The homepage positions it for web and mobile, specifically React Native and web apps. It also describes custom events for tracking application-specific actions.

The homepage labels the installation step “CLI,” but describes adding the client with a preferred package manager; it does not give a command-line workflow. The vendor does not publish an API protocol or name programming-language-specific SDKs on the homepage. Confirm supported languages, SDK versions, platform compatibility and event controls in Vexo’s documentation before choosing an integration. A Reddit launch-thread reply said the native module worked with Expo’s custom development client, not Expo Go, and discussed React Navigation and planned Expo Router support at that time. Treat that as a compatibility question to verify against current docs, not as a current support guarantee.

The free Try it out plan costs $0 and includes up to 500K events per month, 1,000 session replays, heatmaps and two seats. The vendor lists 60-day retention for sessions, replays and events on free, with aggregated metrics kept for 13 months. This is enough to evaluate the product or cover a small app, but event volume and replay retention are the first limits to check.

Premium is usage-billed monthly, with the pricing page estimating $15 for 1M events per month. The first 500K events are free; additional event usage starts at $30 per million and scales down to $12 per million at higher volume. Premium includes two seats and 1,000 replays; additional replays cost $3 per 1,000, and extra seats cost $4.90 each per month. Paid retention is 24 months. Enterprise has custom pricing, supports up to 1+ billion events, includes 10 seats, and offers onboarding and custom configuration. Extra retention for three, four or five years is available as an add-on, but its price is not published. The pricing page lists monthly billing and no annual option.

Vexo’s homepage says it stores captured data on its servers, so the described deployment is vendor-hosted. The vendor does not publish an open-source license or advertise a self-hosting option; teams needing either should ask Vexo before adopting it. The homepage also does not describe a data-export process, supported formats or an API for extracting event history. Ask the vendor how to export raw events, replay data and aggregated metrics, and whether exports remain available after cancellation.

Migration would involve replacing the client integration and rebuilding any dashboards or custom-event reporting in another analytics service. The event types Vexo captures—including taps, screen changes, network requests, errors and custom events—give teams a starting point for mapping their tracking plan elsewhere, but do not establish that the data itself is portable. Teams with compliance or exit requirements should confirm ownership, export scope, deletion timing and any migration assistance in writing.

Vexo says it processes events including taps, screen changes, network requests, errors and custom events; since SDK 1.10, performance samples and console messages are also sent by default. Every event counts toward the monthly total. The vendor says teams can turn event types off or sample them in App Settings, so review defaults and usage before rolling out widely. Replays and seats also have paid overages, and the free plan has shorter retention than paid plans.

The vendor says data is securely stored on its servers, but does not publish security certifications, an uptime SLA, rate limits or detailed reliability commitments on the homepage. Ask about these, event delivery behavior during network failures, deletion controls and data residency before relying on Vexo for a regulated or business-critical workflow. In a Reddit launch thread, a user asked about Expo compatibility and another asked about performance impact; the available replies discuss Expo’s custom development client, not performance measurements. Verify current Expo support and profile overhead in your own app before production rollout.