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

LayerTechnology
LanguagePHP 8.4
FrameworkLaravel 13
QueueLaravel Horizon + Redis 8
DatabasePostgreSQL 18 (one database per service)
FrontendLivewire 4 (dashboard, admin), vanilla JS (widget)
EmailPostmark
TestingPest 5, Playwright (widget)
InfrastructureDocker Compose v5, Caddy

Documentation

DocumentDescription
ArchitectureSystem design, service boundaries, data flow
Data ModelDatabase schema, ER diagram, tables, indexes
CommunicationEvent bus, payloads, outbox, correlation IDs
Getting StartedDeveloper environment setup
ServicesPer-service responsibilities and internals
API ReferencePublic and internal API endpoints
Attribute TypesThe seven attribute types with wire formats
Widget IntegrationEmbedding the widget, CSS customization
Seller OnboardingDashboard walkthrough, attribute configuration
ConfigurationEnvironment variables reference for all services
DeploymentDocker topology, production considerations
TestingTesting strategy and conventions
ContributingCode style, git workflow, commit conventions

Sub-Projects

The product is sequenced into four sub-projects, each with its own spec and implementation plan:

  1. The Loop — Tenancy, catalog, widget, consent, matching, email dispatch
  2. Paid Channels — SMS, WhatsApp, voice drivers, phone verification, usage metering
  3. Commercialization — Plans, quotas, Stripe billing, seller analytics
  4. Additional Ingress — Scraper/watcher service, renewal scheduler

License

Proprietary. All rights reserved.