# Sendora

> Email marketing platform you run for clients — Mailchimp's category, your codebase, your billing rules.

Source page: https://saascode.ai/products/sendora
Machine-readable record: https://saascode.ai/products/sendora.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $249 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

Sendora is an email marketing product. An account collects contacts, organises them into lists and segments, composes campaigns in a block editor, sends them, and reads a report. It also runs automated sequences, hosts subscription forms with double opt-in, and manages unsubscribes and suppression.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/sendora — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://sendora.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

3 roles seeded on the demo (of the 4 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Campaign collaborator** (`member`) — `user@demo.com` / `demo123`
  Does campaign work, without billing or domain setup. Lands on `/lists`.
- **Account owner** (`org_admin`) — `org-admin@demo.com` / `demo123`
  Runs the account: lists, campaigns, domain, billing.
- **Platform admin** (`super_admin`) — `admin@demo.com` / `demo123`
  The backend: every account and the deliverability console.

Or open a role directly: https://saascode.ai/demo/sendora?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 4** — distinct roles accepted by the role CHECK constraint: admin, member, org_admin, super_admin
- **tables: 74** — distinct CREATE TABLE statements across every applied migration
- **migrations: 100** — .sql files in supabase/migrations
- **page modules: 86** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 165,260** — lines of code (comments and blank lines excluded) across 1135 TypeScript files (147,318) and 124 SQL files (17,942); node_modules and .next excluded
- **api route files: 258** — files named route.ts under src/app/api
- **http operations: 351** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 74 tables, 124 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-07-29

## Complete capability inventory

9 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Contacts, lists & segments

- **Contact lists and segments** — at /segments are dynamic: a set of conditions evaluated live. The segment editor shows a recipient count as conditions are built, and the count can be previewed before the segment is saved. Segments work on standard contact fields on every plan; conditions on custom fields appear only when custom fields are available to the account.
- **Custom fields** — are extra per-contact attributes an account defines for itself. They can be used as segment conditions and mapped during import. Available on Growth and above.

### Campaigns & sending

- **Campaigns** — live at /campaigns, indexed by status: draft, scheduled, sending, sent.

### Deliverability & metrics

- **Campaign metrics** — Reports at /campaigns/[id]/report are click-primary. Clicks, unique clicks, bounces, complaints and unsubscribes are the headline numbers. There is no bare open rate anywhere in the product.
- **Sending domains** — An account can send immediately from the platform's shared subdomain, so nothing blocks the first campaign. Sending from a sender's own domain is the upgrade, not the entry requirement.
- **Open tracking** *(seller-authored)* — Open tracking is available and off by default, because a bare open rate has stopped meaning what people think it means. Clicks are the headline number here, and opens are the optional supplement an account turns on deliberately.

### Sequences & consent

- **Subscription forms and double opt-in** — Forms at /forms generate an embeddable script for any website, plus a hosted page as a fallback. The submission endpoint is open to anonymous callers by necessity, so it is defended in layers: a honeypot field, per-address rate limiting, validation that accepts only the fields the form actually declares, and — most importantly — the owning account is resolved from the form record itself rather than from anything the caller sends, so a submission cannot be attributed to a different account.
- **Unsubscribe, preferences and suppression** — Every message carries tokenized links. A contact can unsubscribe in one click, resubscribe from the same page, or open a preference page for finer control. None of this requires an account — contacts never sign in.
- **Sequences** — Sequences at /sequences are automated multi-step flows — a welcome series, a drip. Each step has a delay and a message, and contacts are enrolled individually, so two people at different points in the same sequence are at different steps. Steps run from the scheduled-task background job, which means the schedule that job runs on determines how precise the timing can be.

## What each system gives the operator

*stated.*

- **Contacts, lists & segments** — The recipient list is built from the account's own data, not maintained by hand.
- **Campaigns & sending** — A campaign goes out on schedule and keeps going if a batch fails.
- **Deliverability & metrics** — Mail reaches inboxes, and the report says whether it was read or just delivered.
- **Sequences & consent** — Consent is recorded at the moment it is given, and honoured everywhere after.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Every mailable address can be traced to the moment someone agreed to it.

A list is an asset right up until nobody can say where it came from. Addresses arrive from a form, an import, a spreadsheet from a colleague, an event badge scan — and six months later there is no way to distinguish the people who asked to hear from the business from the ones who were added. That mixture is what produces complaints, and complaints are what get a sending domain in trouble. By the time delivery starts failing, cleaning the list means deleting most of it.

### The report leads with what someone did, not with what a mail client loaded.

Open rates became decorative when mail clients started pre-fetching images. Teams still report them, still compare them week over week, and still make decisions about subject lines and send times using a number that mostly measures which mail providers their recipients use. The damage is not the wrong metric — it is the confidence. A campaign with a healthy open rate and no clicks reads as a success in the weekly update, and nobody investigates the thing that is actually not working.

### Your first campaign goes out today, not after a DNS argument.

Domain authentication is where most email tools lose the customer. Setting it up correctly means DNS records, a registrar login somebody else controls, and terminology the person trying to send a newsletter has never encountered. So the account is created, the first campaign is drafted, and it never goes out — the tool gets remembered as the one that asked for something impossible before it did anything useful.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **A Node host and a Supabase project** (required) — The chassis. Next 16 on any Node host, with Postgres, auth and storage coming from Supabase.
- **A scheduled runner** (required) — Eight jobs ship declared for Vercel, including the send queue itself. On another host they are a cron configuration you wire by hand, and a campaign scheduled for Tuesday simply waits.
- **A sending domain you control** (optional to start) — An account can send from the platform's shared subdomain immediately, so nothing blocks the first campaign. Authenticating a sender's own domain is the upgrade, and it is DNS work at a registrar rather than a service you buy.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 165,260 lines across the application and its database, 74 tables defined by 100 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Sendora demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 3 of them: Campaign collaborator, Account owner, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 86 page modules and 351 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: A Node host and a Supabase project, A scheduled runner. Optional: A sending domain you control. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 100 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $249?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Sendora vs listmonk, vs Brevo, vs building it yourself](https://saascode.ai/inside/sendora-vs-listmonk-vs-brevo-vs-building-it-yourself.md)
- [Self-Hosted and Owned Email Marketing Platforms in 2026: A Buyer's Guide](https://saascode.ai/inside/self-hosted-and-owned-email-marketing-platforms-in-2026-a-buyer-s-guid.md)
- [Road to Sendora](https://saascode.ai/inside/road-to-sendora.md)

## Links

- Catalog page: https://saascode.ai/products/sendora
- Product record: https://saascode.ai/inside/products/sendora
- Live demo: https://sendora.saascode.ai
- Every product: https://saascode.ai/llms.txt