Can I promote my own software here?
Only if it is open source, or if you wait until Wednesday, use the appropriate flair, and provide something of value beyond the software itself.
A source-backed Rankhog guide to r/software: public rules, community context, posting fit, and startup-promotion risk before you publish.
By Anthony Riera, founder and operator of Rankhog.
Subreddit guides combine public Reddit source URLs, captured rules, visible verification dates, and Rankhog's account-safety workflow.
Current public stats
Rules can change, so Rankhog keeps verification dates and the original public Reddit sources visible.
This community is for anything software related. People post about programs, tools, and software topics here. The rules make clear that hardware and tech support questions do not belong, and those should go to r/techsupport instead.
The rule called "Spam/Self-Promotion" is the one that will make or break you. It says you get a permanent ban if you promote your own software unless it is open source, with one exception. The exception is if you share on Wednesdays, use the appropriate flair, and provide something of value to the community rather than just the software. The rule named "Releases" also matters if you are posting about a new program or a big update, because it asks that the program be open source and fully usable without payments. The "Karma requirement" rule means a secret karma threshold exists, and the "Low Effort" rule means your post must be well written and formatted.
A good post here is either a genuine discussion about software or a respectful share of open source work. If you are a founder with open source software, you can share it directly, and the "Releases" rule suggests it should be fully usable without payments. If your software is not open source, you must wait until Wednesday, use the appropriate flair, and offer real value like a deal or a useful insight, not just a product link. Put time into your writing and formatting, since the "Low Effort" rule expects proper grammar and clean presentation.
Do not promote your own paid software outside of the Wednesday exception, because the "Spam/Self-Promotion" rule threatens a permanent ban. Do not share links or tutorials to copyrighted content without permission, and do not discuss software used for piracy or video downloading, as the "Piracy" rule forbids it. Do not troll or harass people, as the "Troll/Abuse" rule can lead to a permanent ban. Do not post hardware questions, since the "Visit r/techsupport Before Posting" rule sends those elsewhere. Do not make low effort posts with poor grammar or formatting, because the "Low Effort" rule asks for real time and effort.
Want the version that does not run out? Subscribers get unlimited tool runs and more careful checks before posting.
Get my free Reddit SEO auditStart your 3-day free trial. Card required. $99/month after trial. Next, connect a verified Reddit account; no strategy starts until you explicitly start Rankhog.
Only if it is open source, or if you wait until Wednesday, use the appropriate flair, and provide something of value beyond the software itself.
The threshold is secret and not shared, but it is not set very high. If your post is blocked, send a modmail to request a manual review.
No, the rules say to head over to r/techsupport for hardware or similar questions.
Releases should be for new programs or big updates, not minor version logs, and the program should ideally be open source and fully usable without payments.
Bootstrapped SaaS founders and solo software builders
A source-backed Rankhog guide to r/languagelearning: public rules, community context, posting fit, and startup-promotion risk before you publish.
Bootstrapped SaaS founders and solo software builders
A source-backed Rankhog guide to r/Spanish: public rules, community context, posting fit, and startup-promotion risk before you publish.
Bootstrapped SaaS founders and solo software builders
A source-backed Rankhog guide to r/chrome_extensions: public rules, community context, posting fit, and startup-promotion risk before you publish.