Build once.
Run the business.
Manage releases, access plans, and customer entitlements from one private workspace.
Continue with DiscordAccess is allowlisted by the platform administrator.Manage releases, access plans, and customer entitlements from one private workspace.
Continue with DiscordAccess is allowlisted by the platform administrator.Your releases, storefront plans, and live customer access at a glance.
Open a plugin to configure access plans and customers.
Who bought your plugins, when they purchased, and when each access period expires.
Everyone on this list gets every plugin you own, including plugins you publish later. Removing someone revokes what the list gave them; store purchases are not affected.
| Member | Plugins | Access until | Sessions | Added |
|---|
| Customer | Plugin / plan | Purchased / added | Access starts | Expires | Payment | Access period |
|---|
Every client running a plugin right now, and the launches that have already ended.
| Client | Plugin | Launched | Uptime | Last heartbeat | Plugin expires | State |
|---|
What the protection worker is building right now, and every release it has shipped.
| Started | Type | Stage | Generation | API | Duration | Outcome |
|---|
| Plugin | Version | Status | Detail |
|---|
Private GitHub sources are polled by immutable commit and artifact hash.
| Plugin | Version | Source | Status |
|---|
Connect accounts you control. Customer payments go through your provider; Raisin grants access only after a verified callback.
Stripe uses the endpoints below. Crypto callbacks are configured automatically when you connect.
Customers can put any of your card-payable plugins in one cart (several plans, or several copies) and pay once. Optionally reward bigger carts: a tier applies when the cart has enough different plugins that each reach the minimum spend, and the cart subtotal reaches the tier’s minimum. The best tier reached discounts every item in the cart.
Live resource usage on this host, and emergency start, stop and restart for the platform's services.
Resource usage is unavailable because this portal is not running on the Linux host.
| Mount | Usage | Used | % | Free |
|---|
Every action asks for confirmation, is recorded in the audit log, and is carried out by a root-side helper that only acts on its own allowlist.
| Requested | Action | By | Result |
|---|
Developers remain isolated; this view spans the whole platform.
Only active Discord IDs below can enter the customer store. Disabling an ID ends its existing store sessions immediately.
| Allowed Discord account | Status | Updated |
|---|
A customer who opens a payment dispute is banned automatically: plugin access from every developer ends and they cannot buy or claim plans. Lifting a ban restores their remaining access; disputed purchases stay revoked.
| Customer | Source | Reason | Banned |
|---|
| Customer | Source | Reason | Banned | Lifted |
|---|
| Developer | Role | Sources | Plugins | Status |
|---|