How I built a RAG-grounded Discord brain in 5 weeks (solo, ESL, no funding)
Peng, a solo founder and ESL teacher, developed Acortia, a Discord-native tool designed to improve knowledge retrieval within communities. The product aims to address the issue of lost information in Discord threads by allowing users to save and ask questions about previously shared content. Acortia is set to launch in mid-June for $99 per month, with a focus on providing grounded, cited answers from the server's saved knowledge.
- ▪Acortia is a tool that helps Discord communities retrieve institutional knowledge effectively.
- ▪The product features three main commands: /save, /ask, and /sources.
- ▪Peng built Acortia without funding or a team, working on it during nights and weekends.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/incultnitollc/how-i-built-a-rag-grounded-discord-brain-in-5-weeks-solo-esl-no-funding-1fgh |
| Publication time | Wed, 03 Jun 2026 06:19:18 +0000 |
| Retrieval time | 2026-06-03T06:41:57.977Z |
| Last seen | 2026-06-03T06:41:57.977Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | IT7S21SMLIDy |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3914325) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } pengspirit Posted on Jun 3 How I built a RAG-grounded Discord brain in 5 weeks (solo, ESL, no funding) #discord #rag #supabase #indiehackers Day 14. The fourth time. A user in our Discord asked, for the fourth time that week, the same question. Same wording, almost. The first three answers were buried somewhere in a thread, a pinned message, and a Notion page nobody bookmarked. A mod typed it out again. I watched it happen, opened Cursor, and started typing.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
