Pre-launch

Use cases

Five jobs, one workspace.

SwarmUp is a community operations workspace for Discord and Telegram. These are the specific jobs it is built to do, each with its own page, and every one of them runs on the same rulebook and leaves the same kind of record.

Pick the one you came for

What are you trying to fix?

Each page below answers a different question, but they describe one product. Connecting a second job does not mean adopting a second tool, a second policy or a second bill.

  • Discord moderation bot

    Moderation with a record you can show somebody

    For a server where the moderation is already automated and the arguments about it are not. Every action carries its evidence, its owner and its appeal, high-risk calls wait for a person, and reversals are recorded rather than quietly applied.

  • Discord anti-raid bot

    Raid and anti-nuke cover that survives review

    For the twenty minutes of an attack and the week of questions afterwards. Raids come from outside and nukes come from inside; both leave a record here, and neither gets to trigger an automatic permanent ban on a pattern match.

  • Discord anti-scam bot

    Scam and impersonation signals, raised for a person

    For communities where impersonation is the standing threat. The signal is surfaced and the evidence is kept; the judgement about whether an account is impersonating somebody is not one the AI is allowed to make on its own.

  • Telegram captcha bot

    A door that reports what it did

    For a group taking automated joins. A captcha is the cheapest filter you own and the one most likely to quietly turn away a real member, so here it is an action with a record, an appeal and an undo rather than a gate and a counter.

  • Telegram verification bot

    Entry decisions that keep their reason

    For groups where the verify prompt itself has become the attack. Cloned bots inherit a habit your members were trained into, and the part you can control is whether anybody can establish afterwards what the real system did.

Why they are one product

The jobs share a rulebook.

Do I have to choose between these, or can I run several?

You can run any of them, and you can start with one. Connect one community, activate one agent or workflow, and expand when you are ready. Servers, groups and seats are unlimited on every plan including the free one, so adding a second job or a second community is not a new line on the bill.

What do all five have in common?

One Community Blueprint holds the rules, tone, knowledge and goals you approve, and nothing becomes live configuration until a person reviews and saves it. Every action any of these jobs takes carries its evidence, its owner and its appeal. And the six limits on what the AI may do without you apply to all of them equally.

Where does SwarmUp stand today?

SwarmUp is not open to the public yet. Moderation is the core of the product and it runs today. Engagement and rewards are still in testing. Plans and prices are final, and nothing is charged before the workspace opens.

One email, when it opens

We will not waste the one email.

We are not naming a launch date until we can hold it. What you get for an address is a single message the day the workspace opens, and the same plain account of where the product stands on that day.