OpenFrame

Using the Knowledge Base & Help Center

DOCUMENTATIONGUIDEKNOWLEDGE MANAGEMENTOPENFRAME

Phase 3 — Platform Navigation · Step 7

Section

June 25, 2026

Published

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Using the Knowledge Base & Help Center

Platform Navigation · OpenFrame Onboarding

Two resources sit at the bottom of the left sidebar — the Knowledge Base and the Help Center — and they do different jobs. One is OpenFrame's help hub for you; the other is your documentation store. This guide sorts out which is which and when to reach for each.

Help Center — OpenFrame's help hub

Open Help Center for a hub of product resources, each as its own card:

  • Onboarding Guides — step-by-step product walkthroughs (these very guides).
  • Development Roadmap — what OpenFrame is building next.
  • Product Releases — version history and release notes.
  • Bug-fixes & Enhancements — recently shipped fixes and improvements.
  • Support Tickets — open and manage your support requests.
  • FAQs — quick answers about how OpenFrame works.
  • Privacy Policy and Terms of Service — the legal pieces.
  • Knowledge Base — a shortcut into the article store (below).

Reach for the Help Center when you want to learn the product, check what's new, or get unstuck — it's the "help me understand OpenFrame" destination.

Knowledge Base — your article store

Open Knowledge Base to build and browse your own documentation — runbooks, client-specific notes, internal procedures. It's organized like a filing cabinet:

  • Folders — group related articles. Create one with New Folder; there's a top-level folder to start from.
  • Add Article — write a new entry.
  • Search for Articles — find anything fast.
  • Archive — retire articles you no longer need without deleting them.

Each item shows its name and created date. Use this for the knowledge your team generates and needs to find again.

Which one do I want?

  • "How does this OpenFrame feature work / what changed?" → Help Center.
  • "What's our procedure / what did we document for this client?" → Knowledge Base.

In short: Help Center is for consuming OpenFrame's help; Knowledge Base is for creating and curating your own.

Quick checklist

  • Opened the Help Center and scanned its cards (Onboarding, Roadmap, Releases, FAQs, etc.)
  • Opened the Knowledge Base and saw the folder/article structure
  • Created or browsed an article with Add Article / Search
  • Knew the rule: Help Center = learn OpenFrame, Knowledge Base = your own docs

What's next

That's the help and documentation layer. Next in getting oriented, see the device detail surfaces — starting with Reading the Device Software Tab.

Based on OpenFrame v0.9.19. The Help Center cards and Knowledge Base tools evolve between releases — what's in your console wins.

Vladislav Marchenko

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 3 — Platform Navigation

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.

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.

Getting Started

“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.

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.
The minimum viable model has five fields: Core Argument (a one-sentence claim, not a topic), Audience Segment plus Pain Point (who is reading and the problem they arrive with), Proof Points (two or three concrete facts reused across every format), Platform Destinations (where it publishes and in what format), and Grading Criteria (the measurable definition of good the AI checks each draft against before a human sees it).

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.

Log Aggregation

Loki collects logs from many systems into one place, storing them cheaply by indexing labels instead of full content. You query them with LogQL inside Grafana. It is built to scale across hosts and clients while keeping storage costs low.