Replies within 24 hours · written by a human

Contact support.

Most questions have a faster answer in the FAQ or community — try those first. For private issues, billing, account recovery, or anything you would rather not post in public, email support@remio.net and we will reply within one business day. No tickets, no queues, no chatbot in the middle.

Four ways to reach us

Pick the channel that fits the question.

Each row is a real contact channel with a real response window. Use email for anything private, the community for show-and-tell and tips, GitHub for reproducible bugs, and X for short public notes.

Email · primary support@remio.net
Response SLA Within 24 hours, weekdays
Use for Bug reports, billing questions, account recovery, anything private, security disclosures
Include App version (Help → About), host OS, client OS, exact steps you tried, and any error text
Discord · community discord.gg/remio
Response SLA Often within an hour during waking hours
Use for Setup help, tips and tricks, feature ideas, asking other users how they wired things up
Include A clear one-line summary in the channel title, then your platforms and what is happening
GitHub · issues github.com/remioapp
Response SLA Triaged within two business days
Use for Reproducible bugs, regressions, performance reports, anything other users can verify
Include Reproduction steps, expected vs actual, build number, and a log excerpt if you have one
X · @remioapp x.com/remioapp
Response SLA Best-effort, daily
Use for Short public notes, release questions, signal-boosting, screenshots of cool setups
Include Avoid posting account details, PINs, or private logs — switch to email for those
Before you contact us

Five things that resolve most tickets.

A short triage list. Most people who follow these five steps find the answer in step one or two — and the people who do not give us enough context in step five to fix things on the first reply.

  1. 01

    Check the FAQ.

    The FAQ covers pairing, network ports, latency tuning, security model, and the most common gotchas. Skim it first — most questions have a 90-second answer already written. Open the FAQ →

  2. 02

    Search the help articles.

    If the FAQ is too short, the help section has longer walkthroughs: install, pair, troubleshoot, system requirements. Search by verb — install, pair, fix, configure. Open help →

  3. 03

    Find your app version.

    Open Remio, click Help → About on the host or Settings → About on the client. Copy the version string and the build number — both matter, because we ship fixes incrementally.

  4. 04

    Note your host and client OS.

    A bug on macOS 14 may not exist on macOS 15. Tell us both sides — for example, host on macOS 15.4 and client on iPadOS 18.2 — so we can reproduce on the same combination.

  5. 05

    Describe what you were doing.

    Exact steps, expected outcome, actual outcome, and any error text — copy-pasted, not paraphrased. The more concrete the report, the faster the fix lands in the next build.

One inbox · one human · one reply

We read every message that lands in support@remio.net.

No ticket queue, no chatbot in the middle, no escalation tier. The same person who writes the app reads the email. Bring us a reproducible bug, an honest question, or a feature idea — we will reply within a business day.

Or join the community on Discord and GitHub. Public, helpful, and usually faster than email.