OpenFrame Gen1 is Here

Add a Device Display Name

DOCUMENTATIONGUIDEOPENFRAME

Phase 2 — Device Deployment · Step 5

Section

June 18, 2026

Published

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Read this first. In the current build, OpenFrame shows a friendly display name for each device that's distinct from its raw hostname, but it's derived from what the device reports about itself — there isn't a separate "set a custom nickname" field in the console yet. If you need your own labels (location, user, role), Device Tags are the tool for that today. This guide explains how device naming works now and the practical way to get custom labels. We'll update it if a manual rename field ships.


How device names work

OpenFrame tracks two names for every machine, and it helps to know the difference:

  • Display name — the friendly name shown at the top of the device's detail page, e.g. "Pavlo's MacBook Pro." This comes from the device's own reported name (the computer name the OS knows it by).
  • Hostname — the technical network name, e.g. "Pavlos-MacBook-Pro.local," shown in the device detail under Hostname and in the Devices list.

So a Mac whose macOS computer name is "Pavlo's MacBook Pro" shows that as its display name, while its .local hostname is what you'll see in network contexts. They're related but not identical.

Because the display name follows what the device reports, the cleanest way to control it is to set a sensible computer name on the device itself (in macOS: System Settings → General → About → Name; in Windows: rename the PC) before or shortly after enrollment. The change flows through as the device checks in.


Finding a device by name

However a device is named, you don't have to scroll:

  1. Go to Devices.
  2. Type into Search for Devices — it matches on the device name, so a partial string is enough.
  3. Switch between the list and grid (card) views with the toggle at the top right, whichever is easier to scan.

Getting custom labels today: use Device Tags

If what you actually want is to label machines your way — by site, by client contact, by role — that's exactly what tags are for, and they're more powerful than a single nickname field because you can filter the whole fleet by them.

Examples:

  • Purpose: reception-pc
  • Type: server
  • Site: london-office

You can attach these at enrollment (on the Add Device screen) or filter by them anytime with the Device Tags filter on the Devices list. Full walkthrough: Organize Devices with Device Tags.

Rule of thumb: if you'd want to find all devices sharing a label, that's a tag, not a name. Names identify one machine; tags group many.


Quick checklist

  • Understand the difference between the friendly display name and the hostname
  • Set a clear computer name on the device itself if you want a tidier display name
  • Use Search for Devices to find machines by name
  • Use Device Tags for custom labels you want to filter on
  • Flag to your OpenFrame contact if a manual in-console nickname field would help your workflow

What's next

Naming sorted, lean into the real organizing tool: Organize Devices with Device Tags. After that, Phase 2 is complete and you're ready for Phase 3 — Platform Navigation.


Based on OpenFrame v0.9.19. Device naming behavior is evolving — re-check the console before treating the "no manual nickname field" note as permanent.

Vladislav Marchenko

Head Of Marketing

Hi all! My name is Vlad and I’ve been brought on to head the marketing team at Flamingo. Thankfully, this isn’t the first time I will be building a marketing department from scratch, so the experience should come in handy. Now it’s time to dive into the world of MSPs and find myself in this new world.

More in Phase 2 — Device Deployment

Related Content

Product Releases

Webinars

Case Studies

Blog Posts

Frequently Asked Questions

MSP AI Agents

Yes. In production MSP shops today, 10% to 25% of tickets close before a human opens them. Thread alone has processed 173 million tickets across 750-plus MSP partners at 96% triage accuracy, handing back 490,000-plus technician hours. Agents own the low-risk, high-volume work (password resets, MFA enrollment, known installs, onboarding and offboarding) and flag anything that touches production data or needs judgment for a human to take.
On a five-person desk, reported deployments show $78,000 to $130,000 in annual direct labor savings, roughly 30% fewer escalations, and 15% to 20% better SLA compliance. Broader MSP adoption data adds ticket handling time cut by 45% and five to 12 points of margin, all from reclaimed capacity rather than headcount cuts.

Getting Started

The People Hub is Flamingo's internal home for the team. Every employee can browse the team roster, open a colleague's “Who Am I” profile, share what they shipped each month, and keep their own profile up to date. Managers additionally see performance insights built on the SPACE framework.
“What I Shipped” is your monthly highlight reel. Each month you can post the work you're proud of — a feature, a document, a deal, a fix — with a short write-up and media. It's visible to the whole team, so everyone can see the impact you're making.

About OpenFrame

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.
Most platforms give you one piece and expect you to bolt the rest on. OpenFrame unifies the whole stack in one place, with AI copilots built in. Fewer logins, fewer bills, less duct tape.

IT Documentation

Hudu is IT documentation software that MSPs and internal IT teams use to centralize client documentation, network details, encrypted passwords, IT assets, and SOP runbooks in one searchable platform, so technicians find what they need without digging through scattered files.

Content Operations

A single data model is one structured record that captures everything about a content idea - the core argument, the audience and its pain point, the proof points, the platform destinations, and the grading criteria - before anything gets written for distribution. Every output (LinkedIn post, blog article, short-form video, email) is a transformation of that one source record, so changing the source lets you regenerate every downstream format.

IT Glue Review

For established MSPs already running Kaseya, Autotask, or Datto RMM, yes. IT Glue is mature, deeply integrated, and highly rated at 4.6 on G2. Smaller shops often find the five-user minimum and onboarding fee push the cost past the value.

BCDR Planning

BCDR stands for business continuity and disaster recovery. Business continuity covers keeping critical operations running during a disruption. Disaster recovery covers restoring data, systems, and infrastructure afterward. A BCDR plan combines both into one document with defined recovery targets and owners.