Traffic in the right context
Cookie-free analytics distinguishes users, bots, internal development and customers. Filters, saved segments, sources and campaigns reveal who contributes to your traffic.
Webfly Pulse is an application by Webfly for web analytics, monitoring and security signals on your own infrastructure. Understand traffic, monitor availability and uncover problems. Multiple users and customers work in one Pulse instance, each with access to assigned websites.
Connect visitor behaviour with application performance. Keep analytics and operations in one place.
Cookie-free analytics distinguishes users, bots, internal development and customers. Filters, saved segments, sources and campaigns reveal who contributes to your traffic.
Long-term trends and period comparisons reveal changes in usage. Custom events, funnels, A/B experiments and internal system adoption complete the picture.
Track API metrics, health endpoints, SSL certificates and task heartbeats. Incidents, outbound integrations and server events keep operations in view.
An external view of application behaviour helps investigate errors. Grouped JavaScript errors, event timelines, Web Vitals and frustration signals provide context.
Unusual activity, changes in country or network, unexpected hours and traffic spikes generate security signals and alerts. Detection uses tracked events and behaviour.
Identify suspicious IP addresses and manage them in a watchlist. Its feed lets a connected firewall automatically receive flagged addresses according to its configuration.
One self-hosted Webfly Pulse instance for multiple websites. Cookie-free analytics, local geolocation and ASN databases. Geolocation and ASN are resolved locally. Availability monitoring and configured integrations communicate with monitored services.
The web tracker and server telemetry collect data separately.
Every team member has their own account. Assign websites to companies and control the data and features available to customer accounts.
Administrators, internal teams and customers work in one instance. Website access is assigned per user, and accounts support two-factor authentication.
One instance manages multiple companies and their websites. Customer accounts see only assigned websites and restricted aggregate data.
Manage websites, customers, monitors and API keys. Full internal access to security, IP information and audit logs.
Analytics and operational data for assigned websites. Sensitive settings are limited by permissions.
Own websites and aggregated data only. Events, funnels and availability depend on account settings. No visitor identities, IPs or raw live feeds.
Public, read-only access via a token. Identifying information stays hidden.
The web tracker does not use cookies. The public information page does not start a login session for anonymous visitors. Application sign-in uses a technical session cookie. The tracker stores a visitor identifier in browser storage; cookie-free does not mean identifier-free.
On the server running your own Pulse instance. Geolocation and ASN use local databases, with no external API calls at runtime.
Register a website in Pulse and add its generated tracker embed code. Server applications send separate telemetry; websites without JavaScript measurement use monitoring.
Yes. Customer accounts access only assigned websites and restricted aggregated data. Read-only API keys and public shared dashboards via tokens are also available.
Pulse evaluates captured events and application activity. Unusual countries or networks, access times, traffic spikes and other deviations generate security events and alerts without reading server logs.
Yes. Flagged IP addresses are available in the watchlist feed. A connected firewall can automatically consume them and apply its rules; its configuration determines how blocking works.
These groups are tracked as traffic dimensions and can be filtered. They help distinguish regular usage from automated, development and customer activity without excluding events from collection.
Multiple companies, websites and accounts are managed in one instance. Access is separated through application permissions and website assignments, rather than a separate database for each customer. The public site provides information; registration and ordering are not available here.
Visit URLs and sources, events, timestamps and duration, language and screen size, page performance and JavaScript errors. The server also evaluates IP addresses, country and network. Internal systems may provide user identities. The exact scope depends on the integration and permissions.
Operators can configure separate retention periods for raw events and IP addresses. Removing an IP address alone is not full anonymization: identifiers and other data may remain. Daily aggregated trends are retained separately.
No. Webfly Pulse is a separate product by Webfly for web analytics, monitoring and security signals across multiple websites. It is unrelated to the open-source Laravel Pulse package (laravel/pulse), which monitors the performance of a single Laravel application, and shares no code with it.
Webfly Pulse is not a public service with sign-up. Webfly deploys it as a dedicated instance on your infrastructure, connects your websites and applications, and sets up accounts for your team and customers. To see Pulse on your own data, book a demo.
Information and operator: Find information about Webfly, contact details and data processing at webfly.sk. This page explains the application and its capabilities. webfly.sk