ARC runs your rooms on your own network without needing the internet. Integrations are the deliberate exceptions — the handful of outside services you may want ARC to talk to. Reaching your control page from home. Getting a severe-weather warning on screen. Speaking hints in a cloud voice. Mirroring your staff chat into Slack.
You’ll find them at System → Integrations, under the heading “Connect ARC to the outside services you use.” Each service is a card. Click a card to open its setup panel, fill in what it asks for, and close it — most settings save themselves as you go.
What’s available
The cards are listed alphabetically, the same order you’ll see them on screen.
| Integration | What it does | Notes |
|---|---|---|
| Anthropic | Writing suggestions — helps you rewrite a hint. Uses your own Anthropic account. | Beta |
| Discord | Mirrors a Discord channel and an ARC chat channel in both directions. | Beta · needs Cloud Connect and Portal setup |
| ElevenLabs | Cloud text-to-speech. Brings realistic AI voices into ARC for hints and narration. | |
| OpenAI | Writing suggestions — helps you rewrite a hint. Uses your own OpenAI account. | Beta |
| Slack | Mirrors a Slack channel and an ARC chat channel in both directions. | Beta · needs Cloud Connect and Portal setup |
| Tailscale | Remote access. Reach your whole ARC setup securely from anywhere. | |
| UniFi Protect | Switches which camera view a UniFi Viewport screen shows when staff pick a game. | Beta |
| Weather | Pulls active severe-weather warnings and watches from the US National Weather Service. | Beta |
What “Beta” means here
A card marked BETA is a feature that ships and works today but is still being refined. Opening its panel shows a short notice saying so. Nothing is locked or hidden — it just means the setup or the behavior may still change, so give it a test run before you lean on it for a busy Saturday.
Everything on this page is optional. ARC runs your rooms perfectly well with none of these connected.
Reading a card’s status
Every card shows the same short status word under its name, so you can scan the page and see what’s set up.
| Status | What it means |
|---|---|
| Checking… | ARC is still working out where this one stands. |
| Active | Set up and working. |
| Disabled | Set up, but currently turned off. |
| Not configured | Nothing has been set up yet. |
| Reconnecting | Set up, but ARC is trying to re-establish the connection. |
| Unavailable | ARC couldn’t read this integration’s state just now. |
| Requires Cloud Connect | Only Slack and Discord. This ARC isn’t connected to Cloud yet. |
The card vocabulary is deliberately generic, so it won’t always match the wording inside the panel. The Tailscale card, for example, reads Not configured whether Tailscale isn’t installed yet or is installed but not signed in — open the panel to see which.
Remote access (Tailscale)
This is the one integration worth reading in full before you turn it on. It’s also the one most owners want.
What it gives you: the ARC computer joins a private network of your own — Tailscale calls it a tailnet — and from then on any device signed into that same tailnet can open ARC. Your control pages, your cameras, your settings, all of it, from your phone at home or a laptop at another site. Nothing in the middle relaying your traffic, and no port forwarding or dynamic DNS to set up.
Tailscale is not a beta feature, and it doesn’t need Cloud Connect. You will need a free Tailscale account of your own — that’s where your tailnet lives and where you’ll manage which devices belong to it.
1. Install Tailscale on the ARC computer
If Tailscale isn’t on the machine yet, the panel says so and offers a single Install Tailscale button. Press it and Windows may ask you to approve the installer — approve it. ARC watches the installation and moves on by itself when it finishes.
That in-panel installer is Windows only. On a Mac or Linux host, install Tailscale yourself from tailscale.com and ARC will pick it up.
2. Connect with an auth key
Once Tailscale is installed, the panel asks for two things:
- Auth key (required) — generated in your own Tailscale admin, under Settings › Keys. The panel links straight there. A reusable, ephemeral, or pre-authorized key all work fine. Keys look like
tskey-auth-.... - Hostname (optional) — the name this machine will appear under in your tailnet. ARC prefills a sensible default; change it if you run more than one location.
Press Connect. When it comes up, the panel shows the Device name, the Address ARC is reachable at, and which Tailnet it joined. Write that address down — it’s how you’ll reach ARC from elsewhere.
ARC never stores your auth key
The key is used once to join the tailnet and is not saved. ARC only remembers the hostname you chose and when it last connected. If you ever need to reconnect, you generate a fresh key.
3. Restart ARC — this step matters for cameras
The moment the connection succeeds, a banner appears:
Restart ARC to finish setting up Remote Access. Cameras need a restart to stream over the connection.
Press Restart now and let it come back up. This isn’t optional housekeeping. ARC works out how to stream camera video when it starts, so if it was already running when the machine joined the tailnet, it has no idea the new network exists. Camera playback will still work remotely, but it falls back to a slower path with more delay and no audio. One restart fixes it permanently.
If ARC isn’t running under the launcher, you’ll be told to restart it yourself instead. The banner appears once — it’s gone after you restart or dismiss it.
4. Reaching ARC from somewhere else
Install Tailscale on your phone or laptop, sign in to the same tailnet, and open the address the panel showed you. That’s it — you get the full ARC interface, exactly as it looks on site.
Understand what you're opening up before you turn this on
Joining a tailnet is not the same as giving one person a password. Every device on that tailnet can reach ARC exactly as though it were plugged into the network at your location. Treat tailnet membership the same way you’d treat handing someone a key to the building.
Three things to do about it:
- Keep the tailnet small. Only devices you actually want reaching your rooms should be on it.
- Restrict access in the Tailscale admin. ARC does not set up access rules for you. If you want only certain devices to reach ARC, that’s configured on the Tailscale side.
- Prefer a one-time or ephemeral auth key. During the moment ARC connects, the key is briefly visible to anything inspecting the machine, so a key that can only be used once is the safer choice.
Key expiry — the thing that catches people out
Tailscale expires device keys after 180 days by default. When that happens, remote access simply stops working and you have to reconnect with a new key.
ARC warns you well ahead. Inside 30 days of expiry, an amber banner appears in the panel telling you how many days the connection has left and counting down, alongside a Keep it active link to your Tailscale admin. Follow it, find the ARC machine in your device list, and turn key expiry off for that device. Do that once and the warning never comes back.
Everyday controls
Once you’re connected, the panel keeps two buttons:
- Disable pauses remote access without forgetting who you are. The status becomes Paused and Enable brings it back.
- Sign out removes the machine from your tailnet entirely. ARC asks you to confirm, because getting back on means generating a fresh auth key.
Leave ARC on its default network setting
Remote access only works if ARC is reachable across a network at all. That’s how ARC ships, so unless someone has deliberately restricted it to the local machine, there’s nothing for you to change.
Weather
The Weather integration watches the US National Weather Service for active warnings and watches covering your location, and surfaces them where staff will actually see them. It’s currently in beta.
There’s no account and no key — just tell ARC where you are.
Setting it up:
- Set your location, either with Use my browser location or by typing a 5-digit US ZIP code and pressing Look up by ZIP. The browser-location button needs a secure connection; if ARC tells you so, use the ZIP code instead.
- ARC looks up the National Weather Service zones covering that spot and lists them under Zones to monitor — a forecast zone, a county, sometimes a fire weather zone or a marine zone. They all start selected. Deselect any you don’t care about.
- Turn on Weather monitoring enabled. That switch stays greyed out until you have a location and at least one zone selected.
Under What to monitor, choose Warnings, Watches, or both. Lower-priority advisories and statements are deliberately left out so the badge doesn’t cry wolf.
Where alerts show up is the part worth deciding on:
| Surface | Behavior |
|---|---|
| The control page badge | Always on. A chip in the information bar shows the number of active alerts; click it for the Active weather list with each alert’s severity and when it runs until. |
| Post into staff notifications | Optional. Each new warning or watch also lands in the staff notifications feed. No acknowledgment needed. |
| Full-screen border on warnings | Optional. Puts a red border around the whole control screen while a warning is active. Watches don’t trigger it. |
| Show on audience display screens | Optional. Adds a small read-only badge in the corner of every active room display. |
ARC checks roughly every minute. The Status section shows when it last checked, along with a Refresh now button if you want to force it.
Alert data comes from the National Weather Service. ARC isn’t affiliated with, sponsored by, or endorsed by NOAA or the National Weather Service.
UniFi Protect
If you run Ubiquiti cameras and have a UP Viewport screen in your control room, this integration makes that screen follow your staff: pick a game on the control page, and the Viewport switches to the camera view you mapped to it. It’s in beta.
This is separate from ARC’s own camera feature — see Vision for cameras inside ARC itself.
Setting it up:
- In the panel’s connection section, enter the Host — your UniFi Dream Machine or Protect controller’s address — and an API Key you create in UniFi OS. Press Connect.
- Under Discovered viewports, press Adopt on each Viewport you want ARC to drive. If the list is empty, make sure the Viewport is adopted in UniFi Protect first.
- In Game mappings, each adopted Viewport gets a row per game with a dropdown of your UniFi live views. Pick the view that Viewport should switch to when that game is selected. It saves as you go.
Refresh reloads viewports and live views from the controller; Disconnect ends the connection but keeps your settings. Adopted viewports show Connected or Offline so you can tell at a glance whether a screen is powered up.
Remember the output lands on the physical Viewport screen in your control room, not inside ARC.
UniFi is a trademark of Ubiquiti Inc. ARC is an independent third-party product and isn’t affiliated with, sponsored by, or endorsed by Ubiquiti.
ElevenLabs
ARC has its own built-in text-to-speech that needs no account and no internet. ElevenLabs is the upgrade path: cloud voices that sound considerably more natural, for hints and narration. It’s not a beta feature.
You supply your own ElevenLabs account and API key, and your usage counts against your own ElevenLabs plan.
Setting it up:
- Open the ElevenLabs card and paste your key into the API key field. It saves automatically. The panel links out to your ElevenLabs account if you need to generate one.
- Press Import voices to pull your ElevenLabs voice library into ARC.
- Preview any imported voice with its play button. Remove ones you won’t use to keep the list short — once you have more than a few, a search box appears.
Once a key exists, a small usage chip appears beside the key field showing your remaining character allowance against your limit. A trash button next to the field clears the key; you press it twice to confirm.
Preview options are just for auditioning
The collapsed Preview options section sets how voices sound when you audition them here. What a game actually speaks during a session is set per game, in the Game Editor under General → Voice & TTS.
The card only reads Active once you’ve saved a key and imported at least one voice — a key on its own leaves it at Not configured.
Prefer to stay offline? ARC’s built-in text-to-speech lives at System → Overview → Text-to-speech and needs no account at all.
ElevenLabs is a trademark of ElevenLabs Inc. ARC is an independent third-party product and isn’t affiliated with, sponsored by, or endorsed by ElevenLabs.
Slack and Discord
These two work identically: they mirror one channel in Slack or Discord with one channel in ARC’s chat, in both directions. Post in Slack and it appears in ARC. Post in ARC and it appears in Slack. Handy if your team already lives in one of those and you’d rather not ask them to watch two places.
Both are in beta, and both are the only integrations on this page that need setup outside the ARC computer.
These two need Cloud Connect and the ARC Portal first
Unlike everything else here, Slack and Discord can’t be set up entirely on your own ARC. Two things have to happen first:
- This ARC must be connected to Cloud. Until it is, the card reads Requires Cloud Connect and the panel says “Connect this ARC to Cloud before setting up Slack.”
- Your Slack workspace or Discord server is linked in the ARC Portal, not here. The panel has a Connect in Portal button that opens the right page in a new tab.
Once both are done, a green Connected in Portal badge appears and the channel pickers come to life.
After that, the Channel mirroring section gives you two dropdowns — the Slack (or Discord) channel on one side, the ARC channel on the other — and a Save button. Unlink takes the pairing apart again.
The panel’s status line tells you exactly where you are: Cloud Connect required, then Not connected, then Ready to mirror, and finally Active, which shows the two channels it’s bridging and confirms the direction is two-way.
Slack is a trademark of Salesforce, Inc. and Discord is a trademark of Discord Inc. ARC is an independent third-party product and isn’t affiliated with, sponsored by, or endorsed by either.
Writing suggestions (OpenAI and Anthropic)
Two separate cards, one feature. Connect either an OpenAI or an Anthropic account, and ARC can offer rewrites of a hint you’ve written — clearer, shorter, less revealing, whatever you’re after. Both are in beta.
You bring your own API key, so any usage is billed to you by that provider. Only one can be active at a time — turning one on turns the other off.
Setting it up:
- Open the OpenAI or Anthropic card and paste your key into the API key field. Press Save key. ARC stores it separately and never shows it again, so keep your own copy.
- Press Test connection to confirm the key works.
- Turn on Use for writing suggestions. That switch stays disabled until a key is saved.
Three more sections appear for whichever provider is active:
| Section | What it’s for |
|---|---|
| Model profile | How much speed you want to trade for quality: Fast, Balanced, or Best. |
| Permissions | Allow objective context decides whether ARC may include the objective’s name, its solution, and its other hints when it asks for a rewrite. Leave it off if you’d rather send only the hint text itself. |
| Monthly usage | Requests, remaining, and token counts for the current month, plus an optional Monthly request limit. Leave the limit blank for unlimited. |
Where you actually use it
Open a game in the Editor, go to Objectives, and open a hint. There’s an Improve with AI button on the hint editor. It opens a Writing suggestions panel with five one-click directions — Clearer, Shorter, Less revealing, More immersive, More natural to say — plus a box for your own instruction if none of those fit.
Press Generate 3 alternatives and you get three rewrites side by side, each with an Apply button that drops it straight into the hint. Nothing is changed until you press Apply.
If you open it before setting a provider up, it tells you plainly: enable an AI capability in System → Integrations to use it.
Keeping an eye on outside requests
Some services charge by request, or cut you off if you ask too often. For the integrations where ARC calls out directly — Weather, UniFi Protect, and ElevenLabs — the bottom of the panel carries an API requests panel with three counts: the last 24h, the last 30d, and All-time on this install. Below them, a line showing when the last request went out and how it went.
It loads when you open the panel and has a refresh button; it doesn’t poll in the background. If a service ever starts behaving oddly, this is the first place to look — a count that’s climbing much faster than you’d expect usually means something is retrying in a loop.
Tailscale, Slack, and Discord don’t have this panel, because ARC doesn’t make direct calls to them. The AI integrations don’t either — their Monthly usage section does the same job with more detail.
Where to go next
- The System Area — the rest of the business-wide settings and where Integrations sits among them.
- Connections — the protocol bridges to your own hardware, which is a different thing from an outside service.
- Vision — ARC’s own cameras, saved views, and the camera add-on.
- Objectives — where hints live, and where the writing suggestions button appears.
- Displays and Audio — how spoken hints reach a room once you’ve picked a voice.