Submission Guidelines
We rely on the community to track the health of SaaS products. Here’s how to contribute effectively and responsibly.
1What We Track
All Your SaaS Are Belong To Us focuses on identifying software products that are showing signs of distress, abandonment, or user-hostile pivots. We are looking for meaningful signals that impact customers.
Good Signals
- •Public Layoffs: Documented workforce reductions, presented with their source and without inferring a company's finances.
- •Leadership changes: Publicly documented departures, without speculation about the reason.
- •Pricing changes: A dated comparison from public pricing or customer communications.
- •Documented downtime: A dated status page, incident report, or other original source.
What to Avoid
- •Rumors: "I heard they are struggling" without proof.
- •Private Data: NDA-protected info, internal emails, or financial docs.
- •Personal Attacks: Criticizing the company is fine; harassing individuals is not.
- •Feature Requests: "They didn't build X" is not a death signal.
2Verification Process
Submitted signals enter a moderation queue. Reviewers can check provided evidence links such as news articles, company announcements, and status pages. A published signal is still a community contribution, not a verified company statement.
The public site displays a pseudonymous handle rather than your account email. Authorized operators can associate a contribution with the internal account for moderation and abuse response.
3The "Dead" Status
A terminated label should be supported by at least one of these publicly checkable conditions:
The official website has remained unavailable or parked across repeated dated checks.
An official shutting down announcement has been made.
The product is no longer accepting new signups or payments.