Trily – Smart Notification & Webhook Automation Platform

1. Vision

Trily is a developer-focused automation platform that allows teams and businesses to receive, transform, and send notifications or webhook-based events without coding complex backend integrations. The idea is simple: one dashboard where you can plug in sources (APIs, apps, webhooks), define routing logic, and get custom notifications through Slack, Discord, email, or other channels.

Trily bridges the gap between raw API events and actionable alerts, focusing on simplicity, reliability, and transparency.

2. Problem Statement

Modern applications emit a lot of signals – webhooks, API callbacks, event notifications. Developers waste time:

• Building custom endpoints to capture and store webhooks.
• Writing glue code for routing and filtering notifications.
• Handling retry logic, authentication, and delivery monitoring.

Trily solves this by offering an out-of-the-box webhook processing engine with configurable routing, security, and analytics.

3. Solution Overview

Trily provides:

• Inbound endpoints (Sources) for any external app or service to send events.
• Routing rules to filter, map, and forward data.
• Connectors (Destinations) to send notifications to Slack, Discord, email, or custom webhooks.
• Dashboard for testing, inspecting, and debugging payloads.
• Developer-friendly API and SDK for automation.
• Pseudo-terminal web interface for command-style interaction.

Example use case: a small SaaS company plugs Trily into their payment gateway webhooks. Trily parses them, filters failed transactions, and sends Slack alerts only when necessary.

4. The Pseudo-Terminal Concept

Instead of building a traditional dashboard, Trily introduces a browser-based terminal interface that mimics a CLI but runs safely in the web browser.

Concept

Developers can type commands such as:

trily source add --name invoices --secret auto
trily source list
trily preview --source invoices --sample ./invoice.json

The pseudo-terminal executes these commands via REST or WebSocket calls to the backend, displaying JSON results and logs in real time.

Purpose

• Provides a fast and lightweight UI for power users.
• Reduces frontend complexity while still feeling interactive.
• Enables easy debugging, configuration, and testing of webhooks without a full graphical dashboard.

Implementation

• Frontend: Next.js + xterm.js for the terminal view.
• Backend: REST endpoints like /api/sources, /api/templates, /preview.
• Transport: WebSockets for streaming logs (e.g., outbox tail).
• Security: JWT auth, command whitelisting, and rate limiting.

Example UX Flow

1. User logs in with JWT.
2. Types trily source add invoices to create a webhook source.
3. Types trily preview --sample to simulate event flow.
4. Trily responds with structured JSON output and visual feedback in terminal.

Long-term goal

The terminal becomes the main entry point for advanced users, while a lightweight visual dashboard can be added later on top of the same API.

5. Business Model

Free Tier

• 3 active sources
• 3 destinations
• 1000 events/month
• Community support

Pro Tier ($12/mo)

• Unlimited sources & destinations
• Priority processing
• 30-day event retention
• Email & Slack support

Business Tier ($39/mo)

• Custom routing rules
• Multiple team members
• Audit logs & observability
• SLA uptime guarantees

Enterprise (Custom)

• SSO, advanced security
• Private deployment (on-prem/cloud)
• Dedicated support and SLAs

Revenue model: recurring subscriptions via Stripe.

6. Target Audience

• Developers and DevOps teams automating alerts.
• Small SaaS businesses needing event routing.
• Freelancers and agencies who need webhook debugging tools.
• Tech startups using multi-app ecosystems (Stripe, GitHub, Notion, etc.).

7. Competition

Competitor	Focus	Weakness
Pipedream	Workflow automation	Heavy, over-engineered
Hookdeck	Webhook proxy & replay	No routing or alerting features
Zapier	No-code automation	Not developer-centric
Svix	Webhook management	Lacks multi-destination routing

Trily’s edge: developer-first simplicity, routing flexibility, terminal UX, and affordability.

8. Technology Stack

Backend: .NET 9 (C#), ASP.NET Core, EF Core, PostgreSQL, Redis Frontend: Next.js / React + xterm.js (pseudo-terminal) Infrastructure: Docker, Docker Compose, GitHub Actions CI/CD Monitoring: OpenTelemetry + Prometheus + Grafana Auth: JWT with refresh tokens Billing: Stripe Checkout API

9. Architecture Summary

• API Layer: RESTful Web API with JWT auth

• Background Workers: handle event processing, retries, and dispatch

• Database: PostgreSQL (persistent data) + Redis (cache, queue)

• Observability: built-in /health and /metrics

• Event Flow:

  1. Webhook hits /ingest/{sourceKey}
  2. Validates HMAC signature
  3. Enqueues event in Redis
  4. Worker reads, applies filters, and dispatches
  5. Result logged and visible via dashboard API or terminal

10. Marketing Strategy

Phase 1: Pre-launch content (now)

• Build social presence on Instagram, TikTok, X as a dev tool brand.
• Post short videos explaining webhooks, APIs, and automation.
• CTA: waitlist and landing page signup.

Phase 2: Early access (MVP)

• Invite developers via GitHub and Product Hunt.
• Offer lifetime discount for first 100 users.
• Collect feedback through Discord community.

Phase 3: Growth

• SEO-optimized docs and guides ("How to handle Stripe webhooks with Trily").
• Integration partnerships (Notion, GitHub Apps, Slack).
• Referral program for developers.

11. Roadmap

Phase	Duration	Goal
MVP (3 months)	Basic API, JWT auth, webhook routing, DB + Redis infra
Beta (6 months)	Pseudo-terminal UI, Stripe billing, user management
v1.0 Launch	Public rollout, social marketing push
Post-launch	Integrations marketplace, AI event summarizer

12. Long-Term Vision

Trily evolves from a webhook router into a universal notification brain. A place where developers can monitor every event their system emits, visualize flows, and act on them instantly. Think of it as the modern equivalent of "Zapier for engineers" — fast, self-hostable, transparent.

13. Team & Ownership

• Mateusz – Founder, Lead Backend Engineer
• Collaborators – Frontend & marketing support
• Open to future contributors via GitHub (Trily Open Core model)

14. Current Status

• ✅ Backend initialized (ASP.NET 9 Web API)
• ✅ Dockerized environment (Postgres + Redis)
• 🧩 JWT auth in progress
• 🧩 Event routing engine planned
• 🔜 Pseudo-terminal UI (Next.js + xterm.js)