Navigate this article
AstralBot grew from the need for an open foundation for people who want to build a Discord sales community without starting with infrastructure. The installation combines idempotent server setup, product operations, assisted purchases, and private delivery in a flow each community can adapt.
Project intent
The goal is an understandable foundation: independent modules, simple SQLite persistence, Components V2 interfaces, and clear extension points for rules, providers, and delivery formats.
AstralBot is my MIT-licensed open-source foundation for creating and operating Discord sales communities. It brings community setup, panels, private purchase tickets, configurable payments, and digital delivery into one bot, with an emphasis on readable code, auditable operations, and per-server adaptation.
WHAT THE FOUNDATION ORGANIZES
These are the main elements organized in this workstream.
- Idempotent creation of categories, text channels, voice rooms, and roles
- Welcome messages, versioned rules, autorole, select roles, logs, and chat cleanup
- Product catalog with title, description, price, images, links, requirements, terms, and languages
- Pix/manual payments and external checkout, with signed Mercado Pago webhooks when configured
- Private purchase ticket, administrator confirmation, DM delivery, and rating request
- Delivery recovery, persisted tasks, temporary links, and consistent backups
- Encrypted sensitive data and SQLite for a simple, local, extensible installation
WHO IT SERVES
Creators, communities, and developers who want an open foundation to sell digital products, organize support, and adapt operations to their own server.
How this experience can be applied
The base can support digital products, courses, software, subscriptions, and services. Sellers configure Pix or external checkout, buyers follow the process in a private ticket, and delivery only closes after administrator confirmation, preserving history for support and ratings.
What to evaluate before applying a similar solution
These criteria help turn the project reference into a decision that fits the company or community context.
- Which community resources must be created idempotently and who can administer them.
- How payments, administrator confirmation, private delivery, and recovery will be audited.
- Which data can remain in SQLite and which needs retention, encryption, or external storage.
- How multilingual products, files, URLs, and redemption codes will be versioned.
- How a server can adapt modules without breaking security rules.
INFRASTRUCTURE & LICENSE
Node.js 24+, TypeScript, discord.js 14, Components V2, SQLite, Fastify, Zod, Vitest, and the MIT license.
Sources and further reading
This material presents my working approach and is educational. The right solution depends on the context, risks, and responsibilities of each project.
Share