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.
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.
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.
- Profile claim
- Public submissions + approval queue
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.
- Bulk CSV listing import
- Free tier listing
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.
- SEO pages (metadata, JSON-LD, async sitemap)
- Public browse/search/proximity
### Ratings
A scheduled reconciliation job re-verifies the counters periodically as a safety net — for example after a bulk data operation.
### Known limit
A reviewer cannot currently edit their own pending review from the interface. The permission and the underlying endpoint exist, but no screen offers the action in this version.
The claim flow depends entirely on email. If no email provider is configured in Admin → Integrations, the verification link is never sent and the whole funnel is inert — that is the first thing to check when claims are not completing.
Submissions are not listings until approved. Nothing a stranger types appears on the directory without passing the queue.
Proximity ("near me") also runs in the database, using each listing's stored coordinates. Nothing is geocoded at search time — coordinates are resolved once, when a listing is saved.
Ranking. Paid tiers get priority placement. That boost is a property of the listing, applied in the search query itself, so it works identically for signed-in users and anonymous visitors.
Known limits in this version. The minimum-rating filter chips are visibly disabled, because the search routine takes no rating argument — they are inert on purpose rather than quietly broken. Browse result cards also carry no call / website / directions buttons; the search result set has no contact column, so those actions live on the listing page instead.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 43 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 60 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · categories · credit_balances · credit_transactions · currencies · data_exports · data_imports · faq_categories · faq_items · feature_flags · inbound_webhook_events · inbound_webhooks · languages · listing_claims · listing_submissions · listings · marketing_audience_members · marketing_audiences · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · processed_events · product_purchases · products · provider_prices · push_devices · report_templates · reviews · roles · scheduled_tasks · seo_meta · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 3 required.
The chassis. Next 16 on any Node host, with Postgres, auth and storage coming from Supabase.
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.
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.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
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.