Introduction

notific.me is the second factor for decisions (2FD). Two-factor authentication protects logins; notific.me protects decisions.

Systems, plugins and AI agents send events. notific.me decides who needs to know, delivers the notification with its context, and sends the person’s answer, signed, back to the system that asked.

Every notification can become a conversation: it arrives with context, renders what is needed and accepts an answer that goes back to whoever asked.

The problem

Notifications today are one-way. A system shouts, and the person has to open a dashboard, find the context and act somewhere else. With AI agents in production, that is no longer enough: an agent that wants to delete records, deploy or move money needs to ask a human, safely, with an audit trail and little friction.

notific.me turns that around:

• Every notification can become a conversation. It arrives with context, renders a card and accepts an answer.
• The decision has proof. The answer is signed by a key on the person’s device that only signs after biometrics or the device PIN, or confirmed with a 2FA code.
• Decisions come to the person. Instead of 15 dashboards, one inbox with the options in hand.

Who it is for

You are	You use notific.me to
A developer	Get alerts from CI, deploys, containers and cron jobs, and approve risky steps from your phone.
A team building AI agents	Put a human in the loop: approvals, choices and instructions, with signed answers and a summary ready for the model.
A company	Route events to the right people with rules, quiet hours and escalation, with an audit trail of every decision.
Anyone	Receive what matters, with the options in hand, on the app or the installable web app (PWA).

How it works in one minute

1. Your system calls the SDK, the REST API, an incoming hook or the MCP server.
2. Policy rules decide whether to notify now, group in a digest, suppress or escalate, and to whom.
3. The person receives the notification with a card (text, metrics, charts, tables, progress, buttons and questions).
4. The person answers. Depending on the level, that takes a tap, an unlocked device, biometrics or a 2FA code, and sometimes a quorum.
5. The server accepts exactly one answer and sends the signed reply back: to your webhook, or to the ask() call that is waiting.

See How it works for the flowcharts.

Open protocol, closed platform

The protocol (JSON Schemas for events, cards, questions and replies), the SDKs, the open channels and the plugins are open source (Apache 2.0), so anyone can integrate or build their own interface. The official app, the server and the hosted infrastructure are closed.

Status

notific.me is in its foundation phase: the full cycle event → notification → decision → reply works on the web app (app.notific.me) and the installable PWA. The native apps come next.