# Listora

> Run a paid niche directory as a business — the Brilliant Directories model on a codebase you own, with listing plans, claim flows, search and maps from day one.

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

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

Price: $99 (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

Listora is a niche business directory run as the operator's own product. The public side is a searchable catalog of business listings — restaurants in a city, B2B suppliers, physios, tradespeople, venues, whatever vertical it is pointed at. The commercial side is that the listed business claims its own page and pays a recurring listing plan to stand out.

## 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/listora — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://listora.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

4 seeded roles. Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Business teammate** (`member`) — `teammate@demo.com` / `see the page`
  Edits the listing content for their business.
- **Listed business** (`org_admin`) — `org-admin@demo.com` / `see the page`
  Holds the subscription, edits the page, answers reviews.
- **Operator staff** (`admin`) — `staff@demo.com` / `see the page`
  Works moderation queues, submissions and listings.
- **Directory operator** (`super_admin`) — `admin@demo.com` / `see the page`
  The operator platform: categories, moderation, plans.

Or open a role directly: https://saascode.ai/demo/listora?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: 60** — distinct CREATE TABLE statements across every applied migration
- **migrations: 110** — .sql files in supabase/migrations
- **page modules: 77** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 151,137** — lines of code (comments and blank lines excluded) across 1035 TypeScript files (136,178) and 130 SQL files (14,959); node_modules and .next excluded
- **api route files: 203** — files named route.ts under src/app/api
- **http operations: 271** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 60 tables, 92 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-08-05

## Complete capability inventory

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

### Listings & attributes

- **Rich listing profiles + categories** *(seller-authored)* — A listing carries the fields that matter in its vertical rather than a generic form — the attributes a category defines, set up once when the category tree is shaped. A restaurant and a plumber are not described by the same nine boxes.
- **Free tier listing** *(seller-authored)* — Every business gets a page for nothing. A directory only has value when it is complete, so the free tier is the product's inventory strategy rather than a trial — the paid tiers sell prominence on top of a listing that already exists.
- **Featured tier perks** *(seller-authored)* — Paid tiers buy placement and presentation on a listing that is already live: position in browse and search results, richer profile treatment, and the analytics a paying business expects to see.

### Claims & moderation

- **Reviews (write requires account)** — A listing's average rating and review count are recalculated automatically whenever an approved review is added, changed or removed. There is exactly one routine in the system allowed to write those two values, and it runs from the reviews trigger. No screen, no import and no scheduled job updates them directly. This is why the number shown always matches the reviews behind it.
- **Profile claim** — 1. A business owner finds their listing and starts a claim from the listing page. 2. They receive an email with a single-use, expiring verification link. Proving control of the business email address is the verification. 3. With operator approval turned on, the claim then waits in Admin → Claims and the claimant sees a "pending approval" page. If approval is off, it completes immediately. 4. On completion the system creates the business's organization, promotes the claimant to business owner, and links the organization to the listing.
- **Public submissions + approval queue** — Anyone, signed in or not, can submit a business from the public submit page. Submissions arrive in Admin → Submissions with status pending. Approving one turns it into a real listing; optionally an invitation to claim it is emailed to the submitted contact address. Rejecting one leaves no public trace.

### Search & maps

- **Public browse/search/proximity** — Browse is the product's main surface. Search runs entirely inside the database: full-text matching over listing names and descriptions, plus category filters, custom-attribute filters and ordering by relevance, rating or featured standing. No external search service is called, so search speed depends on the database and nothing else, and it costs nothing per query.

### Running the directory

- **SEO pages (metadata, JSON-LD, async sitemap)** *(seller-authored)* — Listing and category pages ship with metadata, structured data and a sitemap generated in the background. For a directory, organic search is not a marketing channel — it is the whole distribution model.
- **Bulk CSV listing import** *(seller-authored)* — Loads listings in bulk from a file, which is how a directory launches with a thousand businesses instead of three. An empty directory has no reason for anyone to visit it, and no visitors means no business will pay to be in it.
- **Premium tier perks + listing analytics** — Premium listings get an analytics dashboard showing profile views over time. Search impressions are not measured in this version — the dashboard reports them as "not measured" rather than as zero, deliberately: a business reading "0 impressions" would reasonably conclude nobody is finding them, and that is not something this version actually measured.

## What each system gives the operator

*stated.*

- **Listings & attributes** — The listing carries the fields that matter in your vertical, not a generic form.
- **Claims & moderation** — Businesses take over their own page, and you stop being the edit queue.
- **Search & maps** — A visitor finds the nearest open business without leaving the directory.
- **Running the directory** — The directory launches populated, not as an empty page asking for submissions.

## The problems it was built to solve

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

### An owner claims their listing and keeps it current without going through you.

Directories die of staleness. The operator seeds a few hundred listings, and within a year the phone numbers are wrong, two of the businesses have closed and one has moved. Every correction arrives as an email asking the operator to make an edit, which means the directory's accuracy is capped by how much unpaid administration one person will absorb. Visitors notice before the operator does — they call a disconnected number once and do not come back.

### The directory opens populated, not as an empty page asking for submissions.

A new directory has a chicken-and-egg problem it usually loses. Businesses will not pay to appear somewhere with no visitors, and visitors will not come to a page with nine listings. Most launches try to solve it by selling first, which fails, or by waiting for organic submissions, which never arrive. The project stalls at the point where it needs momentum most, and the operator concludes the vertical was wrong.

### Category and listing pages are built to be the search result, not to be linked from one.

Nobody browses a directory homepage. They search for a plumber in their town and click whatever comes up, and if the directory's pages are not what comes up then the directory is a website with no traffic and no reason for a business to pay for a place in it. Operators who treat search as a marketing task to do later discover that for this kind of product it was never a task — it was the distribution model, and the pages had to be built for it from the start.

## 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 geocoding provider** (required) — Addresses are turned into coordinates once, at save time. Without one, listings save but nothing appears on a map or in a proximity search — which is most of what a visitor came to do.
- **A scheduled runner** (required) — Three jobs run from a single scheduled endpoint. On a host that does not read the shipped schedule file, an external trigger has to be added, or every one of them silently never runs.

## FAQ

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

The complete source repository behind the live demo — 151,137 lines across the application and its database, 60 tables defined by 110 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 Listora 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 4 of them: Business teammate, Listed business, Operator staff, Directory operator. 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. 77 page modules and 271 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 geocoding provider, A scheduled runner. Optional: none. 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 110 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 $99?**

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

- [Listora vs Brilliant Directories](https://saascode.ai/inside/listora-vs-brilliant-directories.md)
- [Best Directory Website Software in 2026: A Buyer's Guide](https://saascode.ai/inside/best-directory-website-software-in-2026-a-buyer-s-guide.md)
- [Road to Listora](https://saascode.ai/inside/road-to-listora.md)

## Links

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