One subscription, access on every platform you run
Arcalotl sells logical access, not a role on one server. A single purchase can grant a Discord role, a Fluxer role, membership of a Telegram chat and a Hytale server package at the same time.
Most community billing tools grant access on a single platform. Arcalotl grants an entitlement, which is stable logical access a member holds, and then applies that entitlement as benefits on every platform the community has connected.
A community can connect a Discord server, a Fluxer server, a Telegram group and a Stoat server at the same time. Plans and subscriptions belong to the community rather than to any one server, so one purchase can grant access on all of them.
The price does not change with the number of connected platforms. Arcalotl costs $0/month plus 2% of each successful payment, charged on the creator's own Stripe account through Stripe Connect direct charges. Stripe's own processing fees (2.9% + $0.30) apply on top.
One entitlement carries many benefits
An entitlement is one named unit of access, such as VIP access, that can carry benefits on several platforms at once. Its benefits are actions Arcalotl performs: a Discord role, a Fluxer role, membership of a Telegram chat, or a Hytale server package. You define the entitlement once and attach plans and donations to it.
The ledger is the source of truth
Arcalotl records who holds what in a member-entitlement ledger, and that ledger is authoritative. Platform benefits are applied from that state rather than being the state. A temporary platform API failure does not change whether the member logically holds the entitlement, so nobody loses access because a role assignment failed once.
Every entitlement has a stable external key
Each entitlement carries a stable external key, such as vip-access, for API and webhook consumers. Your integration matches on that key instead of a platform role ID. Renaming a Discord role, or moving the same access to a second platform, does not change the key your code checks.
One community can connect several platforms
A community is the thing you monetize: its plans, subscribers and billing history. It can have more than one connected platform, including a second Discord server, a Telegram group, a Fluxer server, or a Stoat server. There is one plan catalog, one billing record per member, and one dashboard across all of them.
Members link identities with /link
A benefit needs a platform identity, so a Discord buyer links their Telegram account before Arcalotl can add them to a Telegram chat. The member runs /link on the platform where they already have access and redeems the code on the platform they want to add. Linking works in either direction, and Arcalotl applies the benefits the member already holds as soon as the link completes.
Several sources can support one entitlement
More than one plan tier or donation can provide the same entitlement. Ending one of those sources does not revoke access while another active source remains. That makes it safe to move a member between tiers, or to run a donation alongside a subscription, without a gap in access.
Editing an entitlement converges existing members
Before you save a change that affects active members, the dashboard shows the benefits being added or removed, the active subscribers and purchasers affected, and the members missing an identity on a newly affected platform. Confirming publishes durable reconciliation work. Members with a linked identity converge immediately, and the rest converge once they link.
Connecting a platform later is additive
Existing entitlements do nothing on a newly connected platform until you add a benefit for it. Add the role, chat membership or server package to each entitlement that should span the new platform, and members with linked identities converge automatically. Existing subscriptions keep billing unchanged.
Your own application can enforce the same state
External entitlements let an operator-controlled application receive and enforce the same logical access through signed webhooks. Arcalotl emits member.entitlement.granted, member.entitlement.updated and member.entitlement.revoked from the same authoritative ledger, each carrying the entitlement key and an increasing revision number so out-of-order retries can be ignored safely.
What an entitlement benefit does on each platform
| Platform | Benefit Arcalotl applies |
|---|---|
| Discord | A role on the connected Discord server. |
| Fluxer | A role on the connected Fluxer server. |
| Telegram | Membership of the connected Telegram chat. |
| Hytale | A server package configured under Game Servers. |
| Stoat | Roles on the connected server. Stoat is live. |
How one purchase becomes access everywhere
A buyer starts checkout from a command in one of your community platforms, or from a checkout link you create through the API. Payment goes to your own Stripe account through Stripe Connect direct charges.
When payment activates the subscription or purchase, the member entitlement becomes active in the ledger and Arcalotl reconciles its benefits. Each benefit is applied on the platform where the member has a linked identity. Benefits for platforms the member has not linked yet are applied the moment they link.
When the last active billing source ends, the entitlement is revoked and its benefits are removed. Removing a benefit removes that platform action unless another active entitlement still requires the same action, so overlapping access is not cut off by accident.
Questions
Read next
Sell access once, grant it everywhere
Connect your platforms, define an entitlement, and attach it to a plan. $0/month plus 2% of each successful payment, paid out on your own Stripe account.
Create a community