FAQs
‍Frequently asked questions

Yes, very thoroughly. With the free Peakboard Designer you can build your project without functional restrictions and test it in preview mode with real data. You can even connect your laptop via HDMI to a monitor or touchscreen and work with the team on the target device. After 30 minutes a notification banner interrupts the preview mode. For permanent operation on a screen, you need a Peakboard Box or a BYOD license.

Peakboard does not replace a BI tool – it complements one. BI solutions such as Power BI are usually already established in the company and strong at automating complex analyses and historical data. For capturing and displaying real-time and process data, however, they are poorly suited and normally require a costly IT project – which makes later changes hard to implement.

This is exactly where Peakboard comes in: as a low-code platform for operational intelligence, Peakboard can be used without deep IT knowledge, analyzes data in real time, and lets teams intervene directly in running processes. Changed requirements and feedback loops can be reflected quickly.

The Peakboard Designer is free, with no time limit. Licenses are charged per device, billed annually:

• Peakboard BYOD starting at $1,400/year (pricing capped at $28,000/year for 20+ licenses)
• Peakboard Box (incl. hardware) starting at $2,000/year (additional Boxes beyond 20 at $300/year each)

Onboarding, implementation, support, and maintenance are included. The Peakboard Hub Online includes a free Starter tier for small setups; pricing for larger deployments is available on request. Please contact us for current details.

Yes. Peakboard offers individual workshops and free webinars. Inquiries go to sales@peakboard.com.

Peakboard technical support is reached by email at support@peakboard.com – that is the fastest route.

For most applications, the low-code editor is enough: drag & drop, conditional formatting, pre-built templates, and an intelligent assistant. OPEX and lean teams build productive dashboards on their own. For more complex logic, you can either work with Building Blocks or write Lua scripts directly in the classic text editor.

Peakboard applications are usually built by the people who know the company's data sources best – but in principle any employee can use Peakboard Designer. Installing the Designer may require administrator rights, depending on company policy. The Peakboard Box itself can be set up without admin rights; connecting it to the network infrastructure normally involves IT.

No – Peakboard is offered exclusively as a subscription. Regular updates, support, and security features are included, which keeps usage flexible.

There are two ways:

1. Peakboard Web Access – direct access to a single Peakboard Box via your web browser (desktop or mobile). You see a current screenshot of the visualization, can edit lists, variables, and resources, swap files like images or PDFs, and run predefined functions. Ideal for users who want to operate their Box.
2. Peakboard Hub – central management of multiple Peakboard Boxes. The browser gives you an overview of all devices (with regularly updated screenshots) and lets you switch visualizations, adjust network and IP settings, and manage licenses and users. Ideal for administrators and teams with larger setups.

Yes. Peakboard dashboards are fully interactive – via mouse, keyboard, presenter, or directly on a touch display.

A spare device in stock is the best protection against longer downtime: if a Peakboard Box fails, the replacement can be put into service immediately.

The refresh interval is freely configurable – from real time to intervals of several days, depending on the use case and the data source.

Systems that are not listed can usually still be connected, because most host systems expose APIs or standard interfaces. Peakboard extensions and the Peakboard team support the integration.

If a Peakboard Box stops working, Peakboard support can help. Many problems are resolved via remote access, without a replacement being needed.

A defective Peakboard Box is replaced through Peakboard support. The faulty device is returned for analysis and, where possible, sustainably repaired.

Yes. Peakboard is SAP-certified and comes with its own fully integrated interface to SAP systems.

The Peakboard Box is connected via LAN or Wi-Fi and behaves like a Windows client on the network. Configuration is done in Peakboard Designer; integration into an Active Directory domain is optional.

Peakboard support usually replies within one business day. The team is available on weekdays from 9am to 12pm and from 1pm to 5pm (CET).

The Peakboard Box runs in kiosk mode with a restricted Windows user who cannot install or run programs; switching to desktop mode is not possible. A separate administrator account exists for administrative tasks – change its password after the first login and store it securely, because it cannot be reset.

Peakboard does not pass any data to third parties. Data is exchanged exclusively within the interfaces in use, for example with the SAP system. The exception is cloud-based interfaces such as OneDrive, where the transfer is technically necessary.

Peakboard buffers data locally on the Peakboard Box and only briefly – usually for a few minutes. For longer or larger-scale buffering, an external database is recommended.

Peakboard uses the rights concept of the Windows operating system: user accounts are password-protected, Windows Defender is active, and passwords in visualizations are encrypted. Additional access restrictions at network level should be set up in your own network.

A virus scanner is not necessary on the Peakboard Box: the closed system and restricted user rights already protect it. Anyone who still wants one can install it via the administrator account.

Upgrading to a higher Peakboard version is possible for a fee and is activated with a new license key. Inquiries go to sales@peakboard.com.

The Peakboard Box runs on Microsoft Windows 10 IoT Enterprise (LTSC) with support until 2029. Only the Peakboard Runtime is installed; additional software cannot be installed.

The Peakboard Box comes with a role concept. Every Box ships with an administrator user who can create any number of additional users with their own roles and rights.

One monitor can be connected per Peakboard Box via HDMI cable. Splitting a visualization across multiple monitors is not intended.

Peakboard Pro includes a limited number of data connections, while Peakboard Enterprise includes all of them. The complete list is on the Data connections page.

The Peakboard Box is built for industrial environments: it has an aluminum housing, can be mounted on a DIN rail and additionally protected if required.

Peakboard Boxes can be managed centrally in the browser with the Peakboard Hub – including updates and content distribution. The Hub is available cloud-based or on-premise.

A screen for the Peakboard Box needs an HDMI input. Touchscreens additionally need a USB port, through which the Box receives the touch input.

On the Peakboard Box, all ports are blocked by default – except ICMPv4/v6, ports 6, 7, 5985 and 5986, and 40404, 40405, and 40407 for Peakboard communication.

The Peakboard Box requires no internet access by default and operates on the local network.

The Peakboard Box can be integrated into a Windows domain, but does not have to be: domain integration is optional and not required for operation.

Guides and tips for Peakboard Designer are published on the Peakboard help site and on the Peakboard YouTube channel.

Software updates cost nothing extra. All updates and technical support are included under a valid maintenance contract.

The language in Peakboard Designer is changed via the flag icon in the bottom right corner.

Peakboard releases an update roughly once a month. Under the SLA you have access to all updates. Peakboard recommends updating 2–3 times a year or whenever a specific need arises. Security-relevant updates are communicated actively. All release information is published on the Peakboard help site.

Peakboard Designer is available in German and English, as is the Peakboard help site.

Yes. Peakboard provides ready-made dashboard templates that can be customized in Peakboard Designer – available on the Peakboard template site.

There is no functional difference between Peakboard Box and Peakboard BYOD. With BYOD you use your own Windows device just like a Peakboard Box – same applications, same data connections. The difference lies in the hardware alone: Peakboard supplies and supports the Peakboard Box, while you provide the BYOD device yourself.

Existing IPC hardware can be used directly with Peakboard BYOD – no additional procurement and no separate IT approval for new devices. The main benefit is therefore speed at the start.

After inquiring via the Peakboard pricing page you receive a download link for Peakboard BYOD. The trial version is ready to use right after installation; for permanent operation a hardware-bound license is activated.

Yes. Peakboard BYOD displays Peakboard applications on your own Windows device, without a Peakboard Box. All you need is a usage license and a compatible Windows device.

Peakboard BYOD runs on Windows 10 from version 1607 and on Windows 11, each in a 64-bit edition. 32-bit systems and ARM-based processors are not supported.

Yes. Peakboard BYOD runs on Windows tablets and Windows laptops, provided a 64-bit edition of Windows 10 or Windows 11 is installed. Devices with an ARM processor are not supported.

Peakboard BYOD requires at least a 1 GHz dual-core CPU, 4 GB RAM, and 64 GB of storage. For smooth continuous operation, Peakboard recommends more capable hardware. If you are unsure, the Peakboard sales team will review your existing setup.

With your own IPC hardware, Peakboard provides no replacement units and no hardware support – faulty devices remain the customer's responsibility. Commissioning can also take longer, because the Peakboard Box ships pre-matched to the Peakboard software while third-party hardware has to be checked and set up first.

Peakboard is licensed per device. For 5 applications on 5 screens you therefore need 5 BYOD licenses and 5 compatible devices.

Running Peakboard requires either a Peakboard Box or your own Windows device with Peakboard BYOD.

The Peakboard Box needs:

• a power connection (USB-C power supply is included)
• a network connection via LAN or Wi-Fi
• a monitor with an HDMI port for the display

For Peakboard BYOD and for installing Peakboard Designer, Peakboard recommends a device running Windows 10 or newer.

No – the Peakboard BYOD license is tied to the hardware, not to a user. The license applies to one specific device; how many people work on that device does not matter. Everyone using the licensed hardware can run Peakboard BYOD without restriction.

Peakboard is a low-code platform for digitalizing production and logistics processes. It connects live data from SAP, machines (via OPC UA, MQTT, Siemens S7), and IT systems to interactive dashboards directly on the shop floor. Business teams build and modify applications themselves, without programming knowledge.

The Peakboard Hub is the central platform for Peakboard applications and turns decentralized shop floor solutions into an orchestrated overall system. The Hub is not mandatory – Peakboard Boxes and BYOD devices also run autonomously – but it makes a lot of things easier as soon as multiple devices, multiple plants, or newly captured data come into play. Three core jobs:

1. Centrally manage Peakboard Boxes and BYOD devices – device overview, licenses, IP addresses, remote configuration, and automatic updates rolled out to the entire device fleet.
2. Centrally store and historize data from machines, sensors, and manual inputs instead of only displaying it momentarily. Hub lists work as central data tables that all connected devices can read and write simultaneously; Hub Variables synchronize individual values via MQTT in real time.
3. Define logic once in Hub Flows and run it centrally on the Hub server, instead of maintaining it on every box separately – including buffering and bundling of thousands of machine requests to SAP, writing production figures back to ERP/MES, and centrally managed credentials for third-party systems. (Hub Flows are currently only available in the On-Premise edition.)

The Hub addresses two user groups: IT staff for device administration, network configuration, and access control, and process teams for data models, workflows, and reporting.

No – the Peakboard Hub is optional. Peakboard Boxes and BYOD devices also run autonomously without it. As soon as multiple devices, multiple plants, or centrally captured data come into play, the Hub makes operations considerably simpler.

Peakboard Hub Online is the SaaS edition – instantly ready, hosted and maintained by Peakboard, with a free Starter tier for small setups and pricing available on request beyond that. Peakboard Hub On-Premise runs on your own Windows Server hardware in your own intranet, offers full data sovereignty, and is currently the only edition with Hub Flows, availability overview, Hub logs, and external MQTT broker integration. Both editions are equally valid; the choice depends on data sovereignty requirements, workflow complexity, and setup size.

Peakboard Hub Online includes a free Starter tier for small setups with up to 5 connected Peakboard Boxes or BYOD devices, including Hub lists. Beyond that, pricing is available on request; the paid tier adds central device management, connections, alerts, the Power Automate Connector, and the Hub API. Peakboard Hub On-Premise is licensed separately based on setup size, and add-ons such as Hub Flows affect the total. Both editions can be trialed free of charge for 6 months.

Hub Flows automate data processing and business logic directly inside the Peakboard Hub. Flows are assembled visually from triggers and steps, without classical programming. Available triggers are time-based (periodically or at fixed times), event-based (on data changes), function triggers with parameters, and manual triggering. Flow projects are created in Peakboard Designer and uploaded to the Hub, where they run centrally on the Hub server – without UI or display device, instead of being maintained on every box in parallel. Hub Flows are currently only available in the On-Premise edition.

Yes. The Peakboard Hub connects the shop floor to IT systems such as SAP, ERP, and MES. Data flows in both directions: machine requests can be buffered and bundled before being passed to SAP, order data can be received, and production figures reported back to ERP or MES. Credentials for third-party systems are held centrally in the Hub.

Hub lists are central data tables with a graphical interface that all connected Peakboard Boxes, BYOD devices, browser applications, and the Hub API can read and write simultaneously. Columns can be configured with types, default values, and constraints; filtering (equal, not equal, starts/ends with, contains) and sorting are built in. Typical data models: machine and production data acquisition, shop floor management, actions, shifts, and newly captured values.

The Peakboard Hub stores and evaluates alerts centrally. There are three alert types – Info, Warning, and Problem – delivered by email to configurable recipient lists or by browser push notification on Windows, macOS, Android, and iOS. Alerts are triggered by Peakboard Boxes, Hub Flows, or via the Hub API.

Peakboard Hub On-Premise runs on a Windows Server with IIS in your own intranet. As database, the included SQL Server Express or your own SQL Server can be used. Authentication uses Active Directory with Windows username and password.

Yes. The Peakboard Hub provides an HTTP or HTTPS interface for integration with external systems and for remote function calls. Hub Online uses HTTPS only; Hub On-Premise supports HTTP or HTTPS depending on configuration. Peakboard also provides an MCP server, which makes the Hub available via the Model Context Protocol as a data source for AI agents and LLM applications.

Peakboard is aimed at mid-sized and larger production and logistics companies, primarily in the US and DACH. Typical users are OPEX managers, lean managers, digitalization leads, and production managers. The focus is on companies that want to bring together machine data and business-team applications without large classic IT projects.

Four points:

1. On-premise as standard – data stays in your own network, supports strict data sovereignty requirements.
2. Device-based subscription instead of user-based licensing, avoiding cost explosions as you scale.
3. SAP-certified connector for EWM, ECC, MES, S/4 HANA – with roots in the ecosystem of Theobald Software, a long-established SAP interface vendor.
4. Business-team autonomy – OPEX and lean teams build and modify applications themselves, at their own pace and close to the process.

Neither. Peakboard is an edge-computing platform that sits between data acquisition (PLC, SCADA) and planning (ERP, MES, BI tools). Unlike MES systems, Peakboard is not monolithic and not built for multi-year implementation projects. Unlike BI tools such as Power BI, Peakboard offers real-time updates (per-second instead of periodic), a feedback channel from the shop floor, and direct machine connectivity via OPC UA.

Peakboard binds over 100 data sources out of the box, including: SAP (certified, incl. EWM, ECC, MES, MII, S/4 HANA), OPC UA, MQTT, Siemens S7, Beckhoff, Rockwell, Modbus, MS SQL, Oracle, MySQL, MongoDB, REST APIs, ODBC, Power BI, Qlik, Tableau, IBM Cognos, Excel, SharePoint, OneDrive, Dropbox, Google Drive, CSV, JSON, XML, and OData.

Peakboard Designer, Peakboard Boxes, and BYOD devices generally run locally at the customer – data does not leave the company. Only with the Peakboard Hub is there a choice: as Peakboard Hub Online (SaaS, hosted by Peakboard) or as Peakboard Hub On-Premise in your own network. For industrial customers with strict data sovereignty requirements, Hub On-Premise is the common setup.

First applications are live in under 5 days; a full rollout typically in under 3 months.

Peakboard GmbH was founded in Stuttgart in 2016 and spun off in 2022 as an independent company from Theobald Software, a long-established SAP interface vendor. The company serves over 300 customers in DACH and the US and operates from multiple locations. Peakboard America Inc. was founded in Chicago in 2022.

No – and that has nothing to do with being skeptical about AI. Quite the opposite: AI-assisted building is already part of Peakboard. You describe what you need in a prompt and get a finished Peakboard project. The difference is what the result is built for.

A generic AI generates a slick web app that lives in a browser tab. On the factory floor, that is the wrong shape:

• It runs at the workplace, not in a browser tab. Peakboard runs locally on the Box or tablet right at the line – with direct access to scanners, RFID/NFC readers, foot switches, label printers and andon lamps.
• Industrial data is not REST and JSON. OPC UA, S7, Modbus, SAP, MQTT, SQL and historians bring sessions, subscriptions and automatic reconnect – all built into Peakboard. The AI wires up existing tags instead of fragile middleware.
• Built to run continuously. Full-screen, automatic recovery, last-known state kept on screen when the network blips – not the lifecycle of a tab someone might close.
• On-premises by default. Designer and runtime both stay inside the plant. Nothing leaves the facility unless you deliberately send it out.
• Maintainable, not a black box. The output is a normal Peakboard project that your team can open, adjust and extend in the Designer – even after staff changes. No web stack, no per-app cloud bill.

In short: AI does not replace Peakboard – Peakboard puts AI in the right place.

Read more in the blog post: Industrial Vibe Coding: What Generic AI App Builders Miss on the Shop Floor.