Availability and support

What launch availability looks like for ARC

ARC is not trying to pretend launch looks the same everywhere. The current rollout is focused, practical, and built around the customers and support paths already reflected in the product.

The site already carries a United States launch notice, the launcher is currently packaged as a Windows installer, and the portal already exists for customer account, licensing, and installation workflows.

Launch geography

United States first

The current marketing site already makes clear that ARC is available in the US at launch.

Installer platform

Windows

The current packaged installer flow is Windows-based.

Customer surfaces

Portal plus community

ARC already has customer account surfaces and an active community link on the site.

Current launch position

United States launch first

ARC is currently positioned for a United States launch first, with international availability planned later.

Windows installer path

The release and installer flow currently points to Windows packaging, which makes the launch story cleaner and easier to support.

Customer account and licensing flow

ARC already has a real portal for accounts, licenses, and installations, so launch customers are not being pushed through a makeshift process.

How support can be described at launch

Portal

Account, licensing, and installation management

The portal is the natural place to talk about customer account and installation management because that surface already exists in the product.

Community

Discord for launch conversations and feedback

The marketing site already points people toward Discord, which is a strong support and feedback channel during launch.

Release visibility

Clear update path

Customers should know where to look when versions move. A release notes page helps support by reducing uncertainty.

Good details to gather before asking for help

These are practical details that make support faster and more useful.

  • Your location count and whether you are starting from one site or more than one.
  • What room hardware and device types you already have in place.
  • What system you use today, if you are replacing something existing.
  • Your biggest pain points: reliability, hardware sprawl, operator workflow, or room control complexity.

A plain-language launch promise

Focused availability is not a weakness when it is communicated clearly. A launch that says where ARC is available, how it is delivered, and where customers should go for help feels more credible than a launch that tries to sound universal before the support structure is ready.

That is the right tone for ARC right now: direct, practical, and honest about where the product is strongest today.

Nächster Schritt

Stay close to the launch path that fits you

If ARC is in scope for your operation, start with pricing and setup. If you are waiting on geography or timing, join the current launch-update path and community.