notifito
A B2B2C micro-SaaS notification platform. Sellers embed a widget on their site; consumers register interest in a product or service that is currently unavailable; when it becomes available, notifito notifies them.
What is notifito?
notifito connects sellers with interested consumers through real-time notifications. It is industry-agnostic: sellers define what they sell during onboarding rather than choosing from a fixed taxonomy.
Use cases: Back-in-stock alerts, appointment availability, restock notifications, price drop alerts, and any scenario where a consumer wants to be notified when something becomes available.Architecture
notifito is a Laravel monorepo with five independently deployable applications and one shared contracts package:
apps/edge Public API surface (widget API, push API, webhooks)
apps/core Domain logic (tenancy, catalog, subscriptions, matching)
apps/dispatch Notification delivery (drivers, templates, delivery state)
apps/dashboard Seller-facing UI (Livewire, no database)
apps/admin Platform operator UI (Livewire, no database)
packages/contracts Shared event payloads and DTOs
widget/ Embeddable JavaScript widget (vanilla JS, no framework)
Services communicate asynchronously through a thin EventBus abstraction over Laravel queues on Redis, with synchronous HTTP only where a human is waiting for the answer.
Tech Stack
| Layer | Technology |
|---|---|
| Language | PHP 8.4 |
| Framework | Laravel 13 |
| Queue | Laravel Horizon + Redis 8 |
| Database | PostgreSQL 18 (one database per service) |
| Frontend | Livewire 4 (dashboard, admin), vanilla JS (widget) |
| Postmark | |
| Testing | Pest 5, Playwright (widget) |
| Infrastructure | Docker Compose v5, Caddy |
Documentation
| Document | Description |
|---|---|
| Architecture | System design, service boundaries, data flow |
| Data Model | Database schema, ER diagram, tables, indexes |
| Communication | Event bus, payloads, outbox, correlation IDs |
| Getting Started | Developer environment setup |
| Services | Per-service responsibilities and internals |
| API Reference | Public and internal API endpoints |
| Attribute Types | The seven attribute types with wire formats |
| Widget Integration | Embedding the widget, CSS customization |
| Seller Onboarding | Dashboard walkthrough, attribute configuration |
| Configuration | Environment variables reference for all services |
| Deployment | Docker topology, production considerations |
| Testing | Testing strategy and conventions |
| Contributing | Code style, git workflow, commit conventions |
Sub-Projects
The product is sequenced into four sub-projects, each with its own spec and implementation plan:
- The Loop — Tenancy, catalog, widget, consent, matching, email dispatch
- Paid Channels — SMS, WhatsApp, voice drivers, phone verification, usage metering
- Commercialization — Plans, quotas, Stripe billing, seller analytics
- Additional Ingress — Scraper/watcher service, renewal scheduler
License
Proprietary. All rights reserved.