Rebutdesk documentation

What Rebutdesk is, the ways to run it, and where to find each part of the documentation.

Rebutdesk is an open-source helpdesk and chargeback tool for online stores. Every conversation with a buyer lands in a case: email, live chat, cases you open by hand, and cases created through the API. When you connect Stripe or PayPal, each new dispute opens in the buyer’s case (or joins the newest one that is not closed), so the messages you need as evidence are already next to the deadline.

From a case you can reply, add internal notes, track promises you made to the buyer, see the buyer’s payments, refund them, and build and submit dispute evidence. An optional AI assistant, using any OpenAI-compatible model you bring, answers live chat first, drafts replies and writes summaries.

Ways to run it

Rebutdesk needs PostgreSQL. The same code runs in two places:

  • Docker or plain Node. One process serves the console, the API, websockets for live updates, a timer for background work and, if you want, an SMTP listener for inbound mail. See Run with Docker.
  • Cloudflare Workers. The Worker serves the API and the console as static assets, live updates go through a Durable Object, background work runs from a cron trigger, and inbound mail can come from Cloudflare Email Routing. See Run on Cloudflare Workers.

If you do not want to host it, the hosted cloud runs at app.rebutdesk.com.

Pages

  • Run with Docker: compose setup, reverse proxy, prebuilt images, running on Node, upgrades and backups.
  • Run on Cloudflare Workers: bindings, building the console, migrations, secrets and deploying.
  • Configuration: every environment variable and binding, with defaults.
  • Sign-in and security: password and OAuth sign-in, two-step sign-in, passkeys, roles and permissions.
  • Email: receiving support mail over SMTP, HTTP or Cloudflare Email Routing, attachments, and what sending replies needs.
  • Stripe and PayPal: connecting payment accounts, the automatic webhook, the payments sidebar and refunds.
  • Disputes and evidence: how disputes reach cases, deadlines, the evidence PDF, submitting and accepting.
  • AI: bringing your own model, live chat answers, drafts, summaries and the knowledge base.
  • Plugins: the plugin SDK, adding a payment channel, and host extension points.
  • REST API and webhooks: API keys, endpoints and signed webhook deliveries.

Next: Run with Docker