ShipstryBeta
Before You Ship

Submission Guidelines

Shipstry is for real products, not just ideas. The listing should represent something people can genuinely access, evaluate, discuss, and vote on today.

The review process favors product reality, honest presentation, and maker ownership over launch noise or distribution tricks.

Usually accepted

Real products with a working destination URL, clear ownership, and a credible user experience.

Reviewed case by case

Private betas, repo-first launches, and unusual product shapes may need more evidence.

Usually rejected

Waitlists, service businesses, spammy pages, and unsafe listings do not fit the registry.

The Short Rule

If the listing exists mainly to collect backlinks, harvest traffic, or manufacture launch metrics, it is not a fit for Shipstry.

Fit

What belongs here

The common thread is simple: the thing being submitted should itself be the product people are here to discover.
Fit 1

Apps and software

Web apps, mobile apps, desktop apps, browser extensions, SaaS products, and AI tools with a real product experience.

Fit 2

Developer products

APIs, SDKs, CLIs, infrastructure tools, open source products with clear docs or a usable demo, and other builder-facing software.

Fit 3

Productized platforms

Marketplaces, directories, communities, media products, and similar offerings when the product itself is the experience.

Fit 4

Makers with ownership

Submissions from founders, makers, team members, or people with clear permission to represent the product.

Standards

Five approval checks

These are the standards every approved listing should pass, regardless of category or pricing tier.
01

It is a real product

The submission should represent a real product or platform, not just an idea, teaser page, or vague concept.

02

It is launch-ready or usable now

Users should be able to understand, access, try, install, register for, or meaningfully evaluate it today.

03

It is submitted by the right person

The submitter should be the maker, founder, team member, or another clearly authorized representative.

04

It fits product discovery

The listing should make sense in a community that discovers, discusses, and votes on new products.

05

It is honest and complete

The URL, screenshots, logo, description, and claims should accurately reflect the product without hype or misdirection.

Boundaries

What usually gets rejected

These patterns typically fall outside Shipstry, even when the page itself looks polished.
Usually rejected

Pure waitlists, coming soon pages, and idea-only landing pages

Agencies, consultancies, freelancer services, and personal portfolios

Thin affiliate pages, spam directories, or pages built mainly for backlinks or SEO

Broken, inaccessible, misleading, or obviously low-trust product pages

Products that are illegal, unsafe, infringing, malicious, or clearly abusive

Reviewed case by case

Private beta products

Allowed when the product clearly exists and there is a credible way to request or obtain access.

Open source projects

Allowed when the repo is paired with docs, a demo, screenshots, or a clear onboarding path.

Newsletters, courses, and communities

Allowed when the offering itself is the product, not just a lead magnet for a service business.

Relaunches and major versions

Allowed only when there is a meaningful new release, major rebuild, or substantial change in product scope.

Review Flow

How review works

Approval is not just a content check. We review for product reality, launch fit, trust, and quality.
What speeds approval
  • A working product URL with an obvious product experience.
  • Accurate screenshots, copy, and ownership context.
  • Clear explanation when the product falls into an edge case.
1

We check whether the submission is a real product and whether the listing is complete.

2

We verify fit with Shipstry: maker-built, product-first, and suitable for launch discovery.

3

We look for duplicates, spam, misleading claims, trust and safety issues, and low-quality SEO pages.

4

We approve, reject, or ask for clarification when the product falls into a case-by-case category.

Ready to Submit

If the product clears these checks, send it in.

Submit when the product is real, accessible, honestly presented, and ready for people to evaluate today.