Skip to content
All work

AltixNotify

Multi-channel notification routing and immutable event timeline.

Category
Platforms
Status
Live
Platforms
Web, API
Stack
Next.js, TypeScript, Prisma, PostgreSQL, Tailwind CSS, Auth.js

AltixNotify is an internal multi-tenant notification hub and event timeline. Microservices POST business events over a REST API; AltixNotify records every single event unconditionally to an immutable audit timeline, then evaluates routing rules to dispatch across Telegram, Slack, Discord, email and webhook endpoints.

Every internal service needs to alert developers and customers when important business events occur. AltixNotify centralizes all outbound alerts into one resilient hub.

Ingest unconditionally, deliver by rule

Every incoming event POST is persisted immediately to PostgreSQL before any routing logic runs. If a downstream channel throws an error or reaches a rate limit, the event itself is never dropped and can be inspected or redelivered from the dashboard.

Zero-configuration event types

Event types are open strings rather than closed enums. New services can begin emitting custom events immediately without requiring prior schema migrations or manual dashboard configuration.

4 capabilities
Ingest-first pipeline
Every event is recorded in PostgreSQL before rules evaluate, ensuring an unbroken audit history.
Multi-channel fanout
Dispatch single events simultaneously to Telegram, Slack, Discord, transactional email and webhook destinations.
Tenant isolation
Account-scoped API keys ensure one tenant can never access or trigger another tenant's rules.
Flexible payload mapping
Template event JSON into channel-specific message formats with markdown and attachment support.
2 screens

What it looks like in use.

Select any screen to view it full size. Use the arrow controls or keyboard arrows to move between screens and Escape to close.

  • AltixNotify: live control plane and event routing dashboard at notify.altixcode.com.
  • Incoming event logs, delivery statuses and multi-channel dispatch rules.

Tell us what is broken or what should exist.

Send the shape of the problem and any constraints you already know: budget, deadline, or the stack you are working with. You will get a written reply from the engineer who would do the work, not a sales sequence.