Eventvisor
eventvisor.org
Spec sheet
- Purpose
- Eventvisor governs, transforms, filters, and routes application logs and analytics events to multiple destinations through remote configuration, without redeployments.Read 7 Oct 2026 · eventvisor.org
- Intended users
- The repository describes Eventvisor as especially useful for medium to large product engineering organizations.Read 7 Oct 2026 · github.com
- Deployment
- Generated static JSON datafiles can be served from a user's own server, a CDN, or deployed with application code.Read 7 Oct 2026 · eventvisor.org
- Integrations
- The documentation lists Amplitude, Datadog, Google Analytics 4, Google Tag Manager, Mixpanel, New Relic, Segment, and Sentry as third-party integrations.Read 7 Oct 2026 · eventvisor.org
- Security
- The project repository links to a security policy.Read 7 Oct 2026 · github.com
- Maker
- The homepage credits Fahad Heylaal as the builder.Read 7 Oct 2026 · eventvisor.org
- Bundle size
- The homepage advertises an approximate bundle size of 8 kB.Read 7 Oct 2026 · eventvisor.org
- Conditional routing
- Destination conditions can filter which tracked events are sent to each destination.Read 7 Oct 2026 · eventvisor.org
- Custom destinations
- Destinations can include a user's own custom backend service, and users can create their own transports as modules.Read 7 Oct 2026 · eventvisor.org
- Environments and deployment
- Eventvisor generates static JSON datafiles that teams can serve from their own server or a CDN, allowing configuration deployment separately from application code.Read 7 Oct 2026 · eventvisor.org
- Event definitions
- Teams define structured events and attributes in a project, with event payloads validated against schemas.Read 7 Oct 2026 · eventvisor.org
- Event management
- Teams can define events and attributes in one project as a shared source of truth.Read 7 Oct 2026 · eventvisor.org
- Open source
- The project repository identifies Eventvisor as MIT licensed.Read 7 Oct 2026 · github.com
- Payload transforms
- Destination transforms can manipulate event payloads before they are transported.Read 7 Oct 2026 · eventvisor.org
- Project setup
- The CLI requires Node.js v20 or later, while the SDKs are described as platform agnostic.Read 7 Oct 2026 · eventvisor.org
- Requirements
- The quick start requires Node.js v20 or later for the CLI; it says Node.js is not required by the SDKs themselves.Read 7 Oct 2026 · eventvisor.org
- Routing and transforms
- Event definitions can conditionally route events to destinations and transform payloads before transport.Read 7 Oct 2026 · eventvisor.org
- Sampling
- Sampling rules can limit the percentage of tracked events sent to a destination.Read 7 Oct 2026 · eventvisor.org
- SDK support
- The quick start says the current SDK supports browser and Node.js applications, with more SDKs planned.Read 7 Oct 2026 · eventvisor.org
- Support and contributions
- The project uses GitHub Issues to track bugs and feature requests and accepts pull requests targeting its main branch.Read 7 Oct 2026 · eventvisor.org
- Supported runtimes
- The SDK documentation lists JavaScript for browser and Node.js runtimes, and says more SDKs are planned.Read 7 Oct 2026 · eventvisor.org
- Validation and testing
- Eventvisor provides runtime validation warnings for incorrect event data and supports testing definitions before deployment.Read 7 Oct 2026 · eventvisor.org
- Workflow
- The documented workflow uses a Git repository, a CI/CD pipeline to build and upload datafiles, and a CDN or custom server to serve them.Read 7 Oct 2026 · github.com
Where Specifiction places it
- Event Tracking Software#12 of 247.7