Skip to main content
aciona.me has few concepts, and they all fit on a single line: an organization has members, who form teams, which own services, covered by on-call schedules. External tools send alerts through alert sources, and alerts become incidents.
Your company’s isolated space. Every piece of data — teams, services, schedules, sources, incidents — belongs to one organization and is never visible to another.An organization can have child organizations (one per business unit, for example). The plan and its limits belong to the root organization and are shared across the group.See organizations
A person inside an organization, with a role: owner, admin, member or viewer. The role defines what they can configure and which incidents they can act on.See roles and permissions
The group of people responsible for a set of services. The team is the unit of responsibility: it connects services to on-call schedules.See teams
What is being monitored: payments-api, checkout, auth, erp-integration. Each service has a responsible team and a default severity, used when the alert does not carry its own.See services
Defines who is on call at any moment for a team: ordered participants, rotation type (weekly or 24x7), timezone and rotation start. Temporary overrides cover vacations, days off and one-off swaps.See on-call
The entry point for an external tool. Each source has a type (Grafana, Prometheus, Datadog, CloudWatch, Zabbix, New Relic or generic webhook), a unique ingestion URL and a unique token.See alert sources
The raw event arriving from the monitoring tool, with the original payload preserved. An alert can create an incident, be aggregated into an existing one, or resolve it.
aciona.me’s unit of work: someone needs to look at this. It has severity, status, an owner, a timeline and a notification history.
In Brazilian Portuguese the customer-facing term is acionamento. In English — and in every technical contract, such as routes, payload fields and enums — the term is incident.
See incidents

​
How they connect

Configure a single complete path — one team, one service, one schedule and one source — and the whole product already works end to end. Start with Receive your first alert.