SaaS landing page or full-stack boilerplate?
A landing page presents a product; a full-stack starter may provide parts of the application. Neither label guarantees a complete subscription business.
- For a product launch page, compare messaging sections, pricing presentation, documentation and lead capture. Verify where submitted forms go; a styled form can still have no working backend.
- For a subscription application, inspect account creation, server-side authorization, payment webhooks and data ownership. A pricing card or checkout button is not evidence that subscription state is synchronized.
- List required third-party services and their configuration before adopting a starter. Test failed payments, cancelled accounts and unauthorized requests in an isolated environment. Treat functionality marked unknown in this catalog as something to investigate, not as included functionality.
Separate the marketing page from the paid product
| Task | Where to look | Evidence to collect |
|---|---|---|
| Explain and collect interest | Marketing routes and form destination | The product message is editable and a test enquiry reaches its intended destination. |
| Create an account | Session handling and server authorization | A new account cannot read another account’s records. |
| Change a subscription | Webhook handler and local subscription state | Repeated, delayed and failed events have defined handling in an isolated test environment. |
| Operate the product | Database migrations, secrets and recovery notes | Required services, credentials, running costs and recovery responsibilities are listed. |
Run a small adoption trial
Write two separate lists: pages supplied and working services demonstrated. If the repository only supplies marketing components, budget the account and billing application separately. For a full-stack candidate, follow its test setup and verify one cancelled subscription without using real customer data or live payments.
Keep a note of the repository commit, environment, steps and result. Use three outcomes: demonstrated, not included, or unresolved. Estimate the work needed to close each gap before choosing. A missing check is not a pass, and this guide does not report that we performed these tests on every catalog entry.
Primary documentation
How catalog records and evidence are prepared →These are selection criteria, not claims that every listed template has these capabilities. Verify the linked repository and demo before adopting a project.
Prepared with AI assistance as a selection checklist. No named human review or hands-on project test is recorded for this guide.
Report a correction