YourBot gives communities control over their Discord bot’s identity, server structure, feature set, plugin permissions, updates, custom code, data retention, and day-to-day operation—without requiring the community to host the bot itself.
“Control” should mean more than changing an avatar. Server owners should decide what the bot is called, which workflows are active, what plugins may access, when updates are adopted, how custom features behave, and what happens to stored data.
YourBot brings those decisions into one managed platform through a custom bot identity, Start Your Server, ten built-in services, the plugin marketplace, the AI Plugin Builder, and the Python SDK.
Editorial disclosure: This guide is published by YourBot.gg. It explains the control YourBot provides while being clear about the limits of a managed platform.
What “Control” Means in YourBot
| Area of control | What YourBot provides |
|---|---|
| Identity | Your own Discord application name and avatar |
| Server design | AI-assisted channels, roles, permissions, content, and service setup |
| Feature selection | Ten built-in services that can be enabled or disabled per server |
| Plugin access | Capability and external-domain approval before installation |
| Updates | Managed updates, version pinning, and renewed consent for expanded access |
| Custom behavior | Plain-language plugin generation plus direct Python development |
| Data | Documented retention, transcript deletion, server-data deletion requests, and tenant isolation |
| Operations | Managed hosting, runtime monitoring, dashboards, and public platform status |
The goal is not unrestricted access to the underlying servers. The goal is practical control over the Discord experience while YourBot handles the infrastructure behind it.
Control the Bot Identity Members See
Every YourBot subscription covers one server and includes all ten built-in services, a custom bot identity, and marketplace access. Marketplace plugins may have separate per-server pricing set by their developers.
To use a custom identity, the server owner creates an application in the Discord Developer Portal, chooses the bot name and avatar, enables the required intents, and connects the token through YourBot.
YourBot currently recommends:
- Server Members Intent
- Message Content Intent
- Presence Intent disabled
The connected token is encrypted at rest and is not displayed back in plaintext. The administrator remains responsible for keeping it private and resetting it immediately if it is exposed.
Members see one community bot identity across Welcome, Tickets, Sentinel, events, LFG, marketplace plugins, and custom SDK features.
Read the complete custom branded Discord bot guide for the setup process.
Control the Server Structure With Start Your Server
A bot can only work as well as the channels, roles, and permissions around it.
Start Your Server lets an administrator describe the community in ordinary language:
Reorganize this server for a growing gaming community. Keep our existing
member and staff roles. Create a clear welcome area, private support,
scheduled events, LFG, temporary voice rooms, moderation logs, and analytics.
New members should verify before seeing the main community. Do not delete
or rename the existing setup until staff have tested the replacement.
The builder can draft categories, channels, roles, permission overwrites, starter content, and suitable YourBot settings.
Review before applying
The proposal appears before anything changes in Discord.
Administrators can inspect every queued operation, refine the plan through chat, and use See it as to preview what a normal member or staff role would see. The safety check can flag onboarding and permission problems, such as newcomers landing in an empty server.
Keep a way back
Builds are add-only by default. Deletions require explicit selection and confirmation.
Before applying changes, YourBot creates and downloads a server snapshot. Each operation is logged, the completed build can be undone, and safely running the design again applies only what remains missing.
Configure services with the structure
Start Your Server can also:
- Post a Tickets panel
- Connect Group Finder to an LFG channel
- Create a join-to-create voice lobby
- Enable Sentinel raid protection
- Configure Welcome roles and cards
- Publish starter welcome and rules content
This lets communities design the server and bot as one system.
Start Your Server is not an automatic importer for another provider’s XP history, cases, transcripts, or analytics records. It creates the target structure and YourBot configuration.
Control Which Built-In Services Are Active
YourBot includes ten built-in services:
- Sentinel moderation
- Tickets
- Analytics
- Beacon Events
- Group Finder
- Join-to-create voice channels
- Welcome
- Announcements
- Giveaways
- Social Feeds
Each service can be enabled or disabled per server and configured from its own dashboard page.
A support community may emphasize Tickets and Analytics; a gaming guild may prioritize Beacon, Group Finder, voice rooms, and Sentinel.
“All in one” does not have to mean everything is switched on. The community chooses the smallest feature set that supports its actual workflow.
Control What Marketplace Plugins Can Do
The YourBot Marketplace lets communities install specialist features through the bot already in the server.
Before installation, administrators can review the developer, description, commands, screenshots, pricing, version history, requested capabilities, and outside domains.
Capability approval
Plugins declare the platform actions they need, such as:
- Sending messages
- Reading message content
- Managing roles
- Creating channels
- Applying moderation actions
- Using key-value or SQL storage
YourBot presents capability risk tiers during installation. If a plugin attempts an action that was not requested or approved, the runtime blocks it.
External-domain approval
Marketplace plugins have no direct network access. External HTTP and WebSocket requests use platform-controlled interfaces and declared domains.
A game-statistics API may be reasonable; an unrelated tracking domain deserves closer review.
Technical isolation
YourBot’s security documentation states that marketplace plugins run in separate locked-down containers with:
- Networking disabled
- A read-only filesystem and limited scratch space
- No root access
- CPU and memory limits
- Per-server tenant isolation
- A platform-wide kill switch for reported problems
Every version receives automated validation, and a new developer’s first publication receives human review.
These controls reduce risk, but administrators must still judge whether the requested access is appropriate.
Control Plugin Updates and Rollback
Installed marketplace plugins use managed updates by default, but the server owner is not required to accept every published version immediately.
Administrators can pin any published version, which disables automatic updates for that installation.
If a new version adds a capability or external domain, the update pauses until the administrator approves the expanded access. The existing version continues running until that decision is made.
This prevents a routine update from silently changing the plugin’s permission contract.
Uninstalling a marketplace plugin stops the feature. Its isolated plugin data is retained briefly for recovery and deleted after seven days under the current marketplace policy.
Control Custom Features With the AI Plugin Builder
When the built-in services and marketplace do not contain the required workflow, the AI Plugin Builder can create a YourBot SDK plugin from a written specification.
Create a volunteer-application plugin. Applicants submit their experience,
availability, interests, and private contact details.
Let administrators choose the reviewer role and review channel. Keep private
answers visible only to reviewers, prevent duplicate applications, store
status per server, and add a dashboard for notes and decisions.
The builder can first draft the commands and storage plan. Creators choose a build budget, and prepaid credits are charged according to token use.
The source, manifest, files, and commands remain visible during generation. Validation checks structure, imports, capabilities, command consistency, and parse errors.
Creators can request fixes, inspect or download the files, and continue development through the SDK.
A committed version can be dev-installed on a managed server. Current test installs expire after 24 hours, support up to three active installations, and provide live logs and events.
The community can inspect and test the feature before members rely on it.
Give Developers Direct Control With the SDK
The YourBot SDK is the direct development path.
pip install yourbot-sdk
yourbot new my_plugin
yourbot dev
yourbot validate
The documented SDK uses sandboxed Python and supports Discord events, commands, components, schedules, voice updates, storage, Discord actions, controlled external APIs, metrics, and dashboards.
Developers can use:
- Manifest dashboards for forms, tables, charts, statistics, and settings without a custom frontend
- Iframe dashboards for custom HTML, CSS, and JavaScript interfaces
YourBot handles Gateway connectivity, command synchronization, hosting, per-server storage, encrypted secrets, installation, updates, marketplace distribution, and billing infrastructure.
The developer controls the product logic while YourBot supplies the surrounding platform.
Control Data Retention and Deletion
YourBot’s privacy documentation explains what is stored and for how long.
Current controls include:
- Analytics raw-event retention of 90 days by default, configurable from 7 to 365 days depending on the plan
- Ticket transcripts that administrators can delete from the dashboard
- Server-data deletion requests
- A 30-day grace period after bot removal before most server data is permanently deleted
- Per-server logical data isolation
- Marketplace plugin data deleted seven days after uninstall
Moderation history remains while the bot is installed and can be removed through a server-data deletion request.
Some control remains process-based rather than self-service. Communities with specific export, deletion, or residency requirements should review the current Legal page and contact YourBot before deployment.
Keep Operational Control Without Self-Hosting
YourBot hosting runs the bot and plugins on managed infrastructure.
Communities do not need to rent a VPS, maintain a Gateway process, deploy containers, operate a database server, or restart the bot after each plugin update.
YourBot publishes platform uptime and incident history on a public status page. The dashboard also exposes the custom bot’s runtime state.
Managed hosting creates platform dependence: an outage can affect several workflows together. Keep Discord’s native safeguards configured and maintain manual fallbacks for critical moderation and support.
Where YourBot’s Control Has Boundaries
YourBot provides operational and product control within a managed ecosystem. It does not provide unrestricted access to the underlying runtime.
Important limits include:
- YourBot remains in beta.
- Plugins operate within the SDK, sandbox, capabilities, and resource limits.
- Plugins do not receive direct network or unrestricted operating-system access.
- One subscription covers one server.
- Marketplace plugins may add separate costs.
- YourBot has not yet completed an independent third-party security audit and currently holds no compliance certifications.
- A YourBot SDK plugin is not automatically a standalone Discord bot project.
A standalone bot is the better choice when the organization needs unrestricted architecture, native binaries, direct infrastructure control, or operation outside the YourBot ecosystem.
Control is strongest when the boundaries are clear.
Frequently Asked Questions
Does YourBot Let Me Use My Own Bot Name and Avatar?
Yes. Every YourBot subscription includes a custom bot identity for its covered server. You create the Discord application and connect its token through the dashboard.
Can I Choose Which Features Run?
Yes. Built-in services and marketplace plugins can be enabled or disabled per server.
Can a Plugin Gain New Permissions Through an Update?
Not silently. Adding a capability or external domain pauses the update until the server administrator approves the additional access.
Can I See and Edit AI-Generated Plugin Code?
Yes. The Plugin Builder exposes the source and files, supports downloads, and produces a plugin that developers can continue through the SDK.
Can I Delete My Server’s Data?
YourBot provides dashboard deletion for certain records, including ticket transcripts, and accepts requests to delete server data. Review the current retention policy for exceptions required by law, fraud prevention, or financial record-keeping.
Do I Need to Host the Bot Myself?
No. YourBot operates the custom bot and plugin runtime on managed infrastructure.
Final Verdict
YourBot gives communities control over the parts of a Discord bot that affect them most: identity, structure, features, permissions, versions, custom behavior, data retention, and administration.
Start Your Server controls how the bot fits into the community. The built-in services let administrators activate only the workflows they need. The marketplace makes plugin access and updates visible. The AI Plugin Builder exposes generated source and testing, while the SDK gives developers a direct path to refine the product.
YourBot handles the infrastructure, but the community remains responsible for the decisions that shape its Discord experience.