Can I mention my own tool or service if it is relevant to the architecture discussion?
No, the rule No promotion of personal/business services bans promotion of services offered by an individual or company.
A source-backed Rankhog guide to r/softwarearchitecture: 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 people who want to talk about designing, structuring, and optimizing software systems. The description says you should share insights on architectural patterns, best practices, and real-world experiences. Based on the rules, the room is meant for architecture discussion only, with no room for services, jobs, or crypto talk.
The rule called No promotion of personal/business services is the one that will end your marketing effort before it starts, because it bans promotion of services offered by an individual or company. The rule named No job posts is equally firm, covering job advertisements, links to job boards, resumes, personal sites aimed at getting a job, and any solicitation of employment. The rule titled No AI Generated Posts tells you that anything the community suspects was written by a tool will be removed. The rule called Keep posts related to Software Architecture is the relevance gate, and the rule named No flair abuse warns that using the wrong flair on purpose leads to punitive action. The rule titled No cryptocurrency, zero tolerance is absolute, though it carves out blockchain as a permitted topic.
A good post here is something you wrote yourself, in your own words, about a real architecture problem or decision you faced. Talk about a pattern you chose, a tradeoff you weighed, or a structural challenge you worked through, without naming or linking to your product. The goal is to share an insight that an architect or engineer would find useful on its own. If your experience happens to involve a tool you built, focus on the architectural thinking, not the tool. Keep the post squarely about software architecture so it clears the relevance rule.
Avoid any form of promotion, because the rule No promotion of personal/business services bans it outright. Avoid job posts of any kind, including ads, job board links, resumes, and personal sites aimed at getting work. Avoid AI generated content, because the rule No AI Generated Posts says such posts will be removed. Avoid cryptocurrency posts entirely, since the rule No cryptocurrency, zero tolerance allows no exceptions, though blockchain as a topic is fine. Avoid off-topic posts, because the rule Keep posts related to Software Architecture requires every post to stay on subject. Avoid using the wrong flair on purpose, because the rule No flair abuse says it will result in punitive action.
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.
No, the rule No promotion of personal/business services bans promotion of services offered by an individual or company.
No, the rule No job posts covers job ads, job board links, resumes, personal sites aimed at getting a job, and any employment solicitation.
No, the rule No AI Generated Posts says AI generated posts will be removed because they do not bring value to the community.
Blockchain as a topic is allowed, but cryptocurrency is banned with zero tolerance.
Yes, as long as the post is directly about software architecture and does not promote a service.
Technical product and developer communities
A source-backed Rankhog guide to r/technology: public rules, community context, posting fit, and startup-promotion risk before you publish.
Technical product and developer communities
A source-backed Rankhog guide to r/programming: public rules, community context, posting fit, and startup-promotion risk before you publish.
Technical product and developer communities
A source-backed Rankhog guide to r/learnprogramming: public rules, community context, posting fit, and startup-promotion risk before you publish.