Why people leave Tupperbox
Tupperbox sits at the centre of two overlapping communities on Discord: plural systems who use proxy bots to speak as different members of one body, and roleplay servers where one user runs multiple characters. The bot delivers the basics — register a “tupper” with a name and avatar, type a tag, and your message is reposted under that identity through a webhook. That has been the workflow since 2017.
The friction shows up at scale. Servers with active plural users run into Tupperbox’s narrow webhook quota. Roleplayers with large casts hit the per-user tupper cap. Multi-server members lose their identities when they cross between communities because Tupperbox stores most data per-server. And the bot’s response time during peak hours has been a recurring complaint in r/plural and tupperhouses for years.
PluralKit’s rapid feature growth between 2022 and 2025 reshaped the category. The seven Tupperbox alternatives below cover the modern proxy-bot space — the dominant PluralKit, a handful of forks and successors, one full successor (PolyPhony), and the small set of niche bots that still serve specific roleplay communities better than the mainstream pair.
Quick comparison
| Bot | Best for | Free plan | Paid plan | Standout feature |
|---|---|---|---|---|
| PluralKit | Plural systems with global identity | Yes | Donation only | Cross-server member identity |
| PolyPhony | Roleplay with rich profiles | Yes | $3/month | Character sheets attached to each proxy |
| Tupper | Streamlined Tupperbox fork | Yes | None | Faster response time on small servers |
| PluralKit self-hosted | Total control over data | Yes | Hosting cost | Run the bot on your own VPS |
| Multifurry | Furry RP community | Yes | $4/month | Strong custom species sheet support |
| RP Bot | Long-form roleplay | Yes | $3/month | Long-message handling with edit history |
| Pluralism | Therapeutic plural support | Yes | None | Built around plural mental-health workflows |
What Tupperbox does well, and where it stops
Three patterns repeat in the threads where plural systems and RP heavy users compare bots:
- Webhook latency. Tupperbox proxies messages through Discord webhooks, which is the only legal path. The latency spikes during peak EU/US evening hours can stretch to 2-3 seconds, which breaks fast roleplay scenes.
- Per-server data. Tupperbox stores tuppers and switching state per-server by default. Members in 20 servers re-register the same tuppers 20 times. This is the single biggest reason long-time users move to PluralKit.
- No system metadata. Plural systems often want to share system descriptions, member pronouns, and front history publicly. Tupperbox has minimal support for this; PluralKit built it in from the start.
- Cap walls on big casts. RP users with 30+ characters hit per-user limits. The bots designed for plural systems tend to have generous caps; the RP-leaning bots ship deeper character sheets at the price of paid tiers.
- Backup and export. Tupperbox added basic export in 2023, but the format is bot-specific and importing back into a different bot is unreliable.
The Tupperbox alternatives
1. PluralKit, best modern proxy bot for plural systems
PluralKit is the bot most plural systems run in 2026. It treats the system itself as the first-class object: members live under a system, the system has a name and description, switches are tracked across servers, and a member registered once works in every server that has PluralKit added.
Front tracking is built in. Members can have pronouns, descriptions, avatar URLs, colours, and front-status timestamps. The bot supports message editing, deletion, and reposting after a typo — all preserved through Discord’s webhook constraints.
Where it falls short: No paid tier, so the development pace depends on volunteer time and donations. Some advanced sheet features that RP-focused bots ship are not there. The dashboard is on the bot’s website, which is functional but plain.
Pricing:
- Free: every feature
- Optional: donate via Patreon, no feature gating
- vs Tupperbox: free where Tupperbox is free, deeper on plural-system metadata, faster in our testing
Migrating from Tupperbox: PluralKit ships a Tupperbox import command that pulls tuppers across as PluralKit members. Webhook proxies remain attached. The conversion is one of the cleaner migrations in the bot ecosystem.
Add to server: pluralkit.me
Bottom line: Pick PluralKit if you are a plural system or an active RP user with characters that live in more than one server.
2. PolyPhony, best for roleplay with rich profiles
PolyPhony was built around the roleplay use case and treats each proxy as a character with a full profile rather than a switch. Character sheets attach to each proxy and can include backstory, stats, image galleries, and per-server flags.
The bot supports paged character lists, character search, and templates for common RPG systems (Pathfinder, D&D 5e, World of Darkness). For long-form roleplay servers, the depth is noticeable.
Where it falls short: Less ideal for plural systems because the model centres on individual characters rather than a unified system. Free tier limits character count.
Pricing:
- Free: up to 15 characters per user, basic sheets
- Premium: $3/month per user, unlimited characters, full sheet templates
- vs Tupperbox: paid where Tupperbox is free, richer character data, narrower target audience
Migrating from Tupperbox: Tuppers can be imported as characters, but sheets need to be filled in manually. The migration is straightforward; the sheet enrichment is the work.
Add to server: polyphony.app
Bottom line: Pick PolyPhony if you run roleplay characters with deep backstories and want sheets that show up on demand.
3. Tupper, best lean Tupperbox fork
Tupper is a community-maintained fork of Tupperbox that strips back the codebase, fixes the slow webhook queue, and keeps the command syntax identical. Servers with active Tupperbox users can switch to Tupper without retraining muscle memory.
The proxying logic and identifier system are unchanged. The differences are under the hood: faster response times during peak hours, fewer dropouts on large servers, and a more recent codebase.
Where it falls short: Smaller community, fewer guides, less name recognition. No major new features beyond what Tupperbox offered.
Pricing:
- Free: every feature
- vs Tupperbox: same surface, faster execution, smaller community
Migrating from Tupperbox: Identical command set. Tupperbox export imports directly into Tupper.
Add to server: tupper.gg
Bottom line: Pick Tupper if you like Tupperbox’s design and only want the speed gap closed.
4. PluralKit self-hosted, best for full data control
PluralKit self-hosted runs the same PluralKit codebase on a server you control. For systems that do not want member data on someone else’s infrastructure, this is the only bot on the list where the data path is yours end to end.
The repo is open source on GitHub, the dependencies are a Postgres database and a Discord bot token, and the deployment runs comfortably on a $5-10/month VPS. The maintained docker-compose stack is the easiest path.
Where it falls short: Hosting cost and maintenance time replace the free hosted bot. Multi-server identity only works if other servers also use your instance, which is rare. Most users run hosted PluralKit because the data sensitivity does not justify the overhead.
Pricing:
- Free codebase
- Hosting: a small VPS ($5-10/month) and a domain optional
- vs Tupperbox: completely different model, full control vs convenience
Migrating from Tupperbox: Self-hosted PluralKit ships the same Tupperbox import. The migration path is the same as hosted PluralKit.
Add to server: Repo at github.com/PluralKit/PluralKit
Bottom line: Pick self-hosted PluralKit only if data sovereignty is a real concern. For most users, hosted PluralKit is the simpler answer.
5. Multifurry, best for furry RP communities
Multifurry is the bot many furry roleplay servers run, partly because it ships custom species fields, anatomy templates, and the kind of profile data that RP servers in this space ask for. The proxy engine works the same as PluralKit, but the schema around each character is built for the community.
Species, breeds, custom anatomy fields, fursona references, and inter-character relationship flags are all first-class.
Where it falls short: Niche by design. Mainstream RP and plural-system users get nothing extra from the schema. The community is small enough that bot downtime hits harder.
Pricing:
- Free: basic proxying, limited custom fields
- Premium: $4/month per user for full schema and image hosting
- vs Tupperbox: different target audience, much deeper for that audience
Migrating from Tupperbox: Multifurry imports Tupperbox exports, then prompts to fill in the species fields.
Add to server: multifurry.bot
Bottom line: Pick Multifurry if your server is a furry RP space. Otherwise, PluralKit or PolyPhony is the better default.
6. RP Bot, best for long-form roleplay scenes
RP Bot is built around message volume. Long-form roleplay scenes generate posts of 1,500-2,000 characters, multiple paragraphs, embedded references to past events. RP Bot handles this with split-message support, edit history (so RP partners can see how a post evolved), and a scene-bookmark system that lets servers tag long arcs for later retrieval.
The proxy core works the same as Tupperbox, but the surrounding tooling targets long-form writing rather than fast-scene character switching.
Where it falls short: Light on plural-system features. The sheet system is thinner than PolyPhony’s. Long-message handling is the unique value; everything else is solid but not best in class.
Pricing:
- Free: 25 characters, basic split-message support
- Premium: $3/month per user, unlimited characters, scene bookmarks, edit history
- vs Tupperbox: same audience for one slice (roleplay), narrower scope, more useful for one specific writing style
Migrating from Tupperbox: Tupperbox export imports as characters. Long-message tooling activates on the next message you send.
Add to server: rpbot.gg
Bottom line: Pick RP Bot if your server runs slow, long-form roleplay arcs.
7. Pluralism, best for therapeutic plural workflows
Pluralism is the most specialised bot on the list. It is built for plural systems whose primary need is mental-health-adjacent workflow support: front history with timestamps and triggers, switch logging, integration with therapy journals, optional crisis-mode flags that pin a specific member.
The proxy core is similar to PluralKit. The difference is the workflow assumption.
Where it falls short: The community is small, and the bot is opinionated. Servers that just want proxying without the workflow scaffolding will find it heavier than needed.
Pricing:
- Free: every feature
- vs Tupperbox: very different framing, narrower audience, free
Migrating from Tupperbox: Tupperbox export imports as system members. Therapy-related fields stay empty until filled in.
Add to server: pluralism.bot
Bottom line: Pick Pluralism if the plural-system workflow you want is shaped by therapy or self-care use rather than RP or social use.
How to choose
- You are a plural system in multiple servers: PluralKit.
- You run a deep RP cast with character sheets: PolyPhony.
- You like Tupperbox and want speed without retraining: Tupper.
- You need full control of your data: PluralKit self-hosted.
- Your server is furry RP: Multifurry.
- Your server runs long-form roleplay: RP Bot.
- Your plural workflow is therapeutic: Pluralism.
Stay on Tupperbox if your one server uses the bot lightly, your tuppers are few, and you do not need any of the extra features above. Tupperbox still works for that case.
FAQ
What is the best free Tupperbox alternative? PluralKit. Every feature is free, the migration from Tupperbox is one command, and the community is the largest on this list.
Can I import my tuppers to PluralKit? Yes. PluralKit has a built-in pk;import tupperbox command that pulls your registered tuppers across and preserves names, avatars, and proxy tags.
Does PluralKit work in every server that had Tupperbox? Almost always. PluralKit uses the same Discord webhook system, so server admins do not need to change permissions beyond adding the bot.
Why are some bots free and others paid? Webhook proxying is cheap, but storage, sheet templates, and image hosting are not. Paid bots are usually charging for the surrounding scaffolding (sheets, hosting, advanced search) rather than the proxy itself.
Can two bots run in the same server? Yes, but it can confuse users. Most servers settle on one proxy bot to keep the muscle memory consistent.
Will my Tupperbox tuppers still work after I add a new bot? Tupperbox keeps working until you remove it. The recommended migration is: add the new bot, import your tuppers, test for a week, then remove Tupperbox.