Ariyes

Ariyes is a business platform that puts marketing, sales, support and communications in one workspace. Instead of paying for a campaign tool, an outreach tool, a help desk, a shared inbox and a CRM that don't talk to each other, a team gets all of them with one login, one contact list and one bill.

The modules

• Campaigns: email campaigns with templates, open and click tracking, and reply detection.
• Sequences: multi-step outreach by email and other channels, which stops for a contact as soon as they reply.
• Broadcasts: one-off SMS and WhatsApp messages to a list, within WhatsApp's template and 24-hour rules.
• Contacts: lists, custom fields, CSV import with email verification, and a suppression list every module respects.
• Inbox: email, live chat, SMS and WhatsApp conversations in one shared view.
• Help desk: tickets with SLAs, a knowledge base, a branded customer portal and reports. A workspace can run several help desks.
• CRM: companies, deals and pipelines, linked to the same contacts.
• Drive: file storage and sharing, with per-seat storage, virus scanning and share links.
• To-dos: shared task lists for the team.

Pricing is per seat, and every plan includes every module. Plans only differ on limits like seats and monthly volume.

Built for deliverability

Email is the heart of the product, so sending is built carefully:

• Sending domains are verified with DKIM, SPF and DMARC before use.
• Email goes through Mailgun, with AWS SES taking over automatically if Mailgun fails.
• Bounces, complaints and replies come back through signed webhooks. Each one is stored before it's processed, so none are lost.
• If bounce or complaint rates climb, sending pauses on its own before reputation suffers.
• Every message carries an unsubscribe link, unsubscribe headers and the sender's postal address.

How it's built

Ariyes is one Next.js app behind many subdomains: campaigns., crm., drive. and so on. Middleware reads the hostname and sends each request to its module, and one sign-in works across all of them.

• Data: PostgreSQL through Prisma. Every query is tied to one workspace, enforced in the ORM and again with row-level security in the database.
• API: tRPC inside the app, plus a public REST API with OpenAPI docs and API keys with scopes.
• Workers: BullMQ jobs on Redis send messages, fan out campaigns in batches, advance sequences, process webhooks, poll mailboxes for help desk tickets, and scan and preview Drive files.
• Providers: Mailgun and AWS SES for email, Twilio for SMS and WhatsApp, Chatwoot embedded for the shared inbox, Stripe for billing, and S3-compatible storage for files.
• Running the business: roles and per-module permissions, an audit log, encrypted credentials, self-serve signup and onboarding, workspace deletion, a platform admin for plans and support, and a public site with a blog, changelog and docs.

A few rules are non-negotiable and checked on every change: every send checks the suppression list, sends are idempotent so a retried job can't send twice, webhook events are never lost, and a reply stops a sequence in the same database transaction that records it.

The codebase has 123 data models, 91 database migrations, 59 API routers, 177 pages and 434 test files.

How I built it

I built Ariyes on my own with two Claude sessions: one as architect and reviewer, writing a prompt for each phase and checking the result, and one in VS Code writing the code. The first commit was on 10 May 2026, and version 1 shipped a week later with 20 phases behind it. The help desk, platform admin, CRM, Drive and the public website followed over the next two months.