Operational is an open-source event tracker for tech products that streams signups, payments, webhooks, cron jobs, and errors into a live feed and pushes critical ones to your phone.[1]
Quick verdict
Small SaaS teams that live inside product events will benefit most from Operational. Its live event feed pairs each event with push notifications and action buttons that trigger webhooks back into the product. The usage-based cloud has no pricing tiers but charges per event after a one-time free allowance, and the AGPL-3.0 codebase means distributors and modifiers must respect copyleft terms. If you need trend analytics or a dead-man's-switch cron monitor with on-call rotations, choose PostHog or Healthchecks instead.[1][2][3][4]
Key features
Live product event feed Signups, payments, cancellations, webhooks, background jobs, and errors arrive as they happen with avatars, timestamps, and rich metadata in one project timeline.[1]
Push notifications to phone and web Critical events reach mobile or the web app immediately through PWA-based push, with per-event notification controls documented in the owner's manual. Self-hosted instances need a separate push setup step.[1][2][3]
Action buttons on events Alerts can carry buttons such as approving a user or banning an IP, each triggering a configured webhook back into your own product.[1][2]
Event chaining with contexts Related events link together so a signup followed by a subscription and a cancellation reads as one workflow instead of isolated rows.[1][2]
Structured JSON event logging An expressive events API accepts structured payloads, which suits messy webhook bodies and cron output that plain text logs flatten.[1][2]
Copy-paste SDKs and playground Node.js and PHP SDKs plus a WordPress plugin cover ingestion, and a developer playground produces snippets to place in a codebase within minutes.[1]
Test mode for integration Test traffic stays free of charge, so wiring up ingestion during development does not consume the paid event allowance.[1]
Self-hosting or managed cloud The same product runs on your own server with Node.js 18.18.x and MySQL 8.x or as the vendor's hosted service with usage-based billing.[1][2]
Who will love it
Solo founders tracking the business pulse: waitlist joins, paid subscriptions, and cancellations land on your phone in real time without building an internal dashboard.[1]
Developers babysitting cron jobs and webhooks: nightly reconciliation runs and payment webhooks become visible individual events with payloads instead of lines buried in a log file.[1]
Small teams that answer events with actions: approving users, triggering follow-up emails, or banning abusive IPs from the alert itself removes a round trip into an admin panel.[1][2]
Who should avoid it
Teams needing trend analytics: the vendor itself points analytics workloads at tools like PostHog, since Operational shows individual events rather than cohort charts or funnels.[1]
On-call rotations needing escalation policy: no schedule, escalation chain, or incident timeline comparable to a dedicated incident platform is documented.[1]
Organizations that cannot accept AGPL-3.0 terms: the copyleft license governs the codebase, so teams with incompatible distribution policies need legal review before adopting or modifying it.[1][2]
Questions worth asking
What is the best Operational alternative for non-technical users?
Is Operational really no-code?
Partly. Browsing the feed, filtering by category, managing projects and teammates, and pressing action buttons are all done in the web app. Sending the first event, though, requires adding an SDK snippet or API call to your product, which is a small developer task.[1]
How much does Operational cost per month?
Pricing checked October 12, 2026: the first 10,000 events are free one time with no credit card, then usage-based per-event billing applies with charges on the 1st of each month and a 5-day grace period before deactivation. Self-hosting the AGPL-3.0 codebase avoids event billing but needs your own server with Node.js and MySQL.[1]
Can you self-host Operational?
Yes. The self-hosting guide documents VPS, Render, Docker, Docker with Coolify, and local installs on Node.js 18.18.x with MySQL 8.x and two domains, followed by .env onboarding and a separate PWA and push-notification setup step.[1]
Sources and editorial review
Source research. Reviewed on October 12, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Operational.co: open-source event tracker for tech products
official · Observed October 12, 2026
Homepage scope, live-feed event types, push notifications, action buttons, contexts, SDK snippet, playground, and cron and SaaS use cases.
- Operational docs: start here
official · Observed October 12, 2026
Setup and event guides, Events API reference, manual on PWA push and team management, test mode, SDKs, and self-hosting section.
- Operational pricing
official · Observed October 12, 2026
Free event allowance, usage-based billing, billing date, grace period, retention, self-hosting offer, and free test mode.
- Operational self-hosting introduction
official · Observed October 12, 2026
Server requirements, installation methods, onboarding, and separate push-notification setup for self-hosted instances.
- operational-co/operational.co on GitHub
official · Observed October 12, 2026
Repository identity, AGPL-3.0 license notice, commit activity, and runtime requirement.
- Operational vs Logsnag
official · Observed October 12, 2026
Vendor's stated scope versus event-notification and analytics tooling, and pricing-model contrast.
- Operational on OpenAlternative discovery
aggregate telemetry · Observed October 12, 2026
Discovery snapshot of stars, version, recency, license, and self-hosting used only for identity corroboration.
- Healthchecks: cron job monitoring
official · Observed October 12, 2026
Catalogue-published cron monitor evidencing the substitutable cron-alerting workflow for the competitor inference.
Compared with these products
No explicit proprietary baseline is recorded.