Skip to content

Getting started

ARROW is a secure remote network access platform for security teams. Whether you are running a penetration test, a red team, an incident response, a compliance audit, or a managed engagement for a client, you run the whole engagement from the ARROW Platform, the web console where you request devices, have them provisioned with the tooling you need, ship them to a client site, and connect to them over a VPN from wherever you are.

This guide shows you how to find your way around and submit your first request.

This documentation is written for several kinds of reader. You will probably recognize yourself in one of these:

  • You run the engagements. You are a penetration tester, red teamer, incident responder, or security consultant, and you need a box on the client’s network fast, reliable access to it from wherever you are, and the tools already in place. Most of your time is spent in ARROW Control and ARROW Manager on the device itself, reached over the VPN.
  • You run the schedule. You are an engagement lead or project manager coordinating clients, timelines, and logistics. You need the right device at the right place before the engagement starts, so you track shipments and watch usage and billing. You work in Clients, Device Requests, and Metrics.
  • You run the account. You are an organization administrator who manages who has access and sets up API keys for automation. Least-privilege access and predictable costs are your priorities.
  • You receive the hardware. You are the person at the client site who unboxes an ARROW device, plugs it into power and the network, and lets it come online. Start at Receiving a Device, which covers what to connect, the exact network access the device expects, and what to check if it does not come online. It is written for you and your network team, and needs no ARROW account.

The docs explain where the buttons are and also why a feature matters and what it affects. If something in the product behaves differently than described, or you are not sure how a step should go, contact support rather than guessing.

When you sign in, you start on the Dashboard. It answers the questions you have when you open the console: how much of your plan you are using, whether your devices are healthy, what happened recently, and where your devices are right now.

ARROW Platform dashboard overview ARROW Platform dashboard overview
The ARROW Platform dashboard with plan usage, device health, your devices, recent activity, and a location map
  1. 1 The sidebar is how you move between every area of the platform.
  2. 2 Plan usage shows how many devices you have out against your plan. Watch this as you approach your allocation.
  3. 3 Device health breaks your fleet down into healthy, warning, and critical devices.
  4. 4 Devices is a searchable list of your devices. Click one to fly to it on the map.
  5. 5 Recent activity lists imaging, requests, and fulfillment events as they happen.
  6. 6 Alert cards flag VMs and devices that are past their return or end date, so nothing is left running or unreturned. When nothing needs attention, this card reads All clear.

The panels are:

  • Decrypt appears when your organization has ARROW Decrypt connected. It shows how many of its nodes are online and how many jobs are running, and Launch Decrypt opens it, which needs the ARROW VPN.
  • Plan usage shows your plan and how many devices you are consuming against it, including your physical and virtual device counts and how many VMs are currently active. Watch it if you are close to your allocation.
  • Device health rolls your whole fleet into a single bar showing healthy, warning, and critical devices.
  • Devices is a searchable short list of your devices with their status, so you can jump to one without leaving the Dashboard.
  • Recent activity is a running feed of imaging, deployment, and request events. Check it after you submit a request to watch it move.
  • Map plots your on-site devices on an interactive globe, which helps when you run engagements in more than one location.
  • In transit, Return alerts, and VM completion stack down the right side. Each one appears only when it has something for you: devices with the carrier, engagements past their return date, or VMs that need closing out. A VM in that card can be marked complete or given a new end date from the card itself, and once ARROW has sent a final notice the card shows the date it will close the request on its own (see Notifications). When all three are quiet, the column reads “All clear”.

The panels float over the map, so you can arrange them around whatever you are looking at. Drag a panel by its header to move it, use the minus button in its corner to collapse it, and reset everything with the Reset layout icon in the strip above the map, which also shows when the page was last updated and has a refresh button. Your total and online device counts and your pending requests sit in the middle of the top bar as Devices, Online, and Pending, beside a VPN readout that shows whether your browser can reach your organization’s VPN. Click it to test again.

The sidebar on the left holds every section. They follow the stages of an engagement:

  • Dashboard is the live overview you land on.
  • Notifications is your inbox, the record of everything ARROW has sent you, with a count of the ones you have not read yet.
  • Devices is your inventory, where you view and manage every device assigned to you or your organization.
  • Device requests is where you ask for a physical device or a VM and track it through provisioning and delivery.
  • Images is the catalog of operating system images and their pre-installed tooling. Browse it to confirm a build has what you need before you request it.
  • VPN is how you reach your devices from anywhere. Check status and request setup keys here.
  • Clients is where you record the organizations you run engagements for, along with their sites and contacts. Devices ship to a client’s location, so requests use this information.
  • Users is where admins add teammates and set what they can do.
  • Metrics reports on your request volume, delivery times, and how long deployments run.
  • Billing shows your plan usage and invoices.
  • API keys lets you create credentials for the ARROW REST API when you want to automate.
  • Decrypt opens your organization’s self-hosted ARROW Decrypt password-recovery cluster, which you launch over the ARROW VPN. Admins set it up here; for everyone else it appears once a deployment is connected and shared with the team.

The Help group at the bottom links to Documentation, Support, and Info cards. Support is where you ask ARROW support for help with New ticket and follow every ticket you have raised, whether you raised it in the console or by email. Your organization’s name sits in the top bar beside the ARROW logo, and your account menu is at the top right, next to Logout. The strip under the top bar names the section and page you are on, and the status bar along the bottom of the window shows the console version.

On a wide screen, Collapse at the foot of the sidebar shrinks it to a strip of icons. On a phone, or in a narrow browser window, the sidebar folds away so the page gets the full width. The sidebar toggle at the top left, beside the ARROW logo, slides it back out over the page, and it closes itself as soon as you pick a section. Tapping outside it closes it without going anywhere. On the screens that use tabs, the tab strip scrolls sideways when there are more tabs than fit, so the last one is still reachable.

ARROW has three roles, and your admin assigns yours when your account is created:

  • An Admin can do everything, including billing, user management, and organization settings.
  • A Manager handles the day-to-day work of managing devices, creating clients, submitting requests, and monitoring team activity.
  • A User works with their assigned devices, submits requests, and connects over the VPN.

If a button or section described in these docs is not visible to you, your role is almost always the reason. Ask your admin.

Once you are signed in through your organization’s SSO, the path to a working device is:

  1. Add the client you are working for under Clients, including the site the device should ship to and the person who will receive it.
  2. Browse Images to find a build with the right OS and tooling.
  3. Go to Device requests and submit a request for that client and image.
  4. Once the device is provisioned, use the VPN section to connect to it securely.

When you request a device, you pick a client, and ARROW uses that client’s location and receiver contact as the shipping destination, so set up the client first.